Printer and Non-transitory Computer-readable Recording Medium Storing Computer-read Able Instructions for Printer for Registering Print Setting Information Received from External Device

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to Japanese Patent Application No. 2020-018303, filed on Feb. 5, 2020, and Japanese Patent Application No. 2021-012465, filed on Jan. 28, 2021, the entire contents of which are hereby incorporated by reference into the present application.

TECHNICAL FIELD

The disclosure herein discloses a printer configured to register print setting information received from an external device.

BACKGROUND ART

An image forming system including a communication device and a multi-function peripheral (MFP) is known. A user who uses the communication device can register a print preset in the MFP according to Internet Printing Protocol (IPP).

SUMMARY

The above technique does not give any consideration to restricting registration of the print preset in the MFP. The disclosure herein provides art for restricting registration of print setting information.

A printer disclosed herein may comprise: a memory configured to store, for each of one or more user identification information, the user identification information and registration related information which is related to registration of print setting information in association with each other, the registration related information being either of permission information indicating that registration of the print setting information is permitted or restriction information indicating that registration of the print setting information is restricted; a communication interface; and a controller configured to: receive first user identification information from an external device via the communication interface; receive a registration request including first print setting information from the external device via the communication interface, the registration request being for requesting registration of print setting information to the memory; in a first case where the first user identification information and the registration request are received from the external device and the registration related information associated with the first user identification information among the one or more user identification information in the memory is the permission information, register the first print setting information included in the registration request in the memory in association with the first user identification information, wherein in a second case where the first user identification information and the registration request are received from the external device and the registration related information associated with the first user identification information in the memory is the restriction information, the first print setting information is not registered in the memory.

Another printer disclosed herein may comprise: a memory configured to store, for each of one or more user identification information, the user identification information and registration related information which is related to registration of print setting information in association with each other, the registration related information being either of permission information indicating that registration of the print setting information is permitted or restriction information indicating that registration of the print setting information is restricted; a communication interface; and a controller configured to: receive first user identification information from an external device via the communication interface; in a case where the first user identification information is received from the external device in a state where registration related information associated with the first user identification information is the restriction information, send a restriction request to the external device via the communication interface, the first user identification information being included in the one or more user identification information in the memory, and the restriction request being for requesting restriction on sending of a registration request for requesting registration of the print setting information to the memory, wherein in a case where the first user identification information is received from the external device in a state where the registration related information associated with the first user identification information in the memory is the permission information, the restriction request is not sent; receive the registration request including first print setting information from the external device via the communication interface in the state where the registration related information associated with the first user identification information in the memory is the permission information; and in a first case where the first user identification information and the registration request are received from the external device and the registration related information associated with the first user identification information in the memory is the permission information, register the first print setting information included in the registration request to the memory in association with the first user identification information, wherein in a second case where the first user identification information is received from the external device and the registration related information associated with the first user identification information in the memory is the restriction information, the first print setting information is not registered to the memory.

Control methods, computer programs, and computer-readable recording media storing the computer programs for realizing the above printers are also novel and useful. Further, communication systems comprising the above printers and external device are also novel and useful.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a configuration of a communication system.

FIG. 2 show respective tables.

FIG. 3 shows a flowchart of a printer process according to first to third embodiments.

FIG. 4 shows a flowchart of a web server process according to the first and second embodiments.

FIG. 5 shows a flowchart of a first registration process according to the first and second embodiments.

FIG. 6 shows a flowchart of an IPP process according to the first and second embodiments.

FIG. 7 shows a flowchart of a second registration process according to the first and second embodiments.

FIG. 8 shows a sequence diagram of Case A in which preset information is registered in the first embodiment.

FIG. 9 shows a sequence diagram of Cases B and C in which registration of preset information is restricted in the first embodiment.

FIG. 10 shows a sequence diagram of Case D in which preset information is registered in the first embodiment.

FIG. 11 shows a sequence diagram of Case E in which printing is executed in the first embodiment.

FIG. 12 shows examples of a screen displayed on a PC in the first and second embodiments.

FIG. 13 shows examples of screens displayed on a PC in the first and second embodiments.

FIG. 14 shows a sequence diagram of Case F in which preset information is registered in the second embodiment.

FIG. 15 shows a sequence diagram of Case G in which printing is executed in the second embodiment.

FIG. 16 shows a flowchart of a web server process according to the third embodiment.

FIG. 17 shows a flowchart of a first registration process according to the third embodiment.

FIG. 18 shows a flowchart of an IPP process according to the third embodiment.

FIG. 19 shows a flowchart of a second registration process according to the third embodiment.

FIG. 20 shows a sequence diagram of Cases H and I in which registration of preset information is restricted in the third embodiment.

FIG. 21 shows an example of screen displayed on a PC in the third embodiment.

FIG. 22 shows an example of screen displayed on a PC in the third embodiment.

EMBODIMENTS

First Embodiment

(Configuration of Communication System 2 ; FIG. 1 )

As shown in FIG. 1 , a communication system 2 is provided with a printer 10 and a plurality of PCs 100 A to 100 D. The printer 10 and the PCs 100 A to 100 D belong to the same Local Area Network (LAN) 4 and are configured to communicate with each other via the LAN 4 .

(Configuration of Printer 10 )

The printer 10 is a peripheral device (i.e., a peripheral device of the PCs 100 A to 100 D) configured to execute a print function. The printer 10 is further configured to execute a web server function. The web server function is a function of sending webpage data representing a webpage to an external device in response to the external device accessing a web server in the printer 10 . The printer 10 may be a multi-function peripheral configured to execute, in addition to the above functions, a scan function, a FAX function, and/or the like. The printer 10 is provided with an operation unit 12 , a display unit 14 , a print executing unit 16 , a communication interface (hereinbelow, an interface will be denoted “I/F”) 20 , and a controller 30 .

The operation unit 12 is provided with a plurality of keys. A user can input various instructions to the printer 10 by operating the operation unit 12 . The display unit 14 is a display for displaying various types of information. The display unit 14 also functions as a so-called touch screen (i.e., an operation unit). The print executing unit 16 is a print mechanism of an inkjet scheme, a laser scheme, or the like. The communication I/F 20 is connected to the LAN 4 . The communication I/F 20 may be a wireless I/F or a wired I/F.

The controller 30 is provided with a CPU 32 and a memory 34 . The CPU 32 is configured to execute various processes according to a program 36 stored in the memory 34 . The memory 34 is configured of a volatile memory, a nonvolatile memory, and the like. The memory 34 stores a user table 38 and a preset table 40 .

(Configurations of PCs 100 A to 100 D)

The PC 100 A is used by an administrator of the printer 10 . The PCs 100 B to 100 D are used by users different from the administrator of the printer 10 . The PCs 100 A, 100 B, 100 C, and 100 D respectively store user names “U 1 ”, “U 2 ”, “U 3 ”, and “U 4 ” for identifying the users using the respective PCs.

Each of the PCs 100 A to 100 D is provided with an Internet Printing Protocol (IPP) program (not shown) installed from a server on the Internet. Each IPP program is a program for creating an IPP command according to Hyper Text Transfer Protocol (HTTP) and sending the command to the printer 10 . In the present embodiment, the aforementioned server is provided by a business entity different from a vendor of the printer 10 . However, in a variant, the aforementioned server may be provided by the vendor of the printer 10 . Each of the PCs 100 A to 100 D may originally support IPP without installing the IPP program from the server.

(Contents of Tables 38 , 40 ; FIG. 2 )

Next, contents of the user table 38 and the preset table 40 in the printer 10 will be described with reference to FIG. 2 .

The user table 38 stores, for each of one or more users who use the printer 10 , a user name, a password, print condition information, a registration permission flag, authority information, and a registered preset name in association with each other. All the information other than the registered preset name is registered by the administrator of the printer 10 . The user name and the password are information used for authentication of each user. The print condition information is information indicating whether the user is permitted to use print conditions which the printer 10 can execute, namely “one-sided”, “two-sided”, “monochrome”, and “color”. “One-sided” and “two-sided” respectively mean one-sided printing and two-sided printing. “Monochrome” and “color” respectively mean monochrome printing and color printing. “ON” or “OFF” is assigned to each print condition. “ON” indicates that the user is permitted to use the print condition, while “OFF” indicates that the user is not permitted to use the print condition. Hereinbelow, a print condition assigned with “ON” may be termed “permitted print condition”, and a print condition assigned with “OFF” may be termed “restricted print condition”.

The registration permission flag indicates a value which is one of “ON” indicating that registration of preset information (to be described later) is permitted and “OFF” indicating that registration of preset information is restricted. The authority information indicates one of “Owner” and “Guest”. “Owner” is information indicating the administrator of the printer 10 , and “Guest” is information indicating a user different from the administrator of the printer 10 , that is, a general user (in other words, individual user). The registered preset name is information for identifying preset information to be described later.

The preset table 40 stores one or more preset information. Each preset information includes a preset name and print setting information. The print setting information includes a print condition (i.e., “one-sided” or “two-sided”) corresponding to a print setting item “print type” and a print condition (i.e., “monochrome” or “color”) corresponding to a print setting item “number of colors”. In a variant, the print setting information may include other print setting item(s) (e.g., image quality, paper size, paper type, number of printed sheets, postprocess, etc.). Further, the print setting information may not include one of the print setting item “print type” and the print setting item “number of colors”. Preset information PI 1 including a preset name “DPR” is default preset information registered in the preset table 40 in advance.

(Printer Process; FIG. 3 )

Next, a printer process executed by the CPU 32 of the printer 10 will be described with reference to FIG. 3 . The process of FIG. 3 is started when power of the printer 10 is turned on. All of below-described communication executed by the printer 10 are executed via the communication I/F 20 . As such, the phrase “via the communication I/F 20 ” will be omitted hereinbelow.

In S 10 , the CPU 32 monitors receipt of a top screen request from a PC. The top screen request is a command for requesting sending of top screen data for displaying a top screen, and is a GET command according to HTTP. The CPU 32 proceeds to S 12 in a case of receiving the top screen request from a PC (YES in S 10 ).

In S 12 , the CPU 32 executes a web server process ( FIG. 4 ). The web server process is a process for the printer 10 to function as a web server. When S 12 is completed, the CPU 32 returns to S 10 .

At the same time as the monitoring of S 10 , the CPU 32 monitors receipt of an IPP command from a PC in S 20 . The CPU 32 proceeds to S 22 in a case of receiving an IPP command from a PC (YES in S 20 ).

In S 22 , the CPU 32 executes an IPP process ( FIG. 6 ). The IPP process is a process for executing communication according to IPP to register or delete preset information into/from the preset table 40 . When S 22 is completed, the CPU 32 returns to S 10 .

(Web Server Process; FIG. 4 )

Next, the web server process executed in S 12 of FIG. 3 will be described with reference to FIG. 4 . In S 40 , the CPU 32 sends the top screen data for displaying the top screen to the PC. The top screen is a screen for allowing a user to input a user name and a password.

In S 42 , the CPU 32 receives a management screen request including a user name and a password from the PC. The management screen request is a GET command according to HTTP and is sent from the PC in response to a user name and a password being inputted to the top screen displayed on the PC.

In S 44 , the CPU 32 executes user authentication using the user name and the password in the management screen request. The CPU 32 determines YES in S 44 and proceeds to S 46 in a case where the combination of the user name and the password in the management screen request is registered in the user table 38 , that is, in a case where the user authentication succeeds. Hereinbelow, the user name for which the user authentication succeeded will be termed “authenticated user name” On the other hand, the CPU 32 determines NO in S 44 and terminates the process of FIG. 4 in a case where the combination of the user name and the password in the management screen request is not registered in the user table 38 , that is, in a case where the user authentication fails.

In S 46 , the CPU 32 sends management screen data for displaying a management screen D 11 to the PC. As shown in FIG. 13 , the screen D 11 includes a preset setting button and a cancel button.

In S 50 , the CPU 32 monitors receipt of a preset setting screen request from the PC. The preset setting screen request is a GET command according to HTTP and is sent from the PC in response to the preset setting button in the management screen D 11 being selected. The CPU 32 proceeds to S 52 in a case where the preset setting screen request is received from the PC (YES in S 50 ). On the other hand, the CPU 32 terminates the process of FIG. 4 in a case where a cancel request is received from the PC (NO in S 50 ). The cancel request is sent from the PC in response to the cancel button in the management screen D 11 being selected.

In S 52 , the CPU 32 sends preset setting screen data for displaying a preset setting screen D 12 to the PC. As shown in FIG. 13 , the screen D 12 is a screen in which for each of the one or more preset names associated with the authenticated user name in the user table 38 , the preset name and a deletion button corresponding to the preset name are associated to each other. The screen D 12 further includes a new registration button and a cancel button. In a variant, the screen D 12 may be a screen in which for each of the one or more preset names registered in the preset table 40 , the preset name and a deletion button corresponding to the preset name are associated to each other.

In S 60 , the CPU 32 monitors receipt of an input screen request from the PC. The input screen request is a GET command according to HTTP and is sent from the PC in response to the new registration button in the preset setting screen D 12 displayed on the PC being selected. The CPU 32 proceeds to S 62 in a case of receiving the input screen request from the PC (YES in S 60 ). On the other hand, the CPU 32 proceeds to S 70 in a case of not receiving the input screen request from the PC (NO in S 60 ).

In S 62 , the CPU 32 sends input screen data for displaying an input screen D 13 to the PC. As shown in FIG. 13 , the screen D 13 includes a preset name input box for input of a preset name, a registration user name input box for input of a registration-target user name to be registered, four checkboxes corresponding to the four print conditions (i.e., “one-sided”, “two-sided”, “monochrome”, and “color”), an OK button, and a cancel button. The registration-target user name may be the same as the authenticated user name or may be different therefrom.

In S 64 , the CPU 32 determines whether or not a registration instruction including preset information and a registration-target user name has been received from the PC. Here, this preset information includes the preset name inputted to the preset name input box in the input screen D 13 displayed on the PC and the print conditions checked in the input screen D 13 . Further, the registration-target user name is the user name inputted to the registration user name input box in the input screen D 13 . The registration instruction is a POST command according to HTTP and is sent from the PC in response to the OK button in the input screen D 13 being selected. The CPU 32 proceeds to S 66 in a case of receiving the registration instruction from the PC (YES in S 64 ). On the other hand, the CPU 32 terminates the process of FIG. 4 in a case of receiving a cancel request from the PC (NO in S 64 ). This cancel request is sent from the PC in response to the cancel button in the input screen D 13 being selected. Hereinbelow, the preset information and the registration-target user name included in the registration instruction will respectively be termed “target preset information” and “target registration user name”.

In S 66 , the CPU 32 executes a first registration process ( FIG. 5 ). The first registration process is a process for registering the target preset information included in the registration instruction to the preset table 40 . When S 66 is completed, the CPU 32 terminates the process of FIG. 4 .

In S 70 , the CPU 32 determines whether or not a deletion instruction including a preset name has been received from the PC. The deletion instruction is sent in response to the deletion button in the preset setting screen D 12 displayed on the PC being selected. The CPU 32 proceeds to S 72 in a case of receiving the deletion instruction from the PC (YES in S 70 ). On the other hand, the CPU 32 terminates the process of FIG. 4 in a case of receiving a cancel request from the PC (NO in S 70 ). This cancel request is sent from the PC in response to the cancel button in the preset setting screen D 12 being selected.

In S 72 , the CPU 32 deletes from the preset table 40 the preset information including the preset name included in the deletion instruction received in S 70 . When S 72 is completed, the CPU 32 terminates the process of FIG. 4 .

(First Registration Process; FIG. 5 )

Next, the first registration process executed in S 66 of FIG. 4 will be described with reference to FIG. 5 . In S 90 , the CPU 32 determines whether or not the registration permission flag associated with the authenticated user name is “ON” in the user table 38 . The CPU 32 proceeds to S 92 in a case where the registration permission flag is “ON” (YES in S 90 ). On the other hand, the CPU 32 proceeds to S 110 in a case where the registration permission flag is “OFF” (NO in S 90 ).

In S 92 , the CPU 32 determines whether or not a restricted print condition is included in the print setting information in the target preset information included in the registration instruction received in S 64 of FIG. 4 . Specifically, the CPU 32 firstly identifies in the user table 38 a restricted print condition (i.e., a print condition indicating “OFF”) associated with the target registration user name in the registration instruction. Then, the CPU 32 determines whether or not the identified restricted print condition is included in the print setting information in the target preset information. The CPU 32 proceeds to S 94 in a case where the identified restricted print condition is not included in the print setting information in the target preset information (NO in S 92 ). On the other hand, the CPU 32 proceeds to S 100 in a case where the identified restricted print condition is included in the print setting information in the target preset information (YES in S 92 ).

In S 94 , the CPU 32 registers the target preset information (i.e., the preset name and the print setting information) in the preset table 40 .

In S 96 , the CPU 32 registers the preset name in the target preset information as a registered preset name associated with the target registration user name in the user table 38 .

In S 98 , the CPU 32 sends to the PC completion notification screen data for displaying a completion notification screen including a message that the registration of the preset information has been completed. When S 98 is completed, the CPU 32 terminates the process of FIG. 5 .

In S 100 , the CPU 32 sends selection screen data for displaying a selection screen D 14 to the PC. As shown in FIG. 13 , the screen D 14 includes a message that the restricted print condition is included in the target preset information, a message that asks whether or not preset information in which the restricted print condition is replaced is to be registered, an OK button, and a cancel button.

In S 102 , the CPU 32 determines whether or not a change instruction has been received from the PC. The change instruction is a POST command according to HTTP and is sent from the PC in response to the OK button in the selection screen D 14 displayed on the PC being selected. The CPU 32 proceeds to S 104 in a case of receiving the change instruction from the PC (YES in S 102 ). On the other hand, the CPU 32 proceeds to S 110 in a case of receiving a cancel request from the PC (NO in S 102 ). This cancel request is sent from the PC in response to the cancel button in the selection screen D 14 being selected.

In S 104 , the CPU 32 deletes the restricted print condition included in the print setting information in the target preset information to create new preset information. Specifically, the CPU 32 firstly identifies in the user table 38 a permitted print condition (i.e., a print condition indicating “ON”) associated with the target registration user name. For example, in a case where the print setting item of the restricted print condition included in the print setting information in the target preset information is “print type”, the CPU 32 creates new preset information by replacing the restricted print condition (e.g., “two-sided”) with the identified permitted print condition (e.g., “one-sided”) corresponding to “print type”. Further, for example, in a case where the print setting item of the restricted print condition included in the print setting information in the target preset information is “number of colors”, the CPU 32 creates new preset information by replacing the restricted print condition (e.g., “color”) with the identified permitted print condition (e.g., “monochrome”) corresponding to “number of colors”.

In S 106 , the CPU 32 registers the preset information created in S 104 to the preset table 40 . S 108 is the same as S 96 .

In S 110 , the CPU 32 sends to the PC error notification screen data for displaying an error notification screen including a message that the registration of the preset information failed. When S 110 is completed, the CPU 32 terminates the process of FIG. 5 .

(IPP Process; FIG. 6 )

Next, the IPP process executed in S 22 of FIG. 3 will be described with reference to FIG. 6 . In S 120 , the CPU 32 determines whether or not the IPP command received in S 20 of FIG. 3 is a Get-Printer-Attributes command (hereinbelow termed “GPA”). The GPA is a command that requests the printer 10 to send capability information. The CPU 32 proceeds to S 122 in a case where the IPP command is a GPA (YES in S 120 ). On the other hand, the CPU 32 proceeds to S 150 in a case where the IPP command is not a GPA (NO in S 120 ).

In S 122 , the CPU 32 determines whether or not a user name and a password are included in the GPA. The CPU 32 proceeds to S 124 in a case where a user name and a password are included in the GPA (YES in S 122 ). On the other hand, the CPU 32 proceeds to S 130 in a case where a user name and a password are not included in the GPA (NO in S 122 ). In S 130 , the CPU 32 sends to the PC an authentication information request for displaying an authentication screen on the PC. The authentication screen is a screen for allowing the user to input a user name and a password. When S 130 is completed, the CPU 32 terminates the process of FIG. 6 .

S 124 is the same as S 44 of FIG. 4 except that the user name and the password in the GPA are used.

In S 126 , the CPU 32 sends capability information to the PC. Specifically, the CPU 32 firstly identifies in the user table 38 a preset name associated with the same user name as the user name in the GPA. Then, the CPU 32 identifies in the preset table 40 preset information including the identified preset name. Next, the CPU 32 sends to the PC capability information including all the print conditions which the printer 10 can execute (i.e., “one-sided”, “two-sided”, “monochrome”, and “color”) and the identified preset information. In a variant, the printer 10 may send to the PC capability information including all the print conditions which the printer 10 can execute and may send to the PC the identified preset information separately from the capability information.

In S 140 , the CPU 32 sends to the PC authentication error information for displaying an error notification screen including a message that the user authentication failed on the PC. When S 140 is completed, the CPU 32 terminates the process of FIG. 6 .

In S 150 , the CPU 32 determines whether or not the IPP command received in S 20 of FIG. 3 is a Set-Printer-Attributes command (hereinbelow termed “SPA”). The SPA is a command that requests the printer 10 to register or delete preset information. The SPA is sent from the PC after the capability information has been sent to the PC (S 126 ) as a result of the user authentication having succeeded (YES in S 124 ). The SPA includes the user name for which the authentication succeeded. The CPU 32 proceeds to S 152 in a case where the IPP command is an SPA (YES in S 150 ). On the other hand, the CPU 32 proceeds to S 160 in a case where the IPP command is not an SPA (NO in S 150 ). In the case where it is determined NO in S 150 , the IPP command is a Validate-Job command (hereinbelow termed “VJ”) or the like.

In S 152 , the CPU 32 determines whether or not registration-target preset information is included in the SPA. The CPU 32 identifies one or more preset information associated with the user name included in the SPA from the user table 38 . Then, in a case where there is preset information that is included in the SPA but not included in the identified one or more preset information, the CPU 32 identifies this preset information as registration-target preset information, determines YES in S 152 , and proceeds to S 154 . On the other hand, in a case where there is preset information that is included in the identified one or more preset information but not included in the SPA, the CPU 32 identifies this preset information as deletion-target preset information, determines NO in S 152 , and proceeds to S 156 .

In S 154 , the CPU 32 executes a second registration process ( FIG. 7 ). The second registration process is a process for registering the preset information identified in S 152 as a registration target to the preset table 40 . When S 154 is completed, the CPU 32 terminates the process of FIG. 6 .

In S 156 , the CPU 32 deletes the preset information identified in S 152 as a deletion target from the preset table 40 .

In S 158 , the CPU 32 deletes from the user table 38 the preset name corresponding to the preset information deleted in S 156 . When S 158 is completed, the CPU 32 terminates the process of FIG. 6 .

In S 160 , the CPU 32 executes various processes according to IPP. When S 160 is completed, the CPU 32 terminates the process of FIG. 6 .

(Second Registration Process; FIG. 7 )

Next, the second registration process executed in S 154 of FIG. 6 will be described with reference to FIG. 7 . S 180 and S 182 are the same as S 90 and S 92 of FIG. 5 except that the user name in the SPA is used. The CPU 32 proceeds to S 182 in a case of determining YES in S 180 , while it proceeds to S 190 in a case of determining NO in S 180 . Further, the CPU 32 proceeds to S 184 in a case of determining NO in S 182 , while it proceeds to S 190 in a case of determining YES in S 182 . S 184 and S 186 are the same as S 94 and S 96 except that the preset information in the SPA of FIG. 6 is used. In S 188 , the CPU 32 sends to the PC registration completion information for displaying a completion notification screen including a message that the registration of the preset information has been completed on the PC. In S 190 , the CPU 32 sends to the PC registration error information for displaying an error notification screen including a message that the registration of the preset information failed on the PC. When S 188 or S 190 is completed, the CPU 32 terminates the process of FIG. 7 .

(Specific Cases A to E; FIGS. 8 to 11 )

Specific Cases A to E realized by the processes of FIGS. 3 to 7 will be described with reference to FIGS. 8 to 11 .

(Case A; FIG. 8 )

Case A will be described with reference to FIG. 8 . In Case A, preset information is registered to the preset table 40 using communication according to IPP. In an initial state of Case A, the preset information PI 1 (see FIG. 2 ) is stored in the preset table 40 . Further, for each of the user names “U 1 ”, “U 2 ”, “U 3 ”, and “U 4 ”, the corresponding information (i.e., the user name, password, print condition information, registration permission flag, authority information, and registered preset name) are stored in the user table 38 (see FIG. 2 ). Further, the preset name “DPR” is associated with each user name as a registered preset name.

When accepting an operation for displaying the print setting screen in T 10 , the PC 100 B sends a GPA to the printer 10 in T 12 .

When receiving the GPA from the PC 100 B in T 12 (NO in S 10 , YES in S 20 of FIG. 3 , YES in S 120 of FIG. 6 ), the printer 10 determines that a user name and a password are not included in the GPA (NO in S 122 ), and sends an authentication information request to the PC 100 B in T 14 (S 130 ).

When receiving the authentication information request from the printer 10 in T 14 , the PC 100 B displays the authentication screen in T 16 . Then, when accepting an input of the user name U 2 and a password P 2 in T 18 , the PC 100 B sends a GPA including the user name U 2 and the password P 2 to the printer 10 in T 20 .

When receiving the GPA from the PC 100 B in T 20 (NO in S 10 , YES in S 20 of FIG. 3 , YES in S 120 of FIG. 6 ), the printer 10 determines that a user name and a password are included in the GPA (YES in S 122 ), and then determines that the user authentication succeeded in T 22 (YES in S 124 ) because the combination of the user name U 2 and the password P 2 included in the GPA is registered in the user table 38 . Then, the printer 10 identifies the preset name DPR associated with the user name U 2 in the GPA from the user table 38 and identifies the preset information PI 1 including the identified preset name DPR from the preset table 40 . Then, in T 24 , the printer 10 sends to the PC 100 B capability information including all the print conditions which the printer 10 can execute (i.e., “one-sided”, “two-sided”, “monochrome”, and “color”) and the identified preset information PI 1 .

When receiving the capability information from the printer 10 in T 24 , the PC 100 B displays a print setting screen D 1 in T 30 . As shown in FIG. 12 , the print setting screen D 1 includes a preset name selection box for selection of a preset name, four checkboxes corresponding to “one-sided”, “two-sided”, “monochrome”, and “color”, an OK button, a cancel button, and a preset deletion button. In initial print setting screen D 1 , the preset name “DPR” is displayed in the preset name selection box, and the checkboxes corresponding to “one-sided” and “monochrome” are checked. When accepting an operation of checking the checkbox corresponding to “color” in T 32 and accepting a selection of the pull-down of the preset name selection box in T 34 , the PC 100 B displays a preset name selection image N 1 over the print setting screen D 1 in T 36 . As shown in FIG. 12 , the image N 1 includes a list image of selectable preset names and a new registration image for registration of new preset information. When accepting a selection of the new registration image in T 38 , the PC 100 B displays an input image N 2 over the print setting screen D 1 in T 40 . As shown in FIG. 12 , the image N 2 includes an input box for input of a preset name, an OK button, and a cancel button. When accepting an input of a preset name “IPR 1 ” and a selection of the OK button in T 42 , the PC 100 B sends a GPA including the user name U 2 and the password P 2 to the printer 10 in T 50 . T 52 is the same as T 24 . In a variant, print setting information may be set after a registration-target preset name has been inputted. In this variant, the PC 100 B accepts the selection of the pull-down of the preset name selection box without accepting the operation of checking the checkbox corresponding to “color” after having displayed the print setting screen D 1 . After this, processes same as T 36 to T 42 are executed. Then, when accepting the input of the preset name “IPR 1 ” and the selection of the OK button in T 42 , the PC 100 B displays the print setting screen in which the preset name “IPR 1 ” is displayed in the preset name selection box. Then, when accepting the operation of checking the checkbox corresponding to “color” and the selection of the OK button, the PC 100 B sends a GPA including the user name U 2 and the password P 2 to the printer 10 .

When receiving the capability information from the printer 10 in T 52 , the PC 100 B extracts the preset information PI 1 in the capability information. Then, the PC 100 B creates preset information PI 2 in which the preset name IPR 1 inputted in T 42 is associated with the print setting information “one-sided” and “color” set in T 32 , and sends an SPA including the user name U 2 , the password P 2 , and the preset information PI 1 , PI 2 to the printer 10 in T 54 .

When receiving the SPA from the PC 100 B (NO in S 10 , YES in S 20 of FIG. 3 , NO in S 120 , YES in S 150 of FIG. 6 ), the printer 10 determines that the registration-target preset information PI 2 is included in the SPA (YES in S 152 ). Then, the printer 10 determines that the registration permission flag associated with the user name U 2 included in the SPA is “ON” in the user table 38 (YES in S 180 ), determines that the print setting information in the preset information PI 2 includes no restricted print condition associated with the user name U 2 in the user table 38 (NO in S 182 ), and registers the preset information PI 2 to the preset table 40 in T 56 (S 184 ). Next, in T 58 , the printer 10 registers the preset name “IPR 1 ” to the user table 38 as a registered preset name associated with the user name U 2 (S 186 ). Then, in T 60 , the printer 10 sends the registration completion information to the PC 100 B (S 188 ).

(Case B; FIG. 9 )

Case B will be described with reference to FIG. 9 . In Case B, the registration of preset information using communication according to IPP fails due to the print setting information in registration-target preset information includes a restricted print condition. An initial state of Case B is a state after Case A, that is, the preset information PI 1 and PI 2 are stored in the preset table 40 .

Firstly, processes same as T 10 to T 30 of FIG. 8 are executed between the PC 100 C and the printer 10 . In the present case, the PC 100 C accepts an input of the user name U 3 and a password P 3 in T 18 , and sends a GPA including the user name U 3 and the password P 3 to the printer 10 in T 20 .

In T 132 , the PC 100 C accepts an operation of checking the checkboxes corresponding to “two-sided” and “color”. T 134 to T 140 are the same as T 34 to T 40 of FIG. 8 . When accepting an input of a preset name “IPR 2 ” and a selection of the OK button in T 142 , the PC 100 C sends a GPA including the user name U 3 and the password P 3 to the printer 10 in T 150 . T 152 is the same as T 52 of FIG. 8 . When receiving the capability information from the printer 10 in T 152 , the PC 100 C extracts the preset information PI 1 in the capability information. Then, the PC 100 C creates preset information PI 3 in which the preset name IPR 2 inputted in T 142 is associated with the print setting information “two-sided” and “color” set in T 132 , and sends an SPA including the user name U 3 , the password P 3 , and the preset information PI 1 , PI 3 to the printer 10 in T 154 .

When receiving the SPA from the PC 100 C in T 154 (NO in S 10 , YES in S 20 of FIG. 3 , NO in S 120 , YES in S 150 of FIG. 6 ), the printer 10 determines that the registration-target preset information PI 3 is included in the SPA (YES in S 152 ). Then, the printer 10 determines that the registration permission flag associated with the user name U 3 included in the SPA is “ON” in the user table 38 (YES in S 180 ), and determines that the print setting information in the preset information PI 3 includes a restricted print condition (i.e., “two-sided”) associated with the user name U 3 in the user table 38 (YES in S 182 ). In this case, the printer 10 does not register the preset information PI 3 to the preset table 40 . Then, in T 158 , the printer 10 sends the registration error information to the PC 100 C (S 190 ). As a result, the user who uses the PC 100 C can acknowledge that the registration of the preset information PI 3 failed.

(Effects of Cases A and B)

As shown in Case A of FIG. 8 , the printer 10 registers the preset information PI 2 to the preset table 40 (T 56 ) in the case of determining that the print setting information in the preset information PI 2 includes no restricted print condition associated with the user name U 2 in the user table 38 . On the other hand, as shown in Case B of FIG. 9 , the printer 10 does not register the preset information PI 3 in the case of determining that the print setting information in the preset information PI 3 includes a restricted print condition associated with the user name U 3 in the user table 38 . As such, it can be prevented that printing fails in response to preset information including a restricted print condition being used after the preset information including the restricted print condition has been registered to the preset table 40 .

(Case C; FIG. 9 )

Case C will be described with reference to FIG. 9 . In Case C, the registration of preset information using communication according to IPP fails due to the registration permission flag in the user table 38 being “OFF”. An initial state of Case C is the same as the initial state of Case B.

Firstly, processes same as T 10 to T 40 of FIG. 8 are executed between the PC 100 D and the printer 10 . In the present case, the PC 100 D accepts an input of the user name U 4 and a password P 4 in T 18 , and sends a GPA including the user name U 4 and the password P 4 to the printer 10 in T 20 . When accepting an input of a preset name “IPR 3 ” and a selection of the OK button in T 242 , the PC 100 D sends a GPA including the user name U 4 and the password P 4 to the printer 10 in T 250 . T 252 is the same as T 52 of FIG. 8 . When receiving the capability information from the printer 10 in T 252 , the PC 100 D extracts the preset information PI 1 in the capability information. Then, the PC 100 D creates preset information PI 4 in which the preset name IPR 3 inputted in T 242 is associated with the print setting information “one-sided” and “color” set in T 32 of FIG. 8 , and sends an SPA including the user name U 4 , the password P 4 , and the preset information PI 1 , PI 4 to the printer 10 in T 254 .

When receiving the SPA from the PC 100 D (NO in S 10 , YES in S 20 of FIG. 3 , NO in S 120 , YES in S 150 of FIG. 6 ), the printer 10 determines that the registration-target preset information PI 4 is included in the SPA (YES in S 152 ). Then, the printer 10 determines that the registration permission flag associated with the user name U 4 included in the SPA is “OFF” in the user table 38 (NO in S 180 ). In this case, the printer 10 does not register the preset information PI 4 to the preset table 40 . Then, in T 258 , the printer 10 sends the registration error information to the PC 100 D (S 190 ). As a result, the user who uses the PC 100 D can acknowledge that the registration of the preset information PI 4 failed.

(Case D; FIG. 10 )

Case D will be described with reference to FIG. 10 . In Case D, preset information is registered to the preset table 40 using the web server function of the printer 10 . An initial state of Case D is the same as the initial state of Case B.

When accepting an input of an IP address assigned to the printer 10 in T 310 , the PC 100 C sends a top screen request to the printer 10 in T 312 .

When receiving the top screen request from the PC 100 C in T 312 (YES in S 10 of FIG. 3 ), the printer 10 sends the top screen data to the PC 100 C in T 314 (S 40 of FIG. 4 ).

When receiving the top screen data from the printer 10 in T 314 , the PC 100 C displays the top screen in T 316 . Then, when accepting an input of the user name U 3 and the password P 3 in T 318 , the PC 100 C sends a management screen request including the user name U 3 and the password P 3 to the printer 10 in T 320 .

When receiving the management screen request from the PC 100 C in T 320 (S 42 ), the printer 10 determines in T 322 that the user authentication succeeded (YES in S 44 ) because the combination of the user name U 3 and the password P 3 included in the management screen request is stored in the user table 38 . Then, in T 324 , the printer 10 sends the management screen data to the PC 100 C (S 46 ).

When receiving the management screen data from the printer 10 in T 324 , the PC 100 C displays the management screen D 11 (see FIG. 13 ) in T 330 . Then, when accepting a selection of the preset setting button in T 332 , the PC 100 C sends a preset setting screen request to the printer 10 in T 334 .

When receiving the preset setting screen request from the PC 100 C in T 334 (YES in S 50 ), the printer 10 sends the preset setting screen data to the PC 100 C in T 336 (S 52 ).

When receiving the preset setting screen data from the printer 10 in T 336 , the PC 100 C displays the preset setting screen D 12 (see FIG. 13 ) in T 340 . When accepting a selection of the new registration button in T 342 , the PC 100 C sends an input screen request to the printer 10 in T 344 .

When receiving the input screen request from the PC 100 C in T 344 (YES in S 60 ), the printer 10 sends the input screen data to the PC 100 C in T 346 (S 62 ).

When receiving the input screen data from the printer 10 in T 346 , the PC 100 C displays the input screen D 13 (see FIG. 13 ) in T 350 . In T 352 , the PC 100 C accepts an operation of checking the checkboxes corresponding to “two-sided” and “color”, an input of the preset name “IPR 2 ” to the preset name input box, and an input of the user name U 3 to the registration user name input box. In this case, the PC 100 C creates preset information PI 3 in which the inputted preset name IPR 2 is associated with the set print setting information “two-sided” and “color”, and sends a registration instruction including the preset information PI 3 and the registration user name U 3 to the printer 10 in T 354 .

When receiving the registration instruction from the PC 100 C in T 354 (YES in S 64 ), the printer 10 determines that the registration permission flag associated with the authenticated user name U 3 is “ON” in the user table 38 (YES in S 90 of FIG. 5 ) and determines that the preset information PI 3 includes a restricted print condition (i.e., “two-sided”) associated with the target-registration user name U 3 (YES in S 92 ). In this case, the printer 10 sends the selection screen data for displaying the selection screen to the PC 100 C in T 356 (S 100 ).

When receiving the selection screen data from the printer 10 in T 356 , the PC 100 C displays the selection screen D 14 in T 360 . When accepting a selection of the OK button in T 362 , the PC 100 C sends a change instruction to the printer 10 in T 364 .

When receiving the change instruction from the PC 100 C in T 364 (YES in S 102 ), the printer 10 replaces the restricted print condition (“two-sided”) included in the preset information PI 3 received in T 354 with the permitted print condition (“one-sided”) to create new preset information PI 5 in T 366 (S 104 ). In a variant, the printer 10 may create new preset information that does not include any print condition corresponding to the print setting item “print type” in the preset information PI 3 and only includes the print condition “color” corresponding to the print setting item “number of colors” in the preset information PI 3 . That is, the printer 10 may create new preset information that does not include any print setting item corresponding to the restricted print condition included in the preset information PI 3 and only includes a print setting item corresponding to the permitted print condition included in the preset information PI 3 . Next, the printer 10 registers the preset information PI 5 to the preset table 40 in T 368 (S 106 ), and registers the preset name “IPR 2 ” to the user table 38 as a registered preset name associated with the target-registration user name U 3 in T 370 (S 108 ). Then, the printer 10 sends the completion notification screen data to the PC 100 C in T 372 (S 98 ).

(Effects of Cases A to D)

As shown in Case A of FIG. 8 , the printer 10 registers the preset information PI 2 to the preset table 40 (T 56 ) in the case of determining that the preset information PI 2 includes no restricted print condition associated with the user name U 2 in the user table 38 . On the other hand, as shown in Case D of FIG. 10 , the printer 10 sends the selection screen data to the PC 100 C (T 356 ) in the case of determining that the preset information PI 3 includes the restricted print condition associated with the user name U 3 in the user table 38 . Then, when receiving the change instruction from the PC 100 C (T 364 ), the printer 10 registers the preset information PI 5 to the preset table 40 (T 368 ). As such, even in the case of receiving the preset information PI 3 including the restricted print condition, the printer 10 can register preset information to the preset table 40 according to the selection result by the user.

Further, in Case D of FIG. 10 , when receiving the change instruction from the PC 100 C (T 364 ), the printer 10 registers to the preset table 40 the preset information PI 5 in which the restricted print condition (“two-sided”) has been replaced with the permitted print condition (“one-sided”) (T 368 ). Therefore, the user who uses the PC 100 C can execute printing by using the preset information PI 5 thereafter.

(Case E; FIG. 11 )

Case E will be described with reference to FIG. 11 . In Case E, a print process is executed using preset information in the preset table 40 . An initial state of Case E is a state after Case D, that is, the preset information PI 1 , PI 2 , and PI 5 are stored in the preset table 40 . T 410 to T 422 are the same as T 10 to T 22 of FIG. 8 . When the user authentication succeeded in T 422 (YES in S 124 of FIG. 6 ), the printer 10 identifies in the user table 38 the preset names “DPR” and “IPR 1 ” associated with the user name for which the user authentication succeeded, and then identifies the preset information PI 1 and PI 2 including the identified preset names “DPR”, “IPR 1 ” in the preset table 40 . Then, the printer 10 sends to the PC 100 B capability information including all the print conditions which the printer 10 can execute (“one-sided”, “two-sided”, “monochrome”, “color”) and the identified preset information PI 1 , PI 2 in T 424 .

T 430 and T 432 are the same as T 30 and T 34 , respectively. In this case, the PC 100 B displays a preset name selection image over the print setting screen D 1 . The preset name selection image of the present case includes the preset names “DPR” and “IPR 1 ” and “new registration”. When accepting a selection of the preset name “IPR 1 ” in the preset name selection image in T 436 , the PC 100 B identifies the preset information PI 2 including the preset name “IPR 1 ” in the capability information received in T 424 . Then, the PC 100 B identifies the print conditions “one-sided” and “color” in the identified preset information PI 2 , and conforms the print setting on the print setting screen to the identified print conditions in T 438 . Specifically, the PC 100 B unchecks the checkbox corresponding to “monochrome” and checks the checkbox corresponding to “color”. As above, in response to the preset name being selected by the user, the printer 10 conforms the print setting on the print setting screen to the print setting information in the preset information including the preset name. When accepting a selection of the OK button in T 440 , the PC 100 B sends a VJ according to IPP to the printer 10 in T 450 . The VJ includes the print setting (i.e., “one-sided”, “color”).

When receiving the VJ from the PC 100 B in T 450 , the printer 10 determines that the print setting (i.e., “one-sided”, “color”) included in the VJ can be executed, and sends a 200OK to the PC 100 B in T 452 (S 160 ). The 200OK is not a command defined by IPP but is a command defined by HTTP, and it is specifically a command indicating that a process had been normally completed.

When receiving the 200OK from the printer 10 in T 452 , the PC 100 B sends a Create-Job command (hereinbelow termed “CJ”) according to IPP to the printer 10 in T 454 . The CJ includes the print setting (i.e., “one-sided”, “color”).

When receiving the CJ from the PC 100 B in T 454 , the printer 10 creates a unique job ID “J 1 ” in T 456 , and sends a 200OK including the created job ID “J 1 ” to the PC 100 B in T 458 (S 160 ).

When receiving the 200OK from the printer 10 in T 458 , the PC 100 B sends a Send-Document command (hereinbelow termed “SD”) according to IPP to the printer 10 in T 460 . The SD includes print data and the job ID “J 1 ” included in the received 200OK.

When receiving the SD from the PC 100 B in T 460 , the printer 10 identifies the print setting (i.e., “one-sided”, “color”) corresponding to the job ID “J 1 ” included in the SD, and executes printing according to the print data in the SD and the identified print setting in T 462 (S 160 ). Then, the printer 10 sends a 200OK to the PC 100 B in T 464 .

(Effects of Present Embodiment)

The printer 10 receives from one of the PCs the user name and a registration instruction or an SPA including registration-target preset information (S 42 , YES in S 64 of FIG. 4 , YES in S 120 , YES in S 150 of FIG. 6 ). Then, in the case where the registration permission flag associated with the received user name is “ON” in the user table 38 in the memory 34 (YES in S 90 of FIG. 5 , YES in S 180 of FIG. 7 ), the printer 10 registers the preset information to the preset table 40 in the memory 34 (S 94 of FIG. 5 , S 184 of FIG. 7 ). On the other hand, in the case where the registration permission flag associated with the received user name is “OFF” in the user table 38 in the memory 34 (NO in S 90 of FIG. 5 , NO in S 180 of FIG. 7 ), the printer 10 does not register the preset information to the preset table 40 in the memory 34 . Thus, the printer 10 can suitably restrict the registration of the preset information to the preset table 40 in the memory 34 in accordance with the registration permission flag associated with a user name in the user table 38 in the memory 34 . In other words, by setting the registration permission flags in the user table 38 of the printer 10 , the administrator of the printer 10 can set whether or not the users who use the user names in the user table 38 are permitted to register preset information to the preset table 40 .

(Corresponding Relationships)

The PCs 100 A to 100 D are examples of “external device”. The user name and the registration permission flag are respectively examples of “user identification information” and “registration related information”. The registration instruction and the SPA including registration-target preset information are examples of “registration request”. “ON” and “OFF” of the registration permission flag are respectively examples of “permission information” and “restriction information”. The GPA is an example of “capability information request”. The top screen data request is an example of “access request”. The user name and the password described in a header of the capability information request are examples of “user identification information”. T 42 of FIG. 8 is an example of “first predetermined operation”. The top screen and the top screen data are respectively examples of “acceptance screen” and “acceptance screen data”. T 352 of FIG. 10 is an example of “second predetermined operation”. The print setting items “print type” and “number of colors” are examples of “specific setting item”. The print setting information in each of the preset information PI 2 , PI 3 , and PI 4 is an example of “first print setting information”. The print setting information in the preset information PI 5 is an example of “second print setting information”.

S 42 of FIG. 4 and S 120 and S 150 of FIG. 6 are examples of “receive first user identification information”. S 64 of FIG. 4 and S 150 of FIG. 6 are examples of “receive a registration request”. S 94 of FIG. 5 and S 184 of FIG. 7 are examples of “register the first print setting information”.

Second Embodiment

In the present embodiment, a first registration process ( FIG. 5 ) and a second registration process ( FIG. 7 ) executed by the printer 10 differ from those of the first embodiment. In the first registration process of FIG. 5 , the CPU 32 of the printer 10 skips S 92 and proceeds to S 94 in the case of determining YES in S 90 . Further, in the second registration process of FIG. 7 , the CPU 32 skips S 182 and proceeds to S 184 in the case of determining YES in S 180 .

(Specific Cases F and G; FIGS. 14 and 15 )

Specific Cases F and G realized by the processes of FIGS. 3 to 7 of the present embodiment will be described with reference to FIGS. 14 and 15 .

(Case F; FIG. 14 )

Case F will be described with reference to FIG. 14 . In Case F, preset information is registered to the preset table 40 using communication according to IPP. An initial state of Case F is the same as the initial state of Case B.

Firstly, processes same as T 10 to T 30 of FIG. 8 and T 132 to T 142 of FIG. 9 are executed between the PC 100 C and the printer 10 . In the present case, the PC 100 C accepts an input of the user name U 3 and the password P 3 in T 18 , and sends a GPA including the user name U 3 and the password P 3 to the printer 10 in T 20 .

T 550 to T 554 are the same as T 150 to T 154 of FIG. 9 . When receiving the SPA from the PC 100 C in T 554 (NO in S 10 , YES in S 20 of FIG. 3 , NO in S 120 , YES in S 150 of FIG. 6 ), the printer 10 determines that the registration-target preset information PI 3 is included in the SPA (YES in S 152 ). Then, the printer 10 determines that the registration permission flag associated with the user name U 3 included in the SPA is “ON” in the user table 38 (YES in S 180 ), registers the preset information PI 3 to the preset table 40 in T 556 (S 184 ), and registers the preset name “IPR 2 ” to the user table 38 as a registered preset name associated with the user name U 3 included in the SPA in T 558 (S 186 ). Then, in T 560 , the printer 10 sends the registration completion information to the PC 100 C (S 188 ).

(Case G; FIG. 15 )

Case G will be described with reference to FIG. 15 . In Case G, a print process is executed using preset information in the preset table 40 .

T 610 to T 622 are the same as T 410 to T 422 of FIG. 11 . In the present case, the PC 100 C accepts an input of the user name U 3 and the password P 3 in T 618 , and sends a GPA including the user name U 3 and the password P 3 to the printer 10 in T 620 .

When the user authentication succeeded in T 622 (YES in S 124 of FIG. 6 ), the printer 10 identifies the preset names “DPR” and “IPR 2 ” associated with the authenticated user name U 3 in the user table 38 , and identifies the preset information PH and PI 3 including the identified preset names “DPR” and “IPR 2 ” in the preset table 40 . Then, the printer 10 determines whether or not each of the print setting information in the identified preset information PI 1 and PI 3 includes a restricted print condition associated with the authenticated user name U 3 in user table 38 . Then, the printer 10 determines that the print setting information in the preset information PI 3 includes the restricted print condition “two-sided” associated with the authenticated user name U 3 in the user table 38 . In this case, the printer 10 determines that the preset information PI 3 is preset information that is not to be sent. Then, in T 624 , the printer 10 sends to the PC 100 C capability information including all the print conditions which the printer 10 can execute (“one-sided”, “two-sided”, “monochrome”, “color”) and the identified preset information PI 1 . If the printer 10 receives a GPA including the user name U 3 from the PC 100 C after the print condition “two-sided” associated with the user name U 3 in the user table 38 has been changed from “OFF” to “ON” by the administrator, the printer 10 sends the preset information PI 3 to the PC 100 C. In a variant, the printer 10 may create preset information by replacing the restricted print condition (“two-sided”) included in the preset information PI 3 with the permitted print condition (“one-sided”) and send capability information including the created preset information to the PC 100 C.

T 630 to T 640 are the same as T 430 to T 440 of FIG. 9 except that the preset name DPR is selected. Further, T 650 to T 664 are the same as T 450 to T 464 except that the print conditions are “one-sided” and “monochrome” and the job ID is “J 2 ”.

(Effects of Cases F and G)

As shown in Case F of FIG. 14 , the printer 10 registers the preset information PI 3 to the preset table 40 (T 556 ) regardless of whether or not the preset information PI 3 sent from the PC 100 C includes a restricted print condition. Further, as shown in Case G of FIG. 15 , when receiving the GPA from the PC 100 C (T 620 ), the printer 10 does not send the preset information PI 3 including the restricted print condition to the PC 100 C (T 624 ). As such, it can be prevented that printing fails in response to the user who uses the PC 100 C selecting the preset information PI 3 including the restricted print condition and the VJ including the restricted print condition being sent.

Third Embodiment

In the present embodiment, a web server process ( FIG. 16 ), a first registration process ( FIG. 17 ), an IPP process ( FIG. 18 ), and a second registration process ( FIG. 19 ) executed by the printer 10 differ from those of the first embodiment. Hereinbelow, processes that are the same as those of the first embodiment will be given the same step numbers and descriptions thereof will be omitted.

(Web Server Process; FIG. 16 )

The CPU 32 proceeds to S 245 A in the case of determining YES in S 44 . S 245 A is the same as S 90 of FIG. 5 . The CPU 32 proceeds to S 245 B in a case of determining NO in S 245 A. On the other hand, the CPU 32 skips S 245 B and proceeds to S 46 in a case of determining YES in S 245 A.

In S 245 B, the CPU 32 sends a first restriction request to the PC. The first restriction request is information for requesting restriction on sending of a registration instruction. When S 245 B is completed, the CPU 32 proceeds to S 46 . Here, the timing at which the first restriction request is sent is not limited to after S 245 A. The CPU 32 may send the first restriction request to the PC before or simultaneously with sending the preset setting screen data to the PC.

(First Registration Process; FIG. 17 )

The first registration process of the present embodiment does not include S 90 of FIG. 5 . Except for that, the first registration process of the present embodiment is the same as the first registration process of the first embodiment ( FIG. 5 ).

(IPP Process; FIG. 18 )

The CPU 32 proceeds to S 325 in the case of determining YES in S 124 . S 325 is the same as S 180 of FIG. 7 . The CPU 32 proceeds to S 126 in a case of determining YES in S 325 . On the other hand, the CPU 32 proceeds to S 326 in a case of determining NO in S 325 .

In S 326 , the CPU 32 sends capability information to the PC. This capability information includes a second restriction request. Except for that, the capability information is the same as the capability information sent to the PC in S 126 . The second restriction request is information for requesting restriction on sending of an SAP including registration-target preset information. In a variant, the CPU 32 may send the second restriction request to the PC separately from the capability information.

(Second Registration Process; FIG. 19 )

The second registration process of the present embodiment does not include S 180 of FIG. 7 . Except for that, the second registration process of the present embodiment is the same as the second registration process of the first embodiment ( FIG. 7 ).

(Specific Cases H and I; FIG. 20 )

Specific Cases H and I realized by the processes of FIGS. 16 to 19 of the present embodiment will be described with reference to FIGS. 20 to 22 .

(Case H; FIG. 20 )

Case H will be described with reference to FIG. 20 . In Case H, the registration of preset information using communication according to IPP is restricted due to the registration permission flag in the user table 38 being “OFF”. An initial state of Case H is the same as the initial state of Case B shown in FIG. 9 .

Firstly, processes same as T 10 to T 22 of FIG. 8 are executed between the PC 100 D and the printer 10 . In the present case, the PC 100 D accepts an input of the user name U 4 and the password P 4 in T 18 , and sends a GPA including the user name U 4 and the password P 4 to the printer 10 in T 20 .

The printer 10 determines in T 22 that the user authentication succeeded (YES in S 124 of FIG. 18 ), and determines that the registration permission flag associated with the user name U 4 included in the GPA is “OFF” in the user table 38 (NO in S 325 ). In this case, in T 724 , the printer 10 sends to the PC 100 D capability information including all the print conditions which the printer 10 can execute (i.e., “one-sided”, “two-sided”, “monochrome”, “color”), the preset information PI 1 , and the second restriction request.

When receiving the capability information from the printer 10 in T 724 , the PC 100 D displays the print setting screen D 1 (see FIG. 12 ) in T 730 . T 732 and T 734 are the same as T 32 and T 34 of FIG. 8 , respectively. When accepting a selection of the pull-down, the PC 100 D determines that the capability information received in T 724 includes the second restriction request, and displays a preset selection image N 31 over the print setting screen D 1 in T 736 . As shown in FIG. 21 , the image N 31 includes a list image of selectable preset names, but does not include a new registration image for registration of new preset information (see FIG. 12 ). In a variant, the image N 31 may include a disabled new registration image. As a result, the user who uses the PC 100 D can acknowledge that the registration of preset information is restricted. In T 740 , the PC 100 D accepts a selection of the cancel button.

(Case I; FIG. 20 )

Next, Case I will be described with reference to FIG. 20 . In Case I, the registration of preset information using the web server function of the printer 10 is restricted due to the registration permission flag in the user table 38 being “OFF”. An initial state of the Case I is the same as the initial state of Case H.

Firstly, processes same as T 310 to T 322 of FIG. 10 are executed between the PC 100 D and the printer 10 . In the present case, the PC 100 D accepts an input of the user name U 4 and the password P 4 in T 318 , and sends a management screen request including the user name U 4 and the password P 4 to the printer 10 in T 320 .

The printer 10 determines in T 322 that the user authentication succeeded (YES in S 44 of FIG. 16 ), determines that the registration permission flag associated with the authenticated user name U 4 is “OFF” in the user table 38 (NO in S 245 A), and sends the first restriction request to the PC 100 D in T 823 . T 824 to T 836 are the same as T 324 to T 336 of FIG. 10 . The PC 100 D determines that the first restriction request has been received, and displays a preset setting screen D 32 in T 840 . As shown in FIG. 22 , the screen D 32 does not include a new registration button. Except for that, the screen D 32 is the same as the preset setting screen D 12 of the first embodiment (see FIG. 13 ). In a variant, the screen D 32 may include a disabled new registration button. As a result, the user who uses the PC 100 D can acknowledge that the registration of preset information is restricted. In T 850 , the PC 100 D accepts a selection of the cancel button.

Effects of Present Embodiment

The printer 10 receives the user name from the PC (S 42 of FIG. 16 , YES in S 120 and YES in S 122 of FIG. 18 ). Then, the printer 10 receives a registration instruction or an SAP including registration-target preset information from the PC in a state where the registration permission flag associated with the received user name is “ON” in the user table 38 in the memory 34 (YES in S 64 of FIG. 16 , YES in S 150 and S 152 of FIG. 18 ). In this case, the printer 10 registers the preset information to the preset table 40 in the memory 34 (S 94 of FIG. 17 , S 184 of FIG. 19 ). On the other hand, in the case where the registration permission flag associated with the received user name is “OFF” in the user table 38 in the memory 34 (NO in S 245 A of FIG. 16 , NO in S 325 of FIG. 18 ), the printer 10 sends the first restriction request or the second restriction request to the PC (S 245 B of FIG. 16 , S 326 of FIG. 18 ). In this case, the printer 10 does not receive a registration instruction nor an SAP including registration-target preset information from the PC. Therefore, the printer 10 does not register preset information to the preset table 40 in the memory 34 . Thus, the printer 10 can suitably restrict the registration of preset information to the preset table 40 in the memory in accordance with the registration permission flag associated with a user name in the user table 38 in the memory 34 . In other words, by setting the registration permission flags in the user table 38 of the printer 10 , the administrator of the printer 10 can set whether or not the users who use the user names in the user table 38 are permitted to register preset information to the preset table 40 .

(Corresponding Relationships)

The first restriction request and the second restriction request are examples of “restriction request”. The registration instruction and the SAP including registration-target preset information is an example of “registration request”. S 42 of FIG. 16 and S 120 of FIG. 18 are examples of “receive first user identification information”. S 245 B of FIG. 16 and S 326 of FIG. 18 are examples of “send a restriction request”. S 64 of FIG. 16 and S 150 of FIG. 18 are examples of “receive the registration request”. S 94 of FIG. 17 and S 184 of FIG. 19 are examples of “register the first print setting information”.

(First Variant) In a case of receiving a command including only registration-target preset information (i.e., a registration command) instead of the SPA, the printer 10 may register the preset information included in the command to the preset table 40 . Further, the SPA may include only registration-target preset information.

(Second Variant) After T 42 of FIG. 8 , the PC 100 B may extract the preset information PI 1 in the capability information received in T 24 and send an SPA including the user name U 2 , the password P 2 , and the preset information PI 1 , PI 2 to the printer 10 in T 54 . In this variant, T 50 and T 52 may be omitted. T 150 , T 152 , T 250 , and T 252 of FIG. 9 and T 550 and T 552 of FIG. 14 may also be omitted.

(Third Variant) The second registration process of FIG. 7 may be omitted. In this variant, “receive first capability information request” and “send the capability information” may be omitted.

(Fourth Variant) The first registration process of FIG. 5 may be omitted. In this variant, “receive an access request” and “send acceptance screen data” may be omitted.

(Fifth Variant) The message displayed on the selection screen may be a message for checking whether preset information including a restricted print condition is to be registered. In this variant, the printer 10 monitors receipt of a registration instruction in S 102 and proceeds to S 94 in a case of determining YES in S 102 . In this variant, S 104 to S 108 may be omitted.

(Sixth Variant) The PCs 100 A to 100 D may each send the management screen request in the case of accepting an input of the IP address assigned to the printer 10 . In this variant, the printer 10 sends the authentication screen data to the PC in a case of receiving the preset setting screen request or the input screen request. In another variant, the management screen or the preset setting screen may include an image for input of a user name and a password. In yet another variant, a screen for input of a user name and a password may be displayed in the case where the new registration button is selected.

(Seventh Variant) In S 104 of FIG. 5 , the CPU 32 of the printer 10 may change the restricted print condition included in the print setting information in the target preset information to the permitted print condition in the user table 38 . That is, in a case where the print setting information in the target preset information includes a restricted print condition associated with the authenticated user name in the user table 38 , this restricted print condition may be changed. In other words, in the case where the print setting information in the target preset information includes a restricted print condition associated with the authenticated user name in the user table 38 , the restricted print condition in the user table 38 may be changed from “OFF” to “ON” such that the print setting information in the target preset information may be changed to include the permitted print condition associated with the authenticated user name in the user table 38 . In this variant, When S 104 is completed, the CPU 32 proceeds to S 94 .

(Eighth Variant) In the second embodiment, the printer 10 may send capability information including all the print conditions which the printer 10 can execute (“one-sided”, “two-sided”, “monochrome”, “color”) and the preset information PI 1 , PI 3 to the PC 100 C in T 624 of FIG. 15 . In this variant, the printer 10 sends the preset information to the PC regardless of whether or not the preset information includes a restricted print condition.

(Ninth Variant) In the above embodiments, the respective processes executed by the controller 30 are realized by software (i.e., the program 36 ), however, at least one of these processes may be realized by hardware such as a logic circuit.