Printing apparatus

Abstract

This technology provides a way to restrict others from canceling the reception of a print job while it is being received for storage printing. [Solution] The MFP10 includes a user interface 17 and a controller 11. When a user inputs a cancellation instruction regarding a print job associated with them via the user interface 17, the controller 11 displays a warning to the user interface 17 if the cancellation instruction does not correspond to the user associated with the print job.

Description

Technical Field

[0001] The present application relates to a technique 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 Invention

Problems to be Solved by the Invention

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

[0005] The present application aims to provide a technique that restricts third parties from canceling print jobs for stored printing.

Means for Solving the Problems

[0006] To achieve the above object, a printing apparatus described in an embodiment is a printing apparatus including a user interface and a controller, wherein when a cancellation instruction relating to a print job associated with a user is input via the user interface, the controller displays a warning on the user interface if the cancellation instruction does not correspond to the user associated with the print job.

Effects of the Invention

[0007] According to the printing apparatus described in the embodiment, it is possible to restrict others from canceling print jobs intended for storage. [Brief explanation of the drawing]

[0008] [Figure 1] This is a diagram illustrating the configuration of an image forming system. [Figure 2] This flowchart shows an example of the procedure for a PC to retrieve secure function lock setting screen data from an MFP (Multifunction Printer). [Figure 3] This figure shows an example of how the Secure Function Lock settings screen changes. [Figure 4] This is a flowchart showing the steps for receiving and printing. [Figure 5] This flowchart shows the subsequent steps for the receiving and printing process shown in Figure 4. [Figure 6] This is a flowchart showing the steps for processing user interface operations. [Figure 7] This is a flowchart showing the procedure for pressing the cancel key. [Figure 8] This is a flowchart showing the steps for the display process. [Figure 9] This flowchart shows the subsequent steps in the display process shown in Figure 8. [Figure 10] This is a flowchart showing the login process. [Figure 11] Figure 10 is a flowchart showing the subsequent steps in the login process. [Figure 12] This figure shows an example of how the state of the user interface changes in response to changes in the internal state of the MFP. [Figure 13] This figure shows an example of a change in the state of the user interface, which is different from Figure 12. [Figure 14] This figure shows an example of a change in the state of the user interface, which is different from Figure 13. [Figure 15] This figure shows an example of a change in the state of the user interface, which is different from Figure 14. [Figure 16]This figure shows an example of various types of data stored in the memory of an MFP. [Figure 17] This figure shows an example of the data structure for a print job. [Figure 18] This flowchart shows an example of the procedure for printing a report from an MFP (Multifunction Printer). [Modes for carrying out the invention]

[0009] The image forming system 100 according to this embodiment will be described below with reference to the drawings. The image forming system 100 shown in Figure 1 includes an MFP (abbreviation for multifunction peripheral) 10 and a PC 30. The MFP 10 and the PC 30 are connected to a network 200 and can communicate with each other through the network 200. The network 200 is a LAN or the Internet. In this embodiment, the MFP 10 is an example of a printing device.

[0010] MFP10 includes a controller 11, a memory 12, a printer 13, a scanner 14, a FAX-IF 15, a network IF 16, a user IF 17, and a bus 18. IF is an abbreviation for interface. The network IF 16 connects the MFP10 to a network 200 in compliance with a predetermined network protocol. The user IF 17 is an interface interposed between a user who directly operates the MFP10 and the controller 11. The user IF 17 has a touch panel 17a and a key input unit 17b. The key input unit 17b is composed of a plurality of keys, for example, three keys, and can switch between a lit state and an unlit state for each key by, for example, switching a backlight on and off. The printer 13 executes a printing operation to print an image on a recording medium such as a sheet or a disk. As a recording method of the printer 13, an electrophotographic method, an inkjet method, or the like can be adopted. The scanner 14 executes a scanning operation to read an image recorded on a document and generate image data. The FAX-IF 15 executes a FAX operation to transmit and receive image data in a method compliant with a FAX protocol. Further, the MFP10 may be capable of executing a composite operation that combines a plurality of operations. A copy operation that combines a print operation by the printer 13 and a scan operation by the scanner 14 is an example of the composite operation.

[0011] The controller 11 consists of a CPU and an ASIC (Application Specific Integrated Circuit), and controls the operation of the printer 13, scanner 14, fax-IF 15, network IF 16, and user IF 17. The memory 12 has a data storage area. The data storage area is an area that stores data necessary for the execution of programs, etc. The memory 12 is composed of a combination of RAM, ROM, SSD, HDD, etc. Buffers provided by the controller 11, used when various programs are executed, may also be considered part of the memory 12. The memory 12 may also be a storage medium that the controller 11 can read. A storage medium that the controller 11 can read is a non-transitory medium. Non-transitory media include recording media such as CD-ROMs and DVD-ROMs, in addition to the examples above. Non-transitory media are also tangible media. On the other hand, electrical signals that carry programs downloaded from servers on the internet are a type of computer-readable signal medium, but they are not included in non-transitory computer-readable storage media.

[0012] The memory 12 stores firmware 20 as a program executable by the controller 11. In the present embodiment, the processing of the controller 11 according to the instructions described in the program is mainly illustrated. That is, processes such as "determination", "extraction", "selection", "calculation", "decision", "specification", "acquisition", "reception", and "control" in the following description represent the processing of the controller 11. Note that "acquisition" is used with a concept that does not require a request. That is, the process in which the controller 11 receives data without making a request is also included in the concept of "the controller 11 acquires data". Further, "data" in the present specification is represented by a bit string readable by the controller. Data having substantially the same semantic content but different formats shall be treated as the same data. The same applies to "information" in the present specification.

[0013] The firmware 20 also functions as a web server 21 for causing the PC 30 to display a predetermined web page. That is, it functions as an EWS (abbreviation for Embedded Web Server). The web server 21 can provide the web page to a later-described browser 41 of the PC 30 by transmitting data for displaying the web page to the PC 30. As will be described later, the MFP 10 can accept operations via the web page provided to the PC 30. That is, the web server 21 is an example of a user interface.

[0014] Further, the memory 12 stores setting values 25. Although referred to as setting value 25 for convenience, the setting values 25 include a large number of setting values. The MFP 10 executes various operation processes based on the setting values 25. The MFP 10 can perform communication using the network IF 16, for example, in accordance with network-related setting values included in the setting values 25. Further, the setting values 25 include setting values for a secure function lock. The secure function lock is a function that can restrict various operations of the MFP 10 for each user. In the present embodiment, details of operations that can be restricted by the secure function lock will be described later with reference to FIG. 3.

[0015] Next, the configuration of PC30 will be described. PC30 is equipped with a network interface 31, memory 32, controller 33, display 34, and user interface 35. The components 31, 32, 33, and 35 of PC30 have the same configuration as the controller 11, memory 12, network interface 16, and user interface 17 of MFP30, so their description will be omitted.

[0016] Memory 32 stores the OS 40 and the browser 41. The browser 41, under the control of the controller 33, can display images on the display 34 according to the web page data sent from the MFP 10.

[0017] The control processes performed by the image forming system 100 configured as described above will be explained in detail below with reference to Figures 2 to 18.

[0018] Figure 2 shows an example of the procedure by which PC30 obtains secure function lock setting screen data from MFP10. Hereafter, in the description of each process, the step will be denoted as "S".

[0019] The browser processing in Figure 2 shows the processing of PC 30 from the point where PC 30 is instructed to launch browser 41 and the browser screen is displayed on PC 30's display 34. When the logged-in user of PC 30, for example the administrator of MFP 10, enters the EWS URL into the browser screen, the controller 33 of PC 30 sends an EWS screen acquisition request to MFP 10 (S301). EWS is implemented by the processing of the controller 11 of MFP 10. At this time, the main processing in Figure 2 is the processing of the controller 11 as EWS. The main processing is started in response to the power being turned on of MFP 10.

[0020] When the controller 11 of the MFP10 receives an EWS screen acquisition request from the PC30, it sends EWS screen data corresponding to the request to the PC30 (S201). EWS screen data is a type of web page data. When the controller 33 of the PC30 receives the EWS screen data from the MFP10, it displays a browser screen based on the EWS screen data on the display 34. Hereafter, the browser screen based on web page data will also be simply referred to as the XX screen or XX page. The controller 33 of the PC30 waits until the administrator login password is entered into the login password input field provided in this EWS screen (S302: NO). Then, when the administrator login password is entered (S302: YES), the controller 33 sends an authentication request using the entered administrator login password to the MFP10 (S303).

[0021] When the MFP10 controller 11 receives an authentication request from the PC30, it performs the authentication (S202) and determines whether the entered administrator login password is correct or not (S203). If the entered administrator login password is incorrect (S203: NO), the controller 11 sends a login failure message to the PC30. On the other hand, if the entered administrator login password is correct (S203: YES), it sends the post-login page data of the EWS screen to the PC30 (S204).

[0022] When the controller 33 of PC30 receives post-login page data from MFP10, it displays the post-login page. The post-login page displays an operator corresponding to the secure function lock setting screen. When the administrator operates this operator, the controller 33 of PC30 sends a request to MFP10 to retrieve the secure function lock setting screen (S304).

[0023] When the controller 11 of the MFP10 receives a request from the PC30 to obtain the secure function lock setting screen, it sends the secure function lock setting screen data corresponding to the request to the PC30 (S205). When the controller 33 of the PC30 receives the secure function lock setting screen data from the MFP10, it displays the secure function lock setting screen.

[0024] Figure 3(a) shows an example of the secure function lock setting screen 340. The secure function lock setting screen 340 displays a cancel button 340A, a send button 340B, and radio buttons 340C and 340D. Radio button 340C is the button operated to disable the secure function lock, i.e., to "Off". Radio button 340D is the button operated to enable the secure function lock, i.e., to "On". The cancel button 340A is the button that instructs the user to discard the setting changes made to the secure function lock setting screen 340. The send button 340B is the button that instructs the user to send the setting changes made to the secure function lock setting screen 340 to the MFP10. Radio button 340D is an example of an operation object.

[0025] Figure 3(a) shows the secure function lock setting screen 340 based on secure function lock setting screen data sent from MFP10, where the secure function lock is disabled. Radio button 340C is selected on the secure function lock setting screen 340. When the administrator selects radio button 340D and the send button 340B, a message is sent from PC30 to MFP10 indicating that the secure function lock has been switched from disabled to enabled. In response, the controller 11 of MFP10 changes the setting value of the secure function lock in setting value 25 from disabled to enabled. Then, the controller 11 generates the screen data for the secure function lock setting screen 340' shown in Figure 3(b) and sends it to PC30.

[0026] When the controller 33 of the PC30 receives this screen data from the MFP10, it displays the secure function lock setting screen 340'. The secure function lock setting screen 340' differs from the secure function lock setting screen 340 in that radio button 340D is selected. Furthermore, the secure function lock setting screen 340' displays the message "Please configure detailed security settings for the print job," and adds radio buttons 340E and 340F that indicate whether to disable or enable the detailed security settings for the print job.

[0027] When the administrator selects radio button 340F and the send button 340B, a message is sent from PC30 to MFP10 indicating that the print job's detailed security settings have been switched from disabled to enabled. In response, the controller 11 of MFP10 changes the setting value of the print job's detailed security settings within setting value 25 from disabled to enabled. The controller 11 then generates the screen data for the secure function lock setting screen 340″ shown in Figure 3(c) and sends it to PC30. Radio button 340F is also an example of an operation object.

[0028] When the controller 33 of the PC30 receives this screen data from the MFP10, it displays the secure function lock setting screen 340″. The secure function lock setting screen 340″ differs from the secure function lock setting screen 340′ in that it includes a print job group setting field 341 and a user permission assignment setting field 342.

[0029] The administrator can assign a group name to a permission number, which in the example shows an integer value from 1 to 6, by manipulating the print job group settings field 341. Then, for each permission number, permissions can be set for displaying a list of print jobs, printing, deleting from the print job list, canceling during reception, and canceling during printing. "Displaying a list of print jobs" means displaying, for example, screen 17aG shown in Figure 13(c) on the MFP10's touch panel 17a. "Printing" means printing a print job. "Deleting from the print job list" means deleting some or all print jobs from the print job list 17aG2 displayed on screen 17aG shown in Figure 13(c), for example. "Cancelling during reception" means canceling the reception of a print job while it is being received. "Cancelling during printing" means canceling the printing of a print job or main report while it is being printed. In this embodiment, the main unit report is a report for managing the MFP10, and for example, it is a report that informs the administrator of the remaining toner level of the MFP10, the number of pages printed, and the usage status of each function.

[0030] Permissions are set using four types of symbols: "○", "×", "△", and "▲". "○" indicates permission. "×" indicates prohibition. "△" indicates a warning. "▲" also indicates a warning, but with "△", permission can be granted after the warning, whereas with "▲", only a warning is issued and permission cannot be granted after the warning. Administrators can set permissions for processing and operations on print jobs by specifying one of these four types of symbols. Here, permission is a restriction on processing and operations on print jobs. The four types of symbols "○", "×", "△", and "▲" are examples of restriction information. Note that restrictions on processing and operations on print jobs are restrictions on others, not on oneself.

[0031] The administrator can assign permissions to users who can log in to the MFP10 by manipulating the user permission assignment setting field 342. In this embodiment, users who can log in are specified by username, and permissions are specified by permission number. In the secure function lock setting screen 340, "admin," i.e., the administrator, is assigned permission number "1," "suzuki" is assigned permission number "3," and "kato" is assigned permission number "2." The username is an example of user information.

[0032] In this way, the administrator performs operations on the print job group settings field 341 and the user permission assignment settings field 342 on the secure function lock settings screen 340, and then selects the send button 340B. As a result, the settings in the print job group settings field 341 and the user permission assignment settings field 342 are sent from the PC 30 to the MFP 10. In response, the controller 11 of the MFP 10 updates the settings in the print job group settings field 341 and the user permission assignment settings field 342, which are included in the detailed security settings for the print job within setting value 25, with the new settings.

[0033] The following explanation assumes that the secure function lock setting is stored as a setting value 25 in the memory 12 of the MFP10, in the state shown in Figure 3(c). Under this assumption, when the MFP10 is powered on, the controller 11 executes an initialization process (not shown) and starts the user interface operation process shown in Figure 6, the display process shown in Figures 8 and 9, and the receive and print process shown in Figures 4 and 5.

[0034] When the display process begins, in Figure 8, the controller 11 first displays the home screen on the touch panel 17a (S61). Figure 12(a) shows an example of the home screen (screen ID=100) 17aA displayed on the touch panel 17a. The home screen 17aA consists of a “Public” button 17aA1 and a function selection area 17aA2 for selecting one of the MFP 10’s FAX, copy, or scan functions. A screen ID is associated with each screen displayed on the touch panel 17a, and the screen display on the touch panel 17a switches according to the screen ID change. The screen ID is written by the controller 11 to a screen ID storage area (not shown) located in the memory 12 during S3, etc., which will be described later in the reception and printing process.

[0035] Furthermore, when user interface operation processing begins, in Figure 6, the controller 11 first determines whether or not it has detected a user operation on the user interface 17 (S31). If, in this determination, no user operation is detected (S31: NO), the controller 11 then determines whether or not the screen ID has changed (S42). If, in this determination, the screen ID has not changed (S42: NO), the controller 11 returns to processing S31. The controller 11 then repeatedly performs the determinations in S31 and S42 until a user operation is detected (S31: YES) or the screen ID changes (S42: YES). Note that user operations on the user interface 17 include touch operations on the touch panel 17a of the user interface 17 and key operations on the key input section 17b of the user interface 17.

[0036] For example, when the home screen 17aA is displayed on the touch panel 17a, if the “Public” button 17aA1 is touched, the controller 11 determines “YES” in S31, and then determines whether the user operation is a key operation on the key input unit 17b (S32). In this case, the user operation is a touch operation on the touch panel 17a (S32: NO), so the controller 11 notifies the display process of the touch operation (S41). This notification is done, for example, by storing it in a touch operation storage area (not shown) provided on the memory 12. The information stored in the touch operation notification storage area as a touch operation notification is, for example, the touch position on the touch panel 17a.

[0037] In the above display process, after processing S61, the controller 11 determines whether or not it has detected a key notification or a touch operation notification (S62). Key notifications are made in S36, etc., described later within the user IF operation process. Specifically, key notifications are made by storing them in a key notification storage area (not shown) provided on the memory 12, similar to the touch operation notification. However, unlike touch operation notifications, the information stored in the key notification storage area as a key notification is information that identifies which of the three keys of the key input unit 17b was operated. Thus, key notifications are stored in the key notification storage area and touch operation notifications are stored in the touch operation notification storage area, so in S62, the controller 11 determines 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.

[0038] If, in the determination in S62 above, neither a key notification nor a touch operation notification is detected (S62:NO), the controller 11 determines whether the screen ID written to the screen ID storage area has changed (S65). If, in this determination, the screen ID has not changed (S65:NO), the controller 11 further determines whether a home screen display notification has been detected (S67). If, in this determination, a home screen display notification has not been detected (S67:NO), the controller 11 further determines whether a picture data list screen display notification has been detected (S68). If, in this determination, a picture data list screen display notification has not been detected (S68:NO), the controller 11 returns to processing in S62. After processing in S61, the controller 11 repeatedly performs the decisions in S62, S65, S67, and S68 until a key notification or touch operation notification is detected (S62: YES), until the screen ID changes (S65: YES), until a home screen display notification is detected (S67: YES), or until a picture data list screen display notification is detected (S68: YES).

[0039] In the display process, while the controller 11 is repeatedly making the decisions in S62, S65, S67, and S68, suppose that a touch operation of the "Public" button 17aA1 is notified by the process in S41. In this case, the controller 11 determines "YES" in S62, and then determines whether the operation is a press of the home key 17b2 (see Figure 12(a)) among the three keys of the key input unit 17b, and whether the pressability information for the home key 17b2 is "OK" (S63).

[0040] Figure 16(b) shows an example of table data 25b that indicates the screen and key press permissions according to the internal state of the MFP 10. The table data 25b consists of the internal state of the MFP 10, a screen ID, and key press permissions. The screen ID is an ID that identifies the screen to be displayed on the touch panel 17a of the user IF 17 in that internal state. The key press permissions information indicates whether the three keys provided on the key input section 17b of the user IF 17, specifically the back key 17b1, home key 17b2, and cancel key 17b3, are enabled (OK in Figure 16(b)) or disabled (NG in Figure 16(b)). The table data 25b is registered, for example, as a setting value 25 in the memory 12. Note that when the internal state of MFP10 is "receiving print command", there is no screen ID (-). This is because the time during which the internal state of MFP10 is "receiving print command" is extremely short, making it unnecessary to switch the touch panel 17a screen to the "receiving print command" screen. Of course, this is not the only option; a screen ID can be determined to identify the "receiving print command" screen, and the "receiving print command" screen can be displayed accordingly. Also, as shown in Figure 16(c), display screen data 25c is stored in memory 12, associated with each screen ID.

[0041] The internal state of the MFP10 is determined by a set of internal states defined in advance. The controller 11 selects a state from the defined internal states that matches the current state and stores information indicating the internal state in an internal state storage area (not shown) located on the memory 12. Therefore, the internal state of the MFP10 is the internal state for which information is stored in the internal state storage area on the memory 12. The controller 11 writes information indicating the internal state to the internal state storage area on the memory 12 as needed when it is necessary to switch from the current internal state to another internal state.

[0042] Returning to Figure 8, since a touch operation notification has been detected instead of a key notification, the controller 11 determines "NO" in S63 and checks the currently displayed screen (S64). Specifically, this check is performed by checking the screen ID written to the screen ID storage area. Then, the controller 11 determines whether or not a warning screen is being displayed based on the screen it has checked (S71 in Figure 9). Currently, the home screen is being displayed and a warning screen is not being displayed, so the controller 11 determines "NO" in S71. Furthermore, since neither a warning key notification nor a warning-only key notification has been detected, the controller 11 determines "NO" in S72 and also determines "NO" in S73. Then, the controller 11 determines whether or not a process that should notify user operation is being executed (S74). If the screen ID checked in S64 is 100, the controller 11 determines "NO", and if the screen ID is 101 to 105, it determines "YES". In other words, if the screen ID is 101 to 105, the controller 11 determines that the above-mentioned receiving and printing process (Figures 4 and 5) is in progress as a process that should notify the user of user operation. Currently, the screen ID is 100, so the controller 11 determines "NO" in S74 and notifies the user of a screen update and / or the start of processing according to the key for key notification or the touch position for touch operation notification (S76). Since the touch operation of the "Public" button 17aA1 instructs the start of the login process shown in Figures 10 and 11, the controller 11 updates the screen according to the touch position and notifies the user of the start of the login process in S76.

[0043] In response, the controller 11 initiates the login process shown in Figures 10 and 11, and first displays a list of logged-in users on the touch panel 17a (S91).

[0044] Figure 13(a) shows an example of a user selection screen 17aE displayed on the touch panel 17a. The user selection screen 17aE consists of a display area 17aE1 that displays instructions for user selection (for example, "Select User") and a user list display area 17aE2 that displays a list of users. The operator of the MFP10 can proceed to login authentication by selecting their own username from the users displayed in the user list display area 17aE2.

[0045] Figure 16(a) shows an example of a user DB25a for login management and function restriction management. DB is an abbreviation for database. User DB25a is created, for example, by the administrator who manages MFP10 and stored in memory 12 of MFP10. User DB25a consists of the following items: main LoginUser name, PIN, and Function.

[0046] The "Main LoginUser name" is the username used when logging into the MFP10. In S91 above, the list of users displayed on the touch panel 17a is a list of Main LoginUser names registered in the user DB 25a.

[0047] PIN stands for Personal Identification Number, which is a type of personal identification number. The PIN is registered in advance along with the main unit's LoginUser name and is used for login authentication on the MFP10.

[0048] The Function field contains information for managing the above-mentioned function restrictions, indicating whether the user whose main LoginUser name is registered can use the print, scan, and copy functions (Print, Scan, and Copy in Figure 16(a)). In other words, the user whose main LoginUser name is registered can use functions marked "OK," but cannot use functions marked "NG." For example, a user whose main LoginUser name is "suzuki" can use the print and scan functions of the MFP10 when logged in, but cannot use the copy function of the MFP10.

[0049] Returning to Figure 10, the controller 11 waits, for example, until a user is selected from among the users displayed in the user list display area 17aE2 (S92: NO). Once a user is selected (S92: YES), the controller 11 displays a PIN input screen on the touch panel 17a (S93). Figure 13(b) shows an example of the PIN input screen 17aF. The PIN input screen 17aF consists of a PIN input area 17aF1, a numeric keypad display area 17aF2, and an OK button 17aF3.

[0050] Next, the controller 11 waits until the PIN input is complete (S94: NO), and once the PIN input is complete (S94: YES), it determines whether the entered PIN is correct (S95). To determine whether the PIN input in S94 is complete, it is necessary to determine whether the numeric keypad displayed in the numeric keypad display area 17aF2 has been touched, resulting in the PIN being entered into the PIN input area 17aF1 and the OK button 17aF3 being touched.

[0051] In the judgment of S95, if the entered PIN is correct (S95: YES), the controller 11 saves the login username, i.e., the selected main unit LoginUser name, in the memory 12 (S96). Then, the controller 11 determines whether or not the setting to not display the print job list has been made (S101 in Figure 11). The setting to not display the print job list means, for example, that the print job list display screen 17aG shown in Figure 13(c) is not displayed on the touch panel 17a. The setting to not display the print job list can be registered in the memory 12 as a setting value 25.

[0052] In the determination in S101, if the setting to not display the list of print jobs is enabled (S101:YES), the controller 11 determines whether or not the image data accumulated by the logged-in user is in memory 12 (S102). Hereafter, the selected main LoginUser name will be referred to as "selected LoginUser name". The controller 11 determines whether or not image data associated with a main LoginUser name that matches the selected LoginUser name is accumulated. In S6 of Figure 4, the controller 11 stores the image data in association with the main LoginUser name that indicates the user who sent the underlying print job. More details will be described later.

[0053] In the determination of S102, if the image data accumulated by the logged-in user, i.e., the user indicated by the selected LoginUser name, specifically the image data based on print jobs containing the selected LoginUser name, which will be described later, is stored in memory 12 during the reception and print process (S102: YES), the controller 11 notifies the reception and print process of the instruction to print the accumulated image data (S103), and then terminates the login process.

[0054] Note that when processing proceeds from S102 to S103, there may be multiple image data files accumulated by the logged-in user. In this case, all image data should be printed.

[0055] On the other hand, in the determination in S102 above, if there is no image data accumulated by the logged-in user (S102: NO), the controller 11 performs a display process for the home screen display notification (S104) and then terminates the login process. In the display process in S67 (Figure 8), when the controller 11 detects this home screen display notification (S67: YES), it returns the process to S61 and displays the home screen on the touch panel 17a (S61). At this time, the controller 11 determines whether the selected LoginUser name is stored in memory 12, and if the selected LoginUser name is stored, it displays the logged-in home screen on the touch panel 17a. Figure 14(b) shows an example of the logged-in home screen 17aI displayed on the touch panel 17a. The logged-in home screen 17aI consists of a display area 17aI1 that displays the selected LoginUser name and a function selection area 17aI2. When the selected LoginUser name displayed in the display area 17aI1 of the logged-in home screen 17aI is touched, the controller 11 displays a logout confirmation screen on the touch panel 17a.

[0056] Figure 14(c) shows an example of the logout confirmation screen 17aJ. The logout confirmation screen 17aJ consists of a display area 17aJ1 that asks if the user intends to log out, a YES selection area 17aJ2 for selecting YES, and a NO selection area 17aJ3 for selecting NO. When the user performs a logout operation by touching the YES selection area 17aJ2, the controller 11 deletes the selected LoginUser name stored in the memory 12. The controller 11 then switches the screen of the touch panel 17a from the logout confirmation screen 17aJ in Figure 14(c) to the home screen 17aA in Figure 12(a).

[0057] Returning to Figure 11, if the setting to disable the display of the print job list is not set in the judgment of S101 (S101: NO), the controller 11 determines whether the logged-in user has permission to display the print job list of other users (S105). The permission to display the print job list is set for each group in the print job group setting field 341 shown in Figure 3(c). For example, if the logged-in user is "suzuki", permission number 3 is assigned, so the selected LoginUser name "suzuki" has permission to display the print job list. Therefore, in this case, the controller 11 determines "YES" in S105 and determines whether there is accumulated image data including the logged-in user and others, that is, image data based on print jobs containing the selected LoginUser name "suzuki" and image data based on print jobs containing user names other than the selected LoginUser name "suzuki" that have been accumulated in memory 12 during the reception and printing process (S106). In this determination, if there is stored image data including the logged-in user and other users (S106: YES), the controller 11 notifies the display process to display the image data list screen (S107). In the display process, the controller 11 detects the notification to display the image data list screen (S68: YES) and displays the image data list screen on the touch panel 17a (S69).

[0058] Figure 13(c) shows an example of the image data list screen 17aG displayed on the touch panel 17a. The image data list screen 17aG consists of a display area 17aG1 that displays instructions for selecting a print job, i.e., image data (for example, a display that says "Select Print Job"), an image data list display area 17aG2 that displays a list of image data, and an OK button 17aG3. The logged-in user, "suzuki," can select the image data they want to print from the image data displayed in the image data list display area 17aG2 and then select the OK button 17aG3 to print the selected image data. After that, the controller 11 displays the home screen on the touch panel 17a. Alternatively, when the image data list screen 17aG is displayed on the touch panel 17a, the image data displayed in the image data list display area 17aG2 may be printed immediately without any selection operation.

[0059] Returning to Figure 11, in the determination at S106, if there is no stored image data including the logged-in user and other users (S106: NO), the controller 11 notifies the display process to display the home screen (S108). In the display process, the controller 11 detects the home screen display notification (S67: YES) and displays the home screen (S61).

[0060] On the other hand, if the judgment in S105 indicates that the logged-in user does not have permission to view the print job list of others (S105: NO), the controller 11 determines whether or not there is any image data stored by the logged-in user (S109). If the judgment indicates that there is any image data stored by the logged-in user (S109: YES), the controller 11 notifies the display process to display the target image data list screen (S110). In the display process, the controller 11 detects the notification to display the image data list screen (S68: YES) and displays the image data list screen on the touch panel 17a (S69). On the other hand, if the judgment in S109 indicates that there is no image data stored by the logged-in user (S109: NO), the controller 11 notifies the display process to display the home screen (S111). In the display process, the controller 11 detects the notification to display the home screen (S67: YES) and displays the home screen (S61).

[0061] Furthermore, the image data list screen 17aG may be displayed on the touch panel 17a by selecting the security print icon 17aA23 shown in Figure 13(d), rather than through the login process. The security print icon 17aA23 can be made to appear in the function selection area 17aI2, for example, by operating the left key 17aI21 or the right key 17aI22 displayed in the function selection area 17aI2 of the logged-in home screen 17aI, and then selected.

[0062] Figure 18 shows the procedure for sending a main unit report print command from PC 10 to MFP 10. As mentioned above, the main unit report is a report for managing MFP 10, and is used to inform the administrator of information such as the remaining toner level of MFP 10, the number of pages printed, and the usage status of each function. As each function is executed, MFP 10 stores information indicating the usage status in memory 12. MFP 10 may also select the information to print according to the information included in the main unit report print command that indicates which usage status should be printed as a main unit report.

[0063] The procedure shown in Figure 18 is the same as the procedure shown in Figure 2 up to S204. Therefore, in Figure 18, the same step numbers are used for steps that are the same as those in Figure 2, and their explanations are omitted as appropriate.

[0064] In Figure 18, when PC10 receives the post-login page data from MFP10, it displays the post-login page on the browser screen. The post-login page displays an operator that sends a main report print command to MFP10. When the administrator operates this operator, PC10 sends the main report print command to MFP10 (S314).

[0065] When the MFP10's controller 11 receives a main report print command from the PC10, it notifies the next described receiving and printing process of the external main report print command (S215). Since the notification to the MFP10 is based on an operation by the administrator, it can be said that the main report print command is a print command associated with the administrator user. In this specification, the main report print command and the print job are described separately, but the main report print command is an example of a print job. Printing a main report based on a main report print command is an example of printing based on a print job. In other words, the main report print command is an example of a print job associated with the user.

[0066] Figures 4 and 5 illustrate the procedure for receiving and printing. In Figure 4, the controller 11 first determines whether or not it has started receiving a print job (S1). Specifically, the controller 11 determines whether or not data is stored in the receive buffer, and if so, determines whether or not that data is a print job, and if it is a print job, determines whether or not the beginning of that print job is stored. The receive buffer is, for example, provided on memory 12 and is an area that stores data received from outside the MFP 10 via the network IF 16, etc. Note that the data stored in the receive buffer is not limited to data from outside the MFP 10; various notifications that the controller 11 makes for receiving and printing may also be stored in the receive buffer. For example, the notification in S103 (Figure 11) may be made by storing information that identifies the image data to be printed, specifically information indicating the location where the image data is stored, in the receive buffer.

[0067] Figure 17 shows an example of the data structure of print job 300. As shown in Figure 17, print job 300 has a structure in which PDL is enclosed by PJL. PDL is an abbreviation for page description language, and PJL is an abbreviation for printer job language. The beginning of print job 300 is " <esc>The end of print job 300 is indicated by "%-12345X@PJL" <esc>This is indicated by "%-12345X". Therefore, if the print job to be received in S1 is print job 300, the controller 11 determines from the received data whether or not it has started receiving the print job. <esc>The determination is based on whether or not "%-12345X@PJL" is detected. In addition, the print job 300 also contains information such as the print job name test.txt, the username suzuki, and the creation date and time 20210413201010. Note that the data structure of the print job received by the MFP10 may differ from the data structure of print job 300, but in this embodiment, for the sake of explanation, it is assumed that the MFP10 receives a print job with the same data structure as print job 300.

[0068] Returning to Figure 4, if the determination in S1 above indicates that the reception of a print job has begun (S1: YES), the controller 11 determines whether the print job corresponds to a registered main unit LoginUser name (S2). Specifically, if the username included in the print job matches any of the main unit LoginUser names registered in user DB 25a (Figure 16(a)), the determination is "YES". Note that the same user may use different usernames for MFP10 and PC10, but for the sake of explanation in this embodiment, we will assume that the same username is used.

[0069] In S2's determination, if the print job that has started to be received is the print job corresponding to a registered main unit LoginUser name (S2: YES), the controller 11 displays the receiving screen on the touch panel 17a of the user IF 17 (S3).

[0070] The table data 25b above shows two types of internal states for the MFP 10 indicating that a print job is being received: "Print job being received" and "Print job being received (Printer logged in)". Therefore, when receiving a print job begins (S1:YES), the controller 11 needs to determine which of these internal states applies before proceeding to S2, for example. In other words, the controller 11 determines whether the print job was started to be received while the printer was logged in. If there is a logged-in user, the selected LoginUser name is stored in memory 12 as explained in S76 (Figure 10) of the login process above, so the controller 11 determines whether the selected LoginUser name matches the username included in the print job. If the selected LoginUser name matches the username included in the print job, the controller 11 writes "Print job being received (Printer logged in)" to the internal state storage area. On the other hand, if the selected LoginUser name does not match the username included in the print job, the controller 11 writes "Print job being received" to the internal state storage area.

[0071] In step S3 in Figure 4, the controller 11 displays the receiving screen on the touch panel 17a. Specifically, the controller 11 writes either screen ID "101" or "105" to the screen ID storage area. Here, the decision of whether to write "101" or "105" as the screen ID to the screen ID storage area is determined based on the internal state of the MFP 10. In other words, the controller 11 refers to the table data 25b and, if the internal state of the MFP 10 is "receiving a print job", writes screen ID "101" to the screen ID storage area. On the other hand, if the internal state of the MFP 10 is "receiving a print job (printer logged in)", writes screen ID "105" to the screen ID storage area.

[0072] In the above display process (Figures 8 and 9), when the controller 11 has not detected either a key notification or a touch operation notification (S62: NO), it determines whether the screen ID written to the screen ID storage area has changed (S65). If the screen ID has changed (S65: YES), the controller 11 reads the display screen data associated with the changed screen ID from the memory 12 and updates the screen by displaying it on the touch panel 17a (S66).

[0073] Furthermore, in the user interface operation process described above (Figure 6), the controller 11 determines whether the screen ID written to the screen ID storage area has changed (S42) if it has not detected any user operation (S31: NO). If the screen ID has changed (S42: YES), the controller 11 checks the internal state of the MFP 10 (S43) and determines which keys can be pressed based on the settings in the print job group setting field 341 and the user permission assignment setting field 342 (S44). The controller 11 then lights up the keys that can be pressed and turns off the others (S45).

[0074] Figure 12(b) shows an example of a receiving screen (screen ID=101) 17aB displayed on the touch panel 17a. The receiving screen 17aB consists of a display area 17aB1 that displays the internal state of the MFP 10 and a display area 17aB2 that displays the operating state of the MFP 10. Figure 15(b) shows an example of a receiving screen (screen ID=105) 17aL displayed on the touch panel 17a. Similar to the receiving screen 17aB, the receiving screen 17aL consists of a display area 17aL1 that displays the internal state of the MFP 10 and a display area 17aL2 that displays the operating state of the MFP 10. Although the screen IDs are different, the content displayed on the screens of the receiving screen 17aB in Figure 12(b) and the receiving screen 17aL in Figure 15(b) are the same. Furthermore, the illumination / exit states of the three keys 17b1 to 17b3 on the key input section 17b are the same in Figure 12(b) and Figure 15(b). However, the screen transitions on the touch panel 17a in response to pressing the cancel key 17b3, which is illuminated on the key input section 17b, may differ. Details of this will be described later.

[0075] Returning to Figure 4, the controller 11 then determines whether the stash printing function is enabled or disabled (S4). The stash printing function is a function that stores received print jobs in memory 12 and then prints them in response to user login. In this embodiment, an example is described in which RIP processing is performed on the received print job, the generated image data is stored in memory 12, and then printing is performed in response to user login (see S5 and S6 below). However, the concept of the stash printing function also includes storing the received print job directly in memory and then printing it in response to user login. RIP is an abbreviation for raster image processor. Furthermore, the stash printing function can be enabled or disabled by selecting the option through various settings on the MFP 10. Alternatively, the option to enable or disable the stash printing function can be performed by the PC 10 via the network IF 16.

[0076] In the determination made in S4 above, if the storage print function is enabled (S4:YES), the controller 11 processes the print data included in the print job using RIP (S5), and stores the RIP-processed image data in a predetermined area on the memory 12, associated with the username of the user who sent the original print job (S6).

[0077] Next, the controller 11 determines whether or not the accumulation of image data into memory 12 is complete (S7). If the accumulation of image data into memory 12 is not yet complete (S7: NO), the controller 11 determines whether or not it has received a cancel key notification (S8). If it has not received a cancel key notification (S8: NO), the controller 11 returns to processing S7. On the other hand, if the controller 11 determines in S8 that it has received a cancel key notification (S8: YES), the controller 11 cancels the accumulation of image data into memory 12 midway through (S9) and then proceeds to processing S16. In S16, the controller 11 displays the home screen on the touch panel 17a in the same manner as in S61 (Figure 8). After that, the controller 11 returns to processing S1.

[0078] Furthermore, if the controller 11 is receiving a print job and processing it using RIP to store image data, it will not only cancel the storage but also cancel the reception of the print job. Here, the cancellation key notification is performed in the process from S35 onwards if the cancel key 17b3 can be pressed in the user interface operation process (Figure 6) described above (S34: YES). The control of the cancellation key notification will be explained below based on the user interface operation process and related processes within the display process.

[0079] In the determination in S32 in Figure 6, if the detected user operation is a key operation on the key input unit 17b (S32: YES), the controller 11 checks the internal state stored in the internal state storage area (S33). Next, the controller 11 refers to the table data 25b (Figure 16(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 25b, if the current internal state is "receiving a print job (printer logged in)", the pressability of both the back key 17b1 and the home key 17b2 on the key input unit 17b is "NG". However, the pressability of the cancel key 17b3 is "OK". Therefore, in this case, the controller 11 determines that the key operation of the cancel key 17b3 is an operation that can be pressed (S35: YES), and proceeds to S35 to S36.

[0080] In S36, the controller 11 notifies the display process of the cancel key (S36), and then returns the process to S31. In the display process that has been notified of the cancel key, the controller 11 will notify the receive & print process of the cancel key (S62: YES, S63~S73: NO, S74: YES: S75). In the receive & print process, the controller 11 receives the cancel key notification (S8: YES) and cancels the accumulation of image data midway (S9).

[0081] Note that there are two types of presses for the cancel key 17b3: a short press and a long press. For example, if the current internal state is "receiving print jobs (printer logged in)", the controller 11 may be in the process of RIP processing and accumulating one of the multiple jobs that have been sent. In this case, a short press of the cancel key 17b3 will cause the controller 11 to cancel the accumulation of the one print job that is currently being accumulated. On the other hand, a long press of the cancel key 17b3 will cause the controller 11 to cancel the reception of the one print job that is currently being accumulated, and also cancel the reception of any remaining print jobs that were newly received while the key was being held down. In other words, if multiple print jobs are received while the key is being held down, the reception of all of those print jobs will be canceled. The ability to press the cancel key 17b3 in S34 (Figure 6) above applies to both short and long presses. Note that, as mentioned above, if the controller 11 is accumulating image data based on a job while receiving a job, the reception of that job will also be canceled, regardless of whether the key operation is a short press or a long press.

[0082] On the other hand, when the process proceeds to S34 above, in the table data 25b, the pressability of the back key 17b1 and home key 17b2 on the key input section 17b is "NG", similar to when the current internal state is "receiving print job" or "receiving print job (printer logged in)". However, the pressability of the cancel key 17b3 is determined according to the security settings. Here, the security settings refer to the secure function lock settings described above based on Figure 3. Now, we assume that the detailed security settings for the print job shown in Figure 3(c) have been set as the secure function lock settings, as described above.

[0083] If the currently logged-in username for MFP10, i.e., the selected LoginUsername, is "suzuki", then "▲" is set as a cancellation during reception. Here, as mentioned above, "▲" indicates that only a warning is issued and permission cannot be granted after the warning. Therefore, the permission to press the cancel key 17b3 is "OK", so in this case, if the key operation is the cancel key 17b3, the judgment in S34 will be "YES". In the following S35, the controller 11 determines whether the key operation is the pressing of the cancel key 17b3 for a print job corresponding to the selected LoginUsername (S35). Since the current internal state of MFP10 is "receiving print jobs", the controller 11 determines "NO" in S35. As a result, the controller 11 proceeds from S35 to S37. In S37, the controller 11 determines whether the key operation is the pressing of the cancel key 17b3 for a print job corresponding to a username different from the selected LoginUsername. In this decision, the controller 11 determines "YES" and executes the cancel key press process (38), and then returns the process to S31.

[0084] Figure 7 shows the detailed procedure for pressing the cancel key in S38. In Figure 7, if the detailed security setting for the print job is Off (S51: YES), that is, if the setting value 25 includes the setting value corresponding to the selection of radio button 340E in Figure 3, the controller 11 notifies the display process of the warning key (S52) and then terminates the cancel key press process. As a result, in S78 of the display process, the warning screen 17aC shown in Figure 12(c) is displayed. Thus, when the detailed security setting for the print job is Off (S51: YES), regardless of whether "○", "×", "△", or "▲" is set as the cancellation during reception, the controller 11 executes the process as when "△" is set, that is, the process of notifying the display process of the warning key (S52).

[0085] On the other hand, if the detailed security setting for the print job is On (S51: NO), that is, if the setting value 25 includes the setting value corresponding to the selection of radio button 340F in Figure 3, the controller 11 determines whether a warning is necessary for the target user indicated by the selected LoginUser name (S53). At this time, the selected LoginUser name is "suzuki" and "▲" is set as the cancellation during reception, so the controller 11 determines "YES" in S53. Furthermore, at this time, the controller 11 determines that cancellation after the warning is not possible (S54: NO), notifies the display process of the warning-only key (S56), and then terminates the cancel key press process. As a result, in S77 of the display process, only the warning shown in Figure 12(d) is displayed on screen 17aD.

[0086] In contrast, when the selected LoginUsername is "admin", the selected LoginUsername "admin" has "△" set as the authority to cancel a print job while it is being received. Therefore, in the judgment in S53, it is determined to be "YES", and the controller 11 proceeds to S54. In S54, the controller 11 determines that the target user, the selected LoginUsername "admin", can cancel after the warning (S54: YES), notifies the display process to press the warning key (S55), and then terminates the cancel key press process. As a result, in S78 of the display process, the warning screen 17aC shown in Figure 12(c) is displayed.

[0087] Furthermore, in the case of the selected LoginUsername "kato", the selected LoginUsername "kato" has "×" set as the permission for canceling a print job while it is being received. Therefore, in the judgment of S53, it is determined to be "NO", and the controller 11 proceeds to S57. In S57, the controller 11 determines that the target user, selected LoginUsername "kato", cannot cancel (S57: NO), sounds a rejection sound (S59), and then terminates the cancel key press process.

[0088] Note that in the group settings section 341 of the print job shown in Figure 3(c), "○" is not set as the permission to cancel a print job while it is being received. However, if "○" were set as the permission to cancel a print job while it is being received, the judgment in S53 would be "NO" and the judgment in S57 would be "YES". For this reason, the controller 11 notifies the display process of the cancel key press (S58) and then terminates the cancel key press process.

[0089] In S52 or S55, when the controller 11 notifies the display process of a warning key, the controller 11 detects the notification of the warning key (S72: YES in Figure 9) and displays a warning screen on the touch panel 17a (S78). Figure 12(c) shows an example of the warning screen 17aC displayed on the touch panel 17a. The warning screen 17aC displays the warning message, "You are not the owner of the print job. Are you sure you want to cancel? Press [OK] if you want to proceed." Furthermore, the warning screen 17aC displays an OK button 17aC1 and a Cancel button 17aC2. When the OK button 17aC1 is selected, the controller 11 determines "YES" in S83 and notifies the receiving & printing process of a Cancel key, which is the process in operation corresponding to the screen before the warning (S84), and then displays the home screen on the touch panel 17a (S61 in Figure 8). In the receiving and printing process, the controller 11 receives a cancellation key notification (S8:YES) and cancels the accumulation of image data midway (S9). On the other hand, if the cancel button 17aC2 is selected, the controller 11 determines "NO" in S83, redisplays the screen before the warning (S82), and then proceeds to S62 in Figure 8. In this case, the controller 11 does not receive a cancellation key notification in the receiving and printing process, so S8:YES does not occur, and the accumulation of image data is completed (S7:YES). In this way, even if someone else presses the cancel key 17b3 while receiving a print job for accumulation printing, the receipt of the print job is not immediately canceled. In this way, it is possible to suppress cancellation operations by others.

[0090] On the other hand, in S56, when the controller 11 notifies the display process of a warning-only key, the controller 11 detects the notification of the warning-only key in the display process (S73:YES) and displays a warning-only screen on the touch panel 17a (S77). Figure 12(d) shows an example of the warning-only screen 17aD displayed on the touch panel 17a. The warning-only screen 17aD displays the warning message, "You are not the owner of the print job. You cannot cancel." Furthermore, the warning-only screen 17aD displays a close button 17aD1. When the close button 17aD1 is selected, the controller 11 determines "YES" in S81 and redisplays the screen before the warning (S82), and then proceeds to S62 in Figure 8. At this time, in the receive & print process, the controller 11 does not receive a cancel key notification, so S8:YES does not occur, and the accumulation of image data is completed (S7:YES).

[0091] Furthermore, in S58, when controller 11 notifies the display process of the cancel key, controller 11 will then notify the receive & print process of the cancel key during the display process (S62: YES, S63~S73: NO, S74: YES: S75). During the receive & print process, controller 11 receives the cancel key notification (S8: YES) and cancels the accumulation of image data midway (S9).

[0092] On the other hand, if the judgment in S4 above indicates that the storage print function is disabled (S4:NO), the controller 11 processes the print data included in the print job using RIP in the same manner as in S5 above (S10). Then, the controller 11 displays the printing screen on the touch panel 17a of the user IF 17 (S11). Specifically, the controller 11 writes screen ID "103" to the screen ID storage area in memory 12. Before performing the process in S11, the controller 11 writes "Printing image data" to the internal state storage area. As a result, in S11, the controller 11 refers to the table data 25b and writes screen ID "103" when the internal state is "Printing" to the screen ID storage area, so the printing screen is displayed on the touch panel 17a. Figure 14(a) shows an example of the printing screen (screen ID=102,103) 17aH displayed on the touch panel 17a. The printing screen 17aH consists of a display area 17aH1 that displays the internal status of the MFP 10 and a display area 17aH2 that displays the operating status of the MFP 10. Furthermore, the controller 11 starts printing by outputting the image data after RIP processing to the printer 13 (S12).

[0093] Next, the controller 11 determines whether or not printing is complete (S13). If printing is not complete (S13:NO), the controller 11 determines whether or not it has received a cancellation key notification, in the same manner as in S8 above (S14). If it does not receive a cancellation key notification (S14:NO), the controller 11 returns to processing S13. On the other hand, if a cancellation key notification is received in the determination in S14 (S14:YES), the controller 11 cancels the printing midway (S15) and then proceeds to processing S16. On the other hand, if printing is complete in the determination in S13 (S13:YES), the controller 11 proceeds to processing S16.

[0094] The cancellation key notification received in S14 is controlled in the same way as the cancellation key notification received in S8. However, the difference is that the cancellation key notification received in S8 corresponds to cancellation while a print job is being received, while the cancellation key notification received in S14 corresponds to cancellation while a print job is being printed.

[0095] In the determination in S32 in Figure 6, if the detected user operation is a key operation on the key input unit 17b (S32: YES), the controller 11 checks the internal state stored in the internal state storage area (S33). Next, the controller 11 refers to the table data 25b (Figure 16(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 25b, if the current internal state is "printing", the pressability of both the back key 17b1 and the home key 17b2 on the key input unit 17b is "NG". However, the pressability of the cancel key 17b3 is determined according to the security setting.

[0096] If the username currently logged into MFP10, i.e., the selected LoginUsername, is "suzuki", then "△" is set as the cancellation option during printing. Here, "△" indicates that permission can be granted after a warning, as mentioned earlier. Therefore, the ability to press the cancel key 17b3 is "OK", and the decision in S34 is "YES". In the following S35, the controller 11 determines whether the key operation is a press of the cancel key 17b3 for the print job corresponding to the selected LoginUsername (S35). If the key operation is a press of the cancel key 17b3 for the print job corresponding to the selected LoginUsername "suzuki", then the controller 11 determines "YES" in S35. The controller 11 then proceeds from S35 to S36, notifies the display process of the cancel key (S36), and then returns the process to S31. In the display process where a cancel key is notified, controller 11 will notify the receive & print process of the cancel key (S62:YES, S63~S73:NO, S74:YES:S75). In the receive & print process, controller 11 receives the cancel key notification (S14:YES) and cancels the printing midway (S15).

[0097] On the other hand, in the judgment of S35, if the key operation is not a press of the cancel key 17b3 for the print job corresponding to the selected LoginUser name (S35:NO), the controller 11 proceeds to S37 from S35.

[0098] In S37, the controller 11 determines whether the press of the cancel key 17b3 is for a print job corresponding to a username different from the selected LoginUsername. If the cancel key 17b3 is pressed (S37:YES), the controller 11 executes the cancel key press process (S38). In Figure 7, if the detailed security setting for the print job is On (S51:NO), the controller 11 determines whether a warning is necessary for the target user (S53:YES) and whether cancellation is possible after the warning (S54). The selected LoginUsername "suzuki" has "△" set as the authority for canceling a print job while it is being received. Therefore, in the determination in S53, it is determined to be "YES", and in the determination in S54, it is determined that the target user, the selected LoginUsername "suzuki", can cancel (S54:NO). For this reason, the controller 11 notifies the display process of the warning key (S55).

[0099] In contrast, in the case of the selected LoginUsername "kato", the selected LoginUsername "kato" has "×" set as the permission for canceling during printing. Therefore, in the judgment of S53, it is determined to be "NO", and in the judgment of S57, it is determined that the target user, selected LoginUsername "kato", cannot cancel (S57: NO). For this reason, the controller 11 sounds a rejection tone (S59).

[0100] In S55, when the controller 11 notifies the display process of a warning key, the controller 11 detects the notification of the warning key (S72 in Figure 9: YES) and displays the warning screen 17aC on the touch panel 17a (S78). When the OK button 17aC1 on the warning screen 17aC is selected, the controller 11 determines "YES" in S83 and notifies the processing in progress corresponding to the screen before the warning, i.e., the receive & print process, to cancel (S84), and then displays the home screen on the touch panel 17a (S61 in Figure 8). In the receive & print process, the controller 11 receives the cancel key notification (S14: YES) and cancels printing midway through (S15). On the other hand, when the cancel button 17aC2 is selected, the controller 11 determines "NO" in S83 and redisplays the screen before the warning (S82), and then proceeds to S62 in Figure 8. In this case, during the receiving and printing process, controller 11 does not receive a cancel key notification, so S14:YES does not occur, and printing is completed (S13:YES).

[0101] On the other hand, in the judgment of S2 above, if the print job that has started to be received is not a print job corresponding to a registered main unit LoginUser name (S2:NO), the controller 11 cancels the reception without RIP processing the print job (S17) and then terminates the reception and printing process. Note that in S17, instead of canceling, the controller may perform printing based on that print job.

[0102] On the other hand, if the controller 11 does not start receiving a print job in the judgment of S1 above (S1:NO), the controller 11 determines whether or not it has received an external instruction to print a main report (S20 in Figure 5). This determination is also made by the controller 11 depending on whether or not an external instruction to print a main report is stored in the receive buffer, specifically whether or not it has received the notification in S205 (Figure 18) above. As mentioned above, although the descriptions distinguish between an instruction to print a main report and a print job, an instruction to print a main report is an example of a print job. Printing a main report based on an instruction to print a main report is an example of printing based on a print job.

[0103] In the judgment of S20 above, if an external instruction to print the main unit report is received (S20: YES), the controller 11 displays the printing screen on the touch panel 17a of the user IF 17 (S21). Specifically, the controller 11 writes the screen ID "104" to the screen ID storage area in memory 12. Before performing the process in S21, the controller 11 writes "Main unit report printing due to external instruction" to the internal state storage area. The timing of this writing is not limited to this, and may be before or after the controller 11 receives the instruction to print the main unit report sent by the PC 10 in S304 (Figure 18) and notifies the print process of the instruction (S205). As a result, in S21, the controller 11 refers to the table data 25b and writes the screen ID "104" when the internal state is "Main unit report printing due to external instruction" to the screen ID storage area, so the printing screen is displayed on the touch panel 17a by the display process in S66 above. Figure 15(a) shows an example of a printing screen (screen ID=104) 17aK displayed on the touch panel 17a. Similar to the printing screen 17aH (Figure 14(a)), the printing screen 17aK consists of a display area 17aK1 that displays the internal status of the MFP 10 and a display area 17aK2 that displays the operating status of the MFP 10. Next, the controller 11 generates the image data of the instructed main unit report and outputs it to the printer 13 to start printing (S22), and then proceeds to the above S13 (Figure 4).

[0104] When an external command is issued to print the main report, the process proceeds to S13 after printing begins. Therefore, printing the main report can be canceled during printing, just like printing a print job. Cancellation of printing the main report during printing is controlled in the same way as canceling a print job during printing. However, since the external command to print the main report is usually issued by an administrator, the entity that presses the cancel key 17b3 is not the administrator, but a regular user of the MFP10.

[0105] In the determination in S32 in Figure 6, if the detected user operation is a key operation on the key input unit 17b (S32: YES), the controller 11 checks the internal state stored in the internal state storage area (S33). Next, the controller 11 refers to the table data 25b (Figure 16(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 25b, if the current internal state is "Printing a main unit report by external instruction", then the pressability of both the back key 17b1 and the home key 17b2 on the key input unit 17b is "NG". However, the pressability of the cancel key 17b3 is set to follow the security settings, but the print job group setting field 341 does not have any permission set for canceling during printing in the "Printing a main unit report by external instruction" state. For example, if "△" is set for all owners, as explained above in the explanation of canceling during printing, pressing the cancel key 17b3 will display the warning screen 17aC on the touch panel 17a (S78). If the OK button 17aC1 on the warning screen 17aC is selected, the controller 11 determines "YES" in S83 and notifies the processing in progress corresponding to the screen before the warning, i.e., the receive & print process, of the cancellation (S84), and then displays the home screen on the touch panel 17a (S61 in Figure 8). In the receive & print process, the controller 11 receives the cancellation key notification (S14: YES) and cancels the printing in the middle of printing the main unit report (S15). On the other hand, if the cancel button 17aC2 is selected, the controller 11 determines "NO" in S83 and redisplays the screen before the warning (S82), and then proceeds to S62 in Figure 8. In this case, during the receiving and printing process, the controller 11 does not receive a cancel key notification, so S14:YES does not occur, and the printing of the main unit report is completed (S13:YES).

[0106] On the other hand, if, in the judgment of S20 above, no instruction to print the main unit report from an external source is received (S20: NO), it is determined whether or not an instruction to print the main unit report has been notified from the user IF17 (S23). The instruction to print the main unit report can be made not only from the external source mentioned above, but also from the touch panel 17a of the user IF17. Specifically, for example, when the home screen 17aA (Figure 12(a)) is displayed on the touch panel 17a, if an unillustrated menu button on the home screen 17aA is touched, the above menu screen will be displayed, and if the instruction to print the main unit report is touched on that menu screen, the controller 11 receives the instruction to print the main unit report via the panel instruction and notifies the printing process. Note that cancellation during printing based on an instruction to print the main unit report via the panel instruction is equivalent to cancellation by the operator operating the MFP10. Therefore, cancellation during printing of the main unit report via the panel instruction is permitted, regardless of the settings in the print job group setting field 341 and the user permission assignment setting field 342, even if the detailed security setting for the print job is On in setting value 25. Although the table data 25b above does not include an internal state indicating "printing a report via panel instruction," you can use the internal state "printing" where the pressability of the cancel key 17b3 is set to "OK."

[0107] In the judgment in S23 above, if a main report print command is notified from the user IF17 (S23: YES), the controller 11 displays the "Printing" screen on the touch panel 17a of the user IF17 (S24). Specifically, the controller 11 writes the screen ID "103" to the screen ID storage area in memory 12. Before performing the process in S24, the controller 11 writes "Printing" to the internal state storage area. This writing timing is not limited to this; it may also be at a timing before or after receiving the main report print command and notifying the print process after receiving the touch operation for the main report print command from the menu screen. As a result, in S24, the controller 11 refers to the table data 25b and writes the screen ID "103" when the internal state is "Printing" to the screen ID storage area, so the "Printing" screen is displayed on the touch panel 17a by the display process in S60 above. The printing screen 17aH in Figure 14(a) above serves as both the printing screen for screen ID "102" and the printing screen for screen ID "103". Next, the controller 11 proceeds to process S22 above.

[0108] In S22, as described above, the controller 11 generates the image data for the instructed main unit report and outputs it to the printer 13, thereby starting printing. After that, the controller 11 proceeds to process S13 (Figure 4). The controller 11 determines whether or not it has received a cancellation key notification until the printing of the main unit report is complete (S13: NO) (S14). If it receives a cancellation key notification before the printing of the main unit report is complete (S13: NO) (S14: YES), the controller 11 cancels the printing of the main unit report (S15). On the other hand, if the controller 11 completes the printing of the main unit report without receiving a cancellation key notification (S14: NO) (S13: YES), it proceeds to process S16.

[0109] As mentioned above, the cancellation key notification received in S14 is processed in S35 and below if the cancellation key 17b3 is pressable in the user IF operation process (Figure 6) (S34: YES). In S35, the controller 11 determines that the cancellation key 17b3 has been pressed for printing the main report corresponding to the selected LoginUser name (S35: YES), notifies the display process of the cancellation key (S36), and then returns the process to S31. In the display process that has received the cancellation key notification, the controller 11 will notify the receive & print process of the cancellation key (S62: YES, S63~S73: NO, S74: YES: S75). In the receive & print process, the controller 11 receives the cancellation key notification (S14: YES) and cancels the printing of the main report midway (S15).

[0110] On the other hand, if, in the judgment in S23 above, no instruction to print the main unit report is received from user IF17 (S23: NO), the controller 11 determines whether or not an instruction to print the stored image data has been received (S25). An instruction to print the stored image data is received in S103 of the login process above.

[0111] In the judgment of S25, if a print instruction for the stored image data is notified (S25: YES), the controller 11 reads the print instruction image data from memory 12 (S26) and displays the printing screen on the touch panel 17a of the user IF 17 (S27). Specifically, the controller 11 writes screen ID "102" to the screen ID storage area in memory 12. Before performing the process in S27, the controller 11 writes "Printing stored image data" to the internal state storage area. This writing timing is not limited to this, and may also occur before or after the controller 11 receives the print instruction and notifies the print process in S103 (Figure 11). As a result, in S27, the controller 11 refers to the table data 25b and writes screen ID "102" when the internal state is "Printing stored image data" to the screen ID storage area, so the printing screen with screen ID "102" is displayed on the touch panel 17a. Next, the controller 11 starts printing by outputting the image data read in S26 to the printer 13 (S28), and then proceeds to the process in S13 (Figure 4). Note that when the internal state is "Printing stored image data", the pressability of the cancel key 17b3 in the table data 25b is "OK". Therefore, when the cancel key 17b3 is pressed while the stored image data is being printed (S13:NO), the controller 11 notifies the receiving and printing process of the cancel key, just as when the internal state is "Receiving print job (Printer logged in)". As a result, the printing of the stored image data is canceled midway (S15).

[0112] On the other hand, if, in the judgment of S25 above, a print instruction for the stored image data is not received (S25: NO), the controller 11 returns the process to S1 (Figure 6).

[0113] In Figure 7, the "target user" in S53 and S57 of the cancel key press process is the user indicated by the selected LoginUser name. However, it is not limited to this; the "target user" may also be the user indicated by the username included in the print job that forms the basis of the image data. This allows the system to display either a warning screen 17aC or a warning-only screen 17aD depending on the user indicated by the username included in the print job, even if the user is not logged into the MFP10 and, for example, the cancel key 17b3 is pressed on a print job that is currently being received.

[0114] As described above, the MFP10 of this embodiment makes it possible to restrict others from canceling the reception, printing, or printing of a print job while a print job for storage is being received, printing a print job is being printed, or printing a main unit report via an external command. This makes it possible to suppress accidental cancellation operations by others. Furthermore, the degree of restriction can be specified for each user, which is useful.

[0115] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are possible without departing from the spirit of the invention.

[0116] (1) In the above embodiment, an MFP10 was used as an example of a printing device, but the printing device is not limited to an MFP10; a standalone printer may also be used.

[0117] (2) In this embodiment, the key input unit 17b is configured with three keys 17b1 to 17b3, and each key can be switched between an illuminated state and an unlit state. However, the embodiment is not limited to this, and buttons corresponding to the three keys 17b1 to 17b3 may be displayed on the touch panel 17a, and the display / hide control of the buttons may be performed instead of the illumination / unexcavation control in S45 above. [Explanation of Symbols]

[0118] 10…MFC, 11…Controller, 16…Communication Interface, 17…User Interface, 21…Web Server, 25…Settings, 30…PC, 33…Controller, 34…Display, 41…Browser, 100…Image Forming System.< / esc> < / esc> < / esc>

Claims

1. User interface and Controller and A printing apparatus equipped with, The aforementioned controller, When a user inputs a cancellation instruction for an associated print job via the user interface, if the cancellation instruction does not correspond to the user associated with the print job, a warning is displayed on the user interface. A printing apparatus characterized by the following features.

2. The aforementioned controller, If a user inputs a print cancellation command via the user interface while printing is being performed based on an associated print job, and that cancellation command does not correspond to the user associated with the print job, a warning will be displayed on the user interface. The printing apparatus according to feature 1.

3. The printing apparatus further, Communication interface, Equipped with, The aforementioned controller, If a user is receiving an associated print job via the communication interface, and a cancellation instruction for the reception is input via the user interface, and the cancellation instruction does not correspond to the user associated with the print job, a warning will be displayed on the user interface. The printing apparatus according to feature 1.

4. The printing apparatus further, Communication interface, Memory and Equipped with, The aforementioned controller, When a user receives an associated print job via the communication interface, the system stores the print job in memory without performing printing based on that print job, displays options corresponding to the stored print job on the user interface, and, upon receiving an operation to select an option via the user interface, performs printing based on the print job corresponding to the selected option. If, while the user interface is displaying options corresponding to the accumulated print jobs, a cancellation instruction for the print job is entered via the user interface, and the cancellation instruction does not correspond to the user associated with the print job, a warning will be displayed on the user interface. The printing apparatus according to feature 1.

5. The aforementioned controller, By accepting login operations via the aforementioned user interface, it is possible to enter a logged-in state. The case in which the cancellation instruction does not correspond to the user associated with the print job is when, via the user interface, the user is not logged in when a cancellation instruction for the associated print job is entered by the user, or when the user is logged in but the logged-in user does not correspond to the user associated with the print job. The aforementioned controller, In that case, a warning will be displayed on the user interface. The printing apparatus according to any one of claims 1 to 4.

6. The printing apparatus further, Communication interface, Memory and Equipped with, The aforementioned controller, When a user receives an associated print job via the communication interface, the system stores the print job in memory without performing printing based on that print job, displays options corresponding to the stored print job on the user interface, and, upon receiving an operation to select an option via the user interface, performs printing based on the print job corresponding to the selected option. Based on administrator operations, it is possible to register restriction information in the memory that indicates restrictions on cancellation of associated print jobs by the user. When a user inputs a cancellation instruction for an associated print job via the user interface, and the cancellation instruction does not correspond to the user associated with the print job, the cancellation is restricted according to the restriction information registered in the memory. The printing apparatus according to feature 1.

7. The aforementioned controller, By accepting login operations via the aforementioned user interface, it is possible to enter a logged-in state. Based on administrator operations, it is possible to register multiple user information entries in the memory, each representing a different user who can log in to the printing device. Based on administrator operations, it is possible to register multiple restriction pieces of information in the memory, each of which is associated with a user's information, indicating restrictions on canceling associated print jobs. The case in which the cancellation instruction does not correspond to the user associated with the print job is when, via the user interface, the user is not logged in when a cancellation instruction for the associated print job is entered by the user, or when the user is logged in but the logged-in user does not correspond to the user associated with the print job. The aforementioned controller, In that case, the cancellation is restricted according to the restriction information corresponding to the logged-in user registered in the memory. The printing apparatus according to feature 6.

8. The aforementioned controller, When a user inputs a print cancellation command via the user interface while printing is being performed based on an associated print job, if the user is not logged in, or if the logged-in user does not correspond to the user associated with the print job, When the restriction information corresponding to the logged-in user registered in the memory indicates a warning, the warning is displayed on the user interface. If the restriction information corresponding to the logged-in user, which is registered in the memory, indicates that cancellation is prohibited, the printing will continue without being canceled. The printing apparatus according to feature 7.

9. The aforementioned controller, Based on administrator operations, when registering the display of the warning as restriction information, it is possible to register in the memory, based on administrator operations, either that the print can be canceled via the display screen after the warning is displayed, or that the print cannot be canceled. The printing apparatus according to feature 8.

10. The aforementioned controller, When a user is receiving an associated print job via the communication interface, and a cancellation instruction for the reception is entered via the user interface, if the user is not logged in, or if the user is logged in but the logged-in user does not correspond to the user associated with the print job, When the restriction information corresponding to the logged-in user registered in the memory indicates a warning, the warning is displayed on the user interface. If the restriction information corresponding to the logged-in user, which is registered in the memory, indicates that cancellation is prohibited, the reception will continue without being canceled. The printing apparatus according to feature 7.

11. The aforementioned controller, When a user receives an associated print job via the communication interface, the system stores the print job in memory without performing printing based on that print job, displays options corresponding to the stored print job on the user interface, and, upon receiving an operation to select an option via the user interface, performs printing based on the print job corresponding to the selected option. When the user interface is displaying the options corresponding to the accumulated print jobs, and a cancellation instruction for the print job is entered via the user interface, if the user is not logged in, or if the logged-in user is not the user associated with the print job, When the restriction information corresponding to the logged-in user registered in the memory indicates a warning, the warning is displayed on the user interface. If the restriction information corresponding to the logged-in user, which is registered in the memory, indicates that cancellation is prohibited, the print job will not be canceled. The printing apparatus according to feature 7.

12. The aforementioned controller, When the restriction information corresponding to the logged-in user, which is registered in the memory, indicates that the display of options should be prohibited, when displaying the options corresponding to the stored print jobs on the user interface, for print jobs that do not correspond to the user associated with the print job and the logged-in user, the options will not be displayed on the user interface, thereby preventing the cancellation from being accepted. The printing apparatus according to feature 11.

13. The aforementioned controller, Based on administrator operations via the administrator screen, it is possible to enable or disable login operations. The administrator screen can accept administrator operations that specify the restrictions on canceling the aforementioned print job. The printing apparatus according to feature 6.

14. The aforementioned controller, Upon receiving an administrator operation via the administrator screen to enable login operations, the administrator screen displays an operation object related to the administrator operation that specifies the restrictions on canceling the print job. The printing apparatus according to feature 13.

15. In response to receiving an operation on the operation object displayed on the administrator screen, a restriction operation acceptance screen is displayed on the user interface to receive an administrator operation specifying the restrictions on canceling the print job, and the restriction information is stored in the memory based on the administrator operation received via the restriction operation acceptance screen. The printing apparatus according to feature 14.

16. User interface and Controller and A printing apparatus equipped with, The aforementioned controller, Regarding the printing instructions for the main report based on administrator operations, when a cancellation instruction is entered via the user interface, a warning is displayed on the user interface. A printing apparatus characterized by the following features.

Images