JP2017049718A - Function execution device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique for limiting use of a function according to a user in such a situation that execution of a function is instructed from a server through the Internet.SOLUTION: A MFP (Multifunction Peripheral) 100 determines whether or not a user is permitted to execute a printing function on the basis of user information and permission information when accepting an input operation for inputting the user information. The MFP 100 registers related information for causing a terminal device 20 to display an input screen SC1 which is capable of inputting the user information on a server 10 (T144) and acquires a printing job including the user information from the server 10 (T170) after the terminal device 20 logs in the server 10 and displays the input screen SC1. The MFP 100 determines whether or not a user is permitted to execute the printing function on the basis of the user information included in the printing job and permission information.SELECTED DRAWING: Figure 5

Description

  The present specification relates to a function execution device for executing a specific function.

  There is known a function execution device that restricts a function that can be used for each user. For example, the network facsimile apparatus of Patent Literature 1 includes an operation display unit including a plurality of general-purpose keys that can be operated by the user, and executes a function assigned to the general-purpose key operated by the user. The apparatus stores a user ID and an assigned function attribute in association with each other. Then, the device performs authentication of the user ID and invalidates the operation of the general-purpose key based on the assigned function attribute associated with the user ID, so that the user corresponding to the user ID can Restrict access to functions assigned to keys.

JP 2005-167957 A JP2013-003645A

  In the technique of Patent Document 1, no consideration is given to a situation in which a network facsimile apparatus is instructed to execute a function from a server via the Internet. Even in such a situation, there is a need for a technique for restricting the use of functions depending on the user. The present specification provides a technique for restricting the use of a function according to a user in a situation where the function execution apparatus is instructed to execute the function from a server via the Internet.

  A function execution device disclosed in this specification includes a function execution engine for executing a specific function, an operation unit, and an input operation for the operation unit to input first user information from a first user. The first user information and the permissible information stored in the storage unit, indicating whether the user is permitted to execute the specific function for each of one or more users A first determination unit that determines whether or not the first user is allowed to execute the specific function based on the permission information; and a determination that the first user is allowed to execute the specific function. If the function execution engine causes the function execution engine to execute the specific function, and it is determined that the first user is not allowed to execute the specific function, the function execution engine executes the specific function. A function control unit, and a registration unit for registering first related information related to the function execution device to a server via the Internet, the first related information being a first for inputting user information The registration unit including the first display information for causing the terminal device to display a first input screen including one area and the terminal device log in to the server and display the first input screen. Later, when second user information and an instruction to execute the specific function are input to the first input screen by a second user of the terminal device, the server sends the first information via the Internet. An acquisition unit that acquires first execution information including two pieces of user information, the second user information included in the first execution information when the first execution information is acquired, and the storage Stored in the department Wherein the permission information, based on, and a second determination unit for determining whether to allow the second user to execute the specific function. The function control unit further causes the function execution engine to execute the specific function when it is determined that the second user is allowed to execute the specific function, and executes the specific function. When it is determined that the second user is not allowed, the function execution engine is not allowed to execute the specific function.

  According to said structure, a function execution apparatus registers the 1st relevant information containing 1st display information with a server. Thus, when the terminal device logs in to the server, the first input screen including the first area for inputting the user information is displayed on the terminal device. And a specific function execution instruction can be input to the first input screen. In this case, since the function execution device acquires the first execution information including the second user information from the server, the use of the specific function can be restricted based on the second user information and the permission information. As described above, the function execution device can restrict the use of the function in a situation where the execution of the function is instructed from the server via the Internet.

  A control method, a computer program, and a computer-readable recording medium for storing the computer program for realizing the function execution apparatus are also novel and useful.

1 shows a configuration of a communication system. The sequence diagram for demonstrating a mode that utilization of a printing function is restrict | limited in various situations is shown. The sequence diagram of each process common to the 1st-6th Example is shown. 6 shows a flowchart of job acquisition processing according to the first to fourth embodiments. The sequence diagram showing the specific case of 1st and 3rd Example is shown. The sequence diagram showing the specific case of 2nd Example is shown. 10 shows a flowchart of processing at the time of job acquisition according to a fifth embodiment. The sequence diagram showing the specific case of 5th Example is shown. 10 shows a flowchart of a job acquisition process according to a sixth embodiment. The sequence diagram showing the specific case of 6th Example is shown.

(First embodiment)
(Configuration of communication system 2; FIG. 1)
As shown in FIG. 1, the communication system 2 includes an MFP (abbreviation of Multifunction Peripheral) 100, a print mediation server 10, and a plurality of terminal devices 20 and 30. The MFP 100 and the terminal device 30 can communicate with each other via a LAN (abbreviation of Local Area Network) 4. The MFP 100 can communicate with the print mediation server 10 via the LAN 4 and the Internet 6. The terminal device 20 can communicate with the print mediation server 10 via the Internet 6.

(Configuration of MFP 100)
The MFP 100 is a peripheral device (that is, a peripheral device such as the terminal device 30) that can execute a plurality of functions including a print function, a scan function, a copy function, and the like. The MFP 100 includes an operation unit 102, a display unit 104, a print engine 106, a scan engine 108, a network interface 110, and a control unit 120. Each unit 102 to 120 is connected to a bus line (reference numeral omitted). Hereinafter, the interface is described as “I / F”.

  The operation unit 102 includes a plurality of keys. The user can input various instructions to the MFP 100 by operating the operation unit 102. The display unit 104 is a display for displaying various information. The display unit 104 functions as a so-called touch panel. That is, the display unit 104 also functions as an operation unit operated by the user. The print engine 106 includes a printing mechanism such as an inkjet method or a laser method. The scan engine 108 includes a scan mechanism such as a CCD (abbreviation for Charge Coupled Device), CIS (abbreviation for Contact Image Sensor), or the like. The network I / F 110 is an interface for executing wired communication, and is connected to the LAN 4. However, in a modification, the network I / F 110 may be an interface for executing wireless communication, and in this case, the LAN 4 is a so-called wireless LAN.

  The control unit 120 includes a CPU 122 and a memory 124. The CPU 122 executes various processes according to the program 126 stored in the memory 124. The memory 124 is configured by a volatile memory, a nonvolatile memory, or the like. The memory 124 stores a restriction flag 128 and a restriction table 132 in addition to the program 126 described above. In FIG. 1, the account flag 130 is shown in the memory 124. However, in the present embodiment, the memory 124 does not store the account flag 130. The account flag 130 is used in fifth and sixth embodiments described later.

  The restriction flag 128 indicates that “ON” means that the function use restriction corresponding to each user is executed using the restriction table 132 and that the function use restriction is not executed (that is, the restriction table 132 is not used). It means either “OFF” meaning. The restriction flag 128 is set to “ON” or “OFF” by the administrator of the MFP 100.

  One or more pieces of combination information are registered in the restriction table 132. Each combination information is a combination of an ID (abbreviation of Identification Data), a password, print permission information, and scan permission information. Each combination information is registered in the restriction table 132 when, for example, the administrator of the MFP 100 accesses the MFP 100 from a terminal device (for example, 30). Each combination information is roughly classified into individual information and general information. The individual information is information corresponding to an individual user (that is, an individual user), and a user ID (for example, “Bob”, “John”) for identifying the individual user and a password (for example, “P1”, “P2”). )). The general information is information corresponding to a general user who is all users other than each individual user corresponding to each individual information, includes a user ID “Public” indicating the general user, and does not include a password.

  The print permission information and the scan permission information are information indicating whether the user is permitted to execute the print function and the scan function, respectively. “OK” indicates that the execution of the function is permitted, and “NG” indicates that the execution of the function is not permitted.

(Configuration of the print mediation server 10)
The print mediation server 10 is a server for mediating communication for causing a communication device (for example, the terminal device 20) to execute the print function in the MFP 100, and is installed on the Internet 6 by a provider different from the vendor of the MFP 100. . An example of the business operator is Google (registered trademark). In the modification, the print mediation server 10 may be a server installed by the vendor of the MFP 100.

  A plurality of account information for a plurality of users is registered in the memory 12 of the print mediation server 10. The account information is information for logging in to the print mediation server 10, and normally includes an account ID and a password. Although not shown, in the memory 12, account information can be associated with device information such as an MFP and a printer. The device information is identification information for identifying a device that can be used by the user corresponding to the account information associated with the device information. Further, in the memory 12, another account information can be further associated with the account information associated with the device information. That is, another account ID can be associated with the account ID. In the example of FIG. 1, it is assumed that an account ID “Ken@example.com” for the user (for example, “Ken”) is associated with the device information of the MFP 100. An account ID (for example, “Bob@example.com”) for a different user (for example, “Bob”) is further associated with the account ID “Ken@example.com”. This means that the account ID “Bob@example.com” is associated with the device information of the MFP 100 via the account ID “Ken@example.com”. Thus, for example, if the user “Bob” logs in to the server 10 using his / her account ID “Bob@example.com”, the device information associated with the account ID “Ken@example.com” is used. The identified MFP 100 can be used. In this embodiment, the user who uses the account ID “Ken@example.com” is an administrator of the MFP 100, and each account ID for each individual user is registered in association with the account ID for the administrator. The Therefore, not only the administrator but also each individual user can use the server 10 to cause the MFP 100 to execute the printing function.

(Configuration of terminal devices 20 and 30)
Each of the terminal devices 20 and 30 is a user terminal such as a desktop PC (abbreviation of Personal Computer), a notebook PC, a tablet PC, a mobile phone, or a smartphone. The terminal device 30 includes a memory 32, and the memory 32 stores a driver program 34 for causing the MFP 100 to execute a printing function. For example, the driver program 34 may be installed in the terminal device 30 from a medium shipped with the MFP 100, or may be installed in the terminal device 30 from a server on the Internet provided by the vendor of the MFP 100. The terminal device 20 does not store the driver program 34. The terminal device 20 can cause the MFP 100 to execute the print function using the print mediation server 10 without using the driver program 34.

(Specific case of function usage restriction in MFP 100; FIG. 2)
With reference to FIG. 2, a specific case of function usage restriction in MFP 100 will be described. In the initial state of FIG. 2, the memory 124 stores a restriction flag 128 indicating “ON”. First, usage restrictions on the direct printing function will be described. The direct printing function is a function in which the MFP 100 acquires a file to be printed from a medium (for example, a USB memory) without using a network, and executes printing according to the file.

  In T10, the CPU 122 displays an input screen for inputting user information including a user ID and a password on the display unit 104, and accepts an input operation for inputting user information via the operation unit 102. In this case, the CPU determines whether to allow the user to execute the direct printing function based on the input user information and the print permission information in the restriction table 132, and according to the determination result. The subsequent processing is executed.

  For example, as shown in case N1, when user information including a user ID “Bob” and a password “P1” is input, at T12, the CPU reads the user ID “Bob” and the password “P” from the restriction table 132. The print permission information “OK” associated with “P1” is acquired (see FIG. 1), and it is determined that the individual user corresponding to the user ID “Bob” is permitted to use the print function. Then, the CPU causes the display unit 104 to display a print icon for inputting a direct print instruction. Next, at T <b> 14, the CPU accepts an operation for selecting a print icon, that is, an input operation of a direct print instruction via the operation unit 102. In this case, at T16, the CPU causes the print engine 106 to execute the direct printing function. Specifically, the CPU acquires a file to be printed from a medium (not shown), converts the data in the file, and generates print data having a format that can be interpreted by the print engine 106. Then, the CPU supplies print data to the print engine 106. As a result, the print engine 106 executes printing of the image represented by the print data.

  Further, for example, as shown in case N2, when user information including the user ID “John” and the password “P2” is input, the CPU reads the user ID “John” and the password “John” from the restriction table 132. The print permission information “NG” associated with “P2” is acquired (see FIG. 1), and it is determined that the individual user corresponding to the user ID “John” is not permitted to use the print function. In this case, the CPU does not display the print icon on the display unit 104. For this reason, the individual user corresponding to the user ID “John” cannot select the print icon. As a result, the CPU does not cause the print engine 106 to execute the direct printing function.

  Although not shown, the MFP 100 can execute, for example, restriction on the use of the scan function as well as restriction on the use of the direct printing function. The CPU determines whether to allow the user to execute the scan function based on the input user information and the scan allowance information in the restriction table 132. The CPU executes subsequent processing according to the determination result. For example, in the case N1 described above (that is, in the case of the user ID “Bob”), the CPU acquires the scan permission information “NG” from the restriction table 132 (see FIG. 1), and is permitted to use the scan function. Judge that it is not. In this case, the CPU does not cause the display unit 104 to display a scan icon for inputting a scan instruction. As a result, the CPU does not cause the scan engine 108 to execute the scan function. Further, in the case of the above case N2 (that is, in the case of the user ID “John”), the CPU acquires the scan permission information “OK” from the restriction table 132 (see FIG. 1), and the use of the scan function is permitted. And the scan icon is displayed on the display unit 104. When receiving an operation for selecting a scan icon, that is, an input operation of a scan instruction, via the operation unit 102, the CPU drives the scan engine 108 to cause the scan engine 108 to execute a scan function.

  Next, usage restrictions on the printing function in a situation where an execution instruction is acquired from the terminal device 30 will be described. In T20, the terminal device 30 receives an input operation of user information and a print instruction. Specifically, when receiving an operation for starting the driver program 34 in a state where a file to be printed is selected, the terminal device 30 inputs user information and a print instruction according to the driver program 34. Displays the input screen and accepts input operations. In this case, in T22, the terminal device 30 converts the data in the file to be printed to generate print data having a format that can be interpreted by the MFP 100 (that is, the print engine 106), and the input user information, An execution instruction including print data is supplied to MFP 100. In this case, the CPU 122 determines whether or not to allow the user to execute the printing function based on the input user information and the print permission information in the restriction table 132, and thereafter, depending on the determination result. Execute the process.

  For example, as shown in case N3, when user information including the user ID “Bob” and the password “P1” is input, the CPU acquires the print permission information “OK” from the restriction table 132, and prints. Judge that the use of the function is allowed. In T24, the CPU supplies the print data included in the acquired execution instruction to the print engine 106, and causes the print engine 106 to execute the print function.

  Further, for example, as shown in case N4, when user information including the user ID “John” and the password “P2” is input, the CPU acquires the print permission information “NG” from the restriction table 132. Therefore, it is determined that the use of the printing function is not permitted. In this case, at T26, the CPU does not cause the print engine 106 to execute the print function, and supplies the terminal device 30 with a print prohibition notification indicating that the use of the print function is not permitted. Since the terminal device 30 displays the contents of the notification, the user can know that the use of the printing function is not permitted.

  Next, a situation where the restriction flag 128 is changed from “ON” to “OFF” will be described. In T30, the CPU changes the restriction flag 128 from “ON” to “OFF” in response to the operation of the operation unit 102 by the administrator. In T32, the CPU displays a print icon on the display unit 104 without displaying an input screen for inputting user information. In T <b> 34, the CPU accepts an operation for selecting a print icon via the operation unit 102. In this case, at T36, the CPU causes the print engine 106 to execute the direct printing function without using the restriction table 132. In other words, the CPU 132 causes the print engine 106 to execute the direct printing function when receiving a direct printing instruction from any user. Although not shown, when the CPU acquires an execution instruction including print data from the terminal device 20, the CPU executes the print function on the print engine 106 regardless of the user information corresponding to any user. Let In addition, the CPU causes the scan engine 108 to execute the scan function when receiving a scan instruction from any user.

(Case where the print mediation server 10 is used; FIG. 3)
Next, a case where the MFP 100 acquires a print job from the print mediation server 10 via the Internet 6 will be described with reference to FIG. In T40, the CPU 122 logs in to the server 10 using the account ID “Ken@example.com” in accordance with the operation of the operation unit 102 by the administrator. Next, at T <b> 44, the CPU supplies related information related to the MFP 100 to the server 10 using login information to the server 10. Thereby, at T46, the server 10 registers the related information in the memory 12 in association with the account ID “Ken@example.com”. The related information includes capability information indicating the capability (for example, print resolution, number of colors, paper size) of the print engine 106 of the MFP 100. Accordingly, the print mediation server 10 causes the terminal device 20 to display an input screen including a condition area for inputting printing conditions according to the capability information when the terminal device 20 logs in the print mediation server 10, for example. Can do. In the present embodiment, the related information includes authentication area information. Thereby, for example, when the terminal device 20 logs in the print mediation server 10, the print mediation server 10 causes the terminal device 20 to display an input screen including an authentication area for inputting user information corresponding to the authentication area information. be able to. As described above, the MFP 100 can appropriately display the input screen including the authentication area on the terminal device 20 by registering the authentication area information together with the capability information to be registered in the print mediation server 10 in the print mediation server 10. it can. Although details will be described later, in other embodiments, the related information may not include the authentication area information depending on the state of the MFP 100.

  In T50, the terminal device 20 logs in to the print mediation server 10 using the account ID “Bob@example.com” in accordance with a user operation. As described above, in the server 10, the ID is associated with the account ID “Ken@example.com”, and the device information of the MFP 100 is associated with the account ID “Ken@example.com”. ing. Accordingly, if the terminal device 20 logs in to the server 10 using the account ID “Bob@example.com”, the MFP 100 can cause the MFP 100 to execute printing via the server 10. Further, in the server 10, related information is registered in association with the account ID “Ken@example.com” (T46). Accordingly, the server 10 uses the related information registered in T46 in T52 in response to being logged in from the terminal device 20 based on the account ID “Bob@example.com” (that is, in response to a request). Screen data representing the input screen SC is generated, and the generated screen data is supplied to the terminal device 20 at T54.

  In T56, the terminal device 20 displays the input screen SC using the screen data. The input screen SC includes a condition area, an authentication area, an OK button, and a cancel button. The condition area is an area for inputting printing conditions corresponding to the capability information registered in T46, and includes three boxes. The first box is a box for inputting a file name indicating a file to be printed. The second box is a box for inputting the quality of printing, and specifically, a box for inputting the number of colors and the printing resolution. The third box is a box for inputting the paper size. When the capability information includes information indicating a different type of capability from the above-mentioned quality, paper size, etc. (for example, information indicating the presence / absence of double-sided printing), the condition area is further a box corresponding to the information. May be included. The authentication area is an area for inputting user information corresponding to the authentication area information registered in T46. As described above, in another embodiment, the related information registered at T46 may not include the authentication area information. Therefore, in the input screen SC at T56 in FIG. 3, the authentication area is represented by a broken line. . The OK button is a button for inputting a print execution instruction. The cancel button is a button for ending the display of the input screen SC without inputting the instruction. When the terminal device 20 displays the file to be printed and causes the MFP 100 to perform printing via the print mediation server 10, the terminal device 20 displays the input screen SC that does not include the first box. May be.

  At T60, the terminal device 20 accepts input of printing conditions, input of user information, and selection of an OK button on the input screen SC. In this case, at T <b> 62, the terminal device 20 supplies the file to be printed and the job ticket to the print mediation server 10. The file is a file specified by the file name input in the condition area. The job ticket is information for causing the server 10 to store information for generating a print job. Condition information indicating the quality and paper size input in the condition area and the terminal device 20 log in to the server 10. Account ID “Bob@example.com” (hereinafter referred to as “login ID”) and user information (which may not be included in other embodiments) entered in the authentication area.

  Next, at T64, the print mediation server 10 supplies the MFP 100 with a notification indicating that the job ticket has been acquired. In T66, the CPU 122 supplies a request for acquiring a print job to the server 10 in response to the notification. In T68, the server 10 converts the data in the stored file in response to the request, and generates print data having a data format that the MFP 100 can interpret. Here, the server 10 further generates print data corresponding to the print resolution and the paper size indicated by the stored condition information. In T <b> 70, the server 10 supplies the MFP 100 with a print job including generated print data, a login ID, and user information (which may not be included in other embodiments). The print job is job information for causing the MFP 100 to execute a print function. As described above, the print mediation server 10 converts the file to be printed into print data, and supplies the MFP 100 with a print job including the print data. Therefore, even if the terminal device 20 does not include a printer driver for generating print data, the MFP 100 can execute the print function.

  In response to acquiring a print job from the server 10, the CPU 122 executes job acquisition processing. Hereinafter, details of the job acquisition process will be described with reference to FIG.

(Job acquisition processing; Fig. 4)
In S10, the CPU determines whether or not the restriction flag 128 in the memory 124 indicates “ON”. When the restriction flag 128 indicates “ON” (YES in S10), the CPU proceeds to S20, and when the restriction flag 128 indicates “OFF” (NO in S10), the CPU skips the processes of S20 to S30. Then, the process proceeds to S32.

  In S20, the CPU determines whether the user information in the print job includes a user ID. When the user ID and password are input in the authentication area in the input screen SC (see FIG. 3), the user information in the print job includes the user ID, and the user ID and password are not input in the authentication area. When the button is selected, the user information in the print job does not include the user ID (that is, the user information is empty data). When the user information includes the user ID (YES in S20), the CPU proceeds to S22, and when the user information does not include the user ID (NO in S20), the CPU proceeds to S26. In S26, the CPU acquires the print permission information (“NG” in the example of FIG. 1) associated with the user ID “Public” corresponding to the general user from the restriction table 132, and proceeds to S30.

  In S <b> 22, the CPU acquires a password associated with the user ID included in the user information from the restriction table 132. Then, the CPU determines whether or not the password included in the user information matches the acquired password. If the two passwords match (YES in S22), the CPU determines that the user authentication is successful, and proceeds to S24. If the two passwords do not match (NO in S22), It is determined that the user authentication has failed, and the process proceeds to S40. If the combination information including the user ID included in the user information is not registered in the restriction table 132, the CPU determines NO in S22 in response to the fact that the password cannot be acquired from the restriction table 132.

  In S <b> 40, the CPU supplies an authentication error notification indicating that the user authentication has failed to the print mediation server 10. As a result, the notification is supplied from the print mediation server 10 to the terminal device 20, and as a result, the content of the notification is displayed on the terminal device 20. The user can know that the user authentication has failed. When S40 ends, the process of FIG. 4 ends.

  In S24, the CPU acquires print permission information associated with the user ID and password used in S20 and S22 from the restriction table 132, and proceeds to S30.

  In S30, the CPU determines whether to permit execution of the printing function based on the print permission information acquired in S24 or S26. If the print permission information indicates “OK”, the CPU determines that the user is allowed to execute the print function (YES in S30), and proceeds to S32, and if the print permission information indicates “NG”. If it is determined that the user is not allowed to execute the printing function (NO in S30), the process proceeds to S34.

  In S32, the CPU supplies the print data in the print job to the print engine 106, and causes the print engine 106 to execute the print function. In S <b> 34, the CPU supplies the print mediation server 10 with a print prohibition notification indicating that the use of the print function is not permitted. As a result, the notification is supplied from the print mediation server 10 to the terminal device 20, and as a result, the content of the notification is displayed on the terminal device 20. The user can know that the use of the printing function is not permitted. When S32 or S34 ends, the process of FIG. 4 ends.

(Specific case: Fig. 5)
Next, a specific case realized by this embodiment will be described with reference to FIG. T140 to T170 are the same as T40 to T70 in FIG. In the present embodiment, at T144, the related information includes authentication area information AI1 regardless of the state of MFP 100. Accordingly, the input screen SC1 displayed at T156 includes an authentication area AR1 corresponding to the authentication area information AI1. In FIG. 5, the condition area (see FIG. 3) in the input screen SC1 is not shown. Authentication area AR1 includes a box for inputting a user ID and a box for inputting a password. When an OK button is selected after a character string is input to these boxes, user information including a user ID and a password is communicated at T162 and T170. When the OK button is selected in the state where the user ID and password are not input in the authentication area AR1, user information that is empty data is communicated in T162 and T170. When the CPU 122 acquires the print job at T170, the CPU 122 executes the job acquisition processing shown in FIG. 4 to realize the following cases A1 to A4.

  For example, as shown in case A1, when the restriction flag 128 indicates “ON” and the user information includes the user ID “Bob” and the password “P1”, the CPU 122 performs S10 in FIG. YES is determined, and YES is determined in S20. Then, since the password “P1” in the user information matches the password “P1” in the restriction table 132, the CPU determines YES in S22, and the print permission information associated with the user ID “Bob” is “ “OK” is indicated, and YES is determined in S30. As a result, at T180, the CPU causes the print engine 106 to execute the print function according to the print data in the print job (S32).

  For example, as shown in case A2, when the restriction flag 128 indicates “ON” and the user information includes the user ID “Bob” and the password “P3”, the CPU uses the password in the user information. Since “P3” does not match the password “P1” in the restriction table 132, NO is determined in S22. As a result, at T182, the CPU supplies an authentication error notification to the print mediation server 10 (S40). In T184, the server 10 supplies an authentication error notification to the terminal device 20.

  For example, as shown in case A3, when the restriction flag 128 indicates “ON” and the user information does not include the user ID, the CPU determines NO in S20, and further determines the user ID “Public. The print permission information (S26) associated with "" indicates "NG", so it is determined NO in S30. As a result, in T186, the CPU supplies a print prohibition notice to the print mediation server 10 (S34). In T188, the server 10 supplies a print prohibition notice to the terminal device 20.

  Further, for example, as shown in case A4, when the restriction flag 128 indicates “OFF”, the CPU determines NO in S10, skips the processing of S20 to S30, and in T190 In accordance with the print data, the print engine 106 is caused to execute the print function. That is, in case A4, the CPU does not determine whether or not to allow the user to use the printing function even when user information (ie, user ID and password) is input to the authentication area AR1 of the input screen SC1. The print engine 106 is caused to execute a print function. As described above, the MFP 100 appropriately switches whether to use the print function (Case A1 to A3) or not (Case A4) according to the content of the restriction flag 128 set by the administrator. be able to.

(Effect of this embodiment)
In the present embodiment, when user information is input to the operation unit 102 (T10 in FIG. 2), the MFP 100 uses the restriction table 132 to execute the use restriction of the print function (cases N1 and N2). Further, when the MFP 100 acquires an execution instruction from the terminal device 30 including the driver program 34 via the LAN 4 (T22), the MFP 100 uses the restriction table 132 to execute the use restriction of the printing function (cases N3 and N4). ). Then, when printing is instructed from the server 10, the MFP 100 can use the restriction table 132 as it is and execute restriction on use of the printing function (see FIG. 5). That is, the MFP 100 registers related information including the authentication area information AI1 in the server 10 (T144, T146). Thereby, when the terminal device 20 logs in to the server 10, the input screen SC1 including the authentication area AR1 for inputting user information is displayed on the terminal device 20 (T156). The user information including the print function execution instruction (that is, selection of the OK button) can be input to the input screen SC1 (T160). In this case, since the MFP 100 acquires a print job including user information from the server 10 (T170), the use of the print function can be appropriately limited based on the user information and the print permission information (Case A1). -Case A3).

(Correspondence)
The MFP 100, the terminal device 30, and the print mediation server 10 are examples of “function execution device”, “information processing device”, and “server”, respectively. The print function, the print engine 106, and the memory 124 are examples of “specific function”, “function execution engine”, and “storage unit”, respectively. The print permission information and the restriction flag 128 are examples of “allowance information” and “first setting information”, respectively. The related information of T144 is an example of “first related information”. Authentication area AR1, condition area, input screen SC1, and authentication area information AI1 are examples of “first area”, “second area”, “first input screen”, and “first display information”, respectively. It is. The print job of T170 is an example of “first execution information”.

(Second embodiment)
In the present embodiment, the MFP 100 registers different related information in the print mediation server 10 depending on whether the restriction flag 128 is “ON” or “OFF”. When the restriction flag 128 is “ON” when logging in to the server 10, the MFP 100 registers the relevant information of the first embodiment (that is, the relevant information of T144 in FIG. 5) in the server 10, and the restriction flag 128 is set. If “OFF”, related information not including the authentication area information AI1 is registered in the server 10. When the restriction flag 128 is changed after logging in to the server 10, the MFP 100 registers new related information in the server 10 according to the changed setting.

(Specific case: Fig. 6)
A specific case realized by this embodiment will be described with reference to FIG. A specific case realized in a situation where the restriction flag 128 is “ON” is the same as T140 to T170 and cases A1 to A3 of FIG. 5 of the first embodiment.

  In the initial state of FIG. 6, the MFP 100 stores a restriction flag 128 indicating “ON”. The CPU 122 logs in to the print mediation server 10 using the account ID “Ken@example.com”. That is, in the server 10, related information including the authentication area information AI1 is registered in association with the account ID “Ken@example.com” (T144 and T146 in FIG. 5).

  In T242, the CPU changes the restriction flag 128 from “ON” to “OFF” in response to the operation of the operation unit 102 by the administrator. In this case, at T244, the CPU supplies new related information including the same capability information as in the first embodiment and does not include the authentication area information AI1 to the server 10. Thereby, in T246, the server 10 registers new related information that does not include the authentication area information AI1 instead of the related information that includes the authentication area information AI1 in association with the account ID “Ken@example.com”.

  When the terminal device 20 logs in at T250, the server 10 generates screen data representing an input screen that does not include the authentication area using the new related information at T252, and at T254, the screen data is transmitted to the terminal device. 20 is supplied. As a result, at T256, the terminal device 20 displays the input screen SC2 using the screen data. The input screen SC2 includes a condition area, an OK button, and a cancel button, but does not include an authentication area. Since the input screen SC2 does not include an authentication area, the user does not input user information. T260 to T280 are the same as T160 to T180 in FIG. However, since the input screen SC2 does not include an authentication area, the job ticket of T262 and the print job of T270 do not include user information. The CPU executes the job acquisition processing shown in FIG. 4 in response to acquiring the print job at T270. As a result, at T280, since the restriction flag 128 indicates “OFF”, the CPU determines NO in S10 of FIG. 4 and causes the print engine 106 to execute the print function according to the print data included in the print job.

(Effect of this embodiment)
When the restriction flag 128 indicates “OFF”, the MFP 100 determines NO in S <b> 10 of FIG. 4 and does not use the restriction table 132. That is, since the MFP 100 executes the print function regardless of the user who obtains the instruction (T32), there is no need to obtain user information. For this reason, in this embodiment, when the restriction flag 128 is changed from “ON” to “OFF”, the MFP 100 replaces the related information including the authentication area information with a new one not including the authentication area information. The related information is registered in the server 10 (T244 and T246 in FIG. 6). As a result, when the terminal device 20 logs in to the print mediation server 10, the input screen SC2 that does not include the authentication area is displayed on the terminal device 20 (T256), so the user does not input user information on the input screen SC2. It will end. User convenience can be improved. In the present embodiment, the related information of T244 and the print jobs of the input screens SC2 and T270 are examples of “second related information”, “second input screen”, and “second execution information”, respectively. is there.

(Third embodiment)
In the present embodiment, the content of the related information registered in the print mediation server 10 from the MFP 100 is different from that in the first embodiment. Specifically, the related information includes each user ID included in each individual information included in the restriction table 132.

(Specific case: Fig. 5)
Differences from the first embodiment will be described with reference to FIG. In this embodiment, the authentication area information AI1 in the related information of T144 includes a list of user IDs included in each individual information in the restriction table 132. At T152, the server 10 generates screen data representing the input screen SC3 by using the related information registered at T144. Input screen SC3 includes an authentication area AR2. Authentication area AR2 includes a box for selecting each user ID included in the list. Thereby, the user of the terminal device 20 should just select one user ID displayed on a box, without inputting the character string which shows user ID directly. For this reason, user convenience can be improved.

  In this embodiment, when the MFP 100 is logged in to the server 10 and the combination information in the restriction table 132 is changed (that is, the individual information is added or deleted), the CPU 122 New related information including a list of IDs is registered in the server 10. After the new related information is registered in the server 10, when the terminal device 20 logs into the server 10, the terminal device 20 displays the authentication area AR2 corresponding to the changed list. That is, the authentication area AR2 corresponding to the related information registered before the combination information is changed is different from the authentication area AR2 corresponding to the new related information registered after the combination information is changed. Therefore, the user can select a user ID from the latest list. In the present embodiment, the case where the combination information is changed is an example of “when a predetermined condition is satisfied”.

(Fourth embodiment)
In this embodiment, the combination information in the restriction table 132 further includes sheet number information indicating the remaining number of prints allowed for the user (see FIG. 1). For combination information including print permission information “OK”, it is permitted to set a value larger than “0” as the number information. On the other hand, for combination information including print permission information “NG”, it is prohibited to set a value larger than “0” as the number information.

(Job acquisition processing in the fourth embodiment; FIG. 4)
In this embodiment, in S24 of FIG. 4, the CPU 122 acquires the number information associated with the user ID and password used in S20 and S22 from the restriction table 132 in addition to the print permission information, and the process proceeds to S30. Proceed to In S26, the CPU 122 acquires the number information corresponding to the general information from the restriction table 132 in addition to the print permission information, and proceeds to S30.

  In S30, if the acquired print permission information indicates “NG”, the CPU determines that the user is not permitted to execute the print function (NO in S30). The CPU executes the print function when the acquired print permission information indicates “OK” but the remaining number of prints indicated by the acquired number information is less than the number of prints according to the print job. Is determined not to be allowed by the user (NO in S30).

  On the other hand, when the acquired print permission information indicates “OK” and the remaining print number indicated by the acquired number information is equal to or greater than the print number according to the print job, the CPU It is determined that the user is allowed to execute (YES in S30). In this case, the CPU causes the print engine 106 to execute the print function in S32, and further updates the limit table 132 by subtracting the number of prints according to the print data from the remaining number of prints in the limit table 132. .

  In the cases N1 and N3 in FIG. 2 as well, the CPU performs printing when the remaining number of prints indicated by the number information associated with the input user information is less than the number of prints to be executed. The function is not executed by the print engine 106. On the other hand, when the remaining number of prints indicated by the number information associated with the input user information is greater than or equal to the number of prints to be executed, the CPU causes the print engine 106 to execute a print function and The table 132 is updated.

  According to the present embodiment, the MFP 100 realizes not only a simple use restriction according to the print permission information (that is, “OK” or “NG”) but also a detailed use restriction using the remaining number of prints allowed by the user. can do. In this embodiment, the print permission information and the number information are examples of “allowance information”.

(5th Example)
In this embodiment, the MFP 100 further stores an account flag 130 (see FIG. 1). The account flag 130 is “ON”, which means that a determination based on the account ID (ie, login ID) used when the terminal device 20 logs into the server 10 is executed, and that the determination based on the account ID is not executed. It means either “OFF” meaning. The account flag 130 is set to “ON” or “OFF” by the administrator of the MFP 100.

  In the restriction table 132, individual information including an account ID can be registered in addition to individual information including a user ID. In the example of FIG. 1, individual information including the account ID “Ken@example.com” and individual information including the account ID “Alice@example.com” are registered. In this embodiment, no password is registered in association with the account ID.

(Process at the time of job acquisition of the fifth embodiment; FIG. 7)
In this embodiment, the job acquisition time processing of FIG. 7 is executed instead of FIG. S110 is the same as S10 of FIG. 4. If YES in S110, the process proceeds to S112. If NO in S110, the process proceeds to S132. In S112, the CPU 122 determines whether or not the account flag 130 in the memory 124 indicates “ON”. When the flag 130 indicates “ON” (YES in S112), the CPU proceeds to S220, and when the flag 130 indicates “OFF” (NO in S112), the CPU proceeds to S120. S120 to S126 are the same as S20 to S26 of FIG. If NO in S122, the process proceeds to S140, and if S124 or S126 is executed, the process proceeds to S130. S140 is the same as S40 of FIG.

  S220 is the same as S20 of FIG. If YES in S220, the process proceeds to S222. If NO in S220, the process proceeds to S226. S222 and S224 are the same as S22 and S24 of FIG. If NO in S222, the process proceeds to S140, and if S224 is executed, the process proceeds to S130. In S226, the CPU acquires print permission information associated with the account ID (ie, login ID) in the print job from the restriction table 132 in the memory 124, and the process proceeds to S130. In the present embodiment, since the password is not registered in association with the account ID in the restriction table 132, the determination based on the password is not executed. S130 to S134 are the same as 30 to S34 in FIG.

(Specific case; Fig. 8)
Next, a specific case realized by the present embodiment will be described with reference to FIG. A specific case realized in a situation where the account flag 130 is “OFF” is the same as T140 to T170 and cases A1 to A4 in FIG. 5 of the first embodiment.

  In the initial state of FIG. 8, the MFP 100 stores a restriction flag 128 indicating “ON” and an account flag 130 indicating “OFF”. The CPU 122 logs in to the print mediation server 10 using the account ID “Ken@example.com”. Accordingly, related information including the authentication area information AI1 associated with the account ID “Ken@example.com” has been registered in the server 10 (T144 and T146 in FIG. 5). Thereafter, in T342, the CPU changes the account flag 130 from “OFF” to “ON” in response to the operation of the operation unit 102 by the administrator.

  In T350, the terminal device 20 logs in to the server 10 using the account ID “Alice @ example.com” in accordance with a user operation. In the server 10, the ID is associated with the account ID “Ken@example.com”, and related information is registered in association with the account ID “Ken@example.com” (see T146 in FIG. 5). . Accordingly, the server 10 generates screen data representing the input screen SC1 using the registered related information at T352, and supplies the screen data to the terminal device 20 at T354.

  In T356, the terminal device 20 displays the input screen SC1 using the screen data. Although the input screen SC1 includes the authentication area AR1, in this case, the user does not input the user ID and password in the authentication area information AI1. That is, at T360, the terminal device 20 accepts the print condition input operation and the OK button selection without accepting the user information input operation. In this case, at T362, the terminal device 20 supplies the print mediation server 10 with a job ticket including condition information, a login ID, and user information that is empty data, along with a file to be printed. T364 to T368 are the same as T164 to T168 in FIG. In T370, a print job including print data, a login ID, and user information that is empty data is communicated. When acquiring a print job at T370, the CPU executes the job acquisition processing shown in FIG.

  In this case, the user information included in the T370 print job does not include the user ID. As a result, the CPU determines whether to allow the user to execute the printing function based on the login ID in the print job and the print permission information (YES in S112 in FIG. 7, NO in S220). . Specifically, the CPU acquires print permission information “OK” associated with the login ID “Alice@example.com” in the print job (S226), and determines that the user is allowed to use the print function. (YES in S130). As a result, in T380, the CPU causes the print engine 106 to execute the print function according to the print data in the print job.

(Effect of this embodiment)
The administrator of the MFP 100 has already registered the account ID “Alice@example.com” for other individual users in the server 10 in association with the account ID “Ken@example.com” for the MFP 100 (FIG. 1). reference). In this embodiment, the MFP 100 can realize not only the use restriction of the print function based on the user information including the user ID and the password but also the use restriction of the print function based on the account ID (that is, the login ID). Therefore, if the administrator registers the individual information including the account ID for the individual user in the restriction table 132 without registering the individual information including the user ID and the password in the restriction table 132, the administrator uses the information for the individual user. Limits can be set. Administrator convenience can be improved.

  Further, since the individual information including the account ID does not include the password, the MFP 100 does not perform password authentication (S222 is not performed when NO in S220 of FIG. 7). However, when the terminal device 20 logs in to the server 10 using the account ID “Alice@example.com” (T350 in FIG. 8), the server 10 normally performs authentication of the password corresponding to the account ID. Has been. Therefore, when MFP 100 acquires a print job including a login ID from server 10, password authentication for the login ID has already been executed by server 10, and as a result, MFP 100 does not execute further password authentication. . For this reason, the processing load on the MFP 100 can be reduced. Further, since the user does not need to input the user ID and password to the terminal device 20, the convenience for the user can be improved. In this embodiment, the account ID “Alice@example.com” is an example of “specific account ID”. A print job of T370 is an example of “third execution information”.

(Sixth embodiment)
In this embodiment, in the restriction table 132, passwords (see “P4” and “P5” in FIG. 1) are further registered in the individual information including the account ID. Further, the MFP 100 registers different related information in the print mediation server 10 depending on whether the account flag 130 is “ON” or “OFF”. The related information registered when the account flag 130 indicates “OFF” is the same as in the first and fifth embodiments (see T144 in FIG. 5). On the other hand, the related information registered when the account flag 130 indicates “ON” does not include a box for inputting a user ID and includes an input screen including an authentication area including a box for inputting a password. 20 is information to be displayed on the screen. In this embodiment, even when the account flag 130 indicates “ON”, the MFP 100 can execute password authentication.

(Job acquisition processing in the sixth embodiment; FIG. 9)
FIG. 9 shows a flowchart of the job acquisition time processing of this embodiment. Differences from the job acquisition processing (see FIG. 7) of the fifth embodiment will be mainly described. When the account flag 130 indicates “ON” (YES in S112), the CPU 122 acquires the password associated with the login ID in the print job from the restriction table 132 in the memory 124 in S322, and print job It is determined whether or not the password in the password matches the acquired password. If the two passwords match (YES in S322), the CPU proceeds to S226, and if the two passwords do not match (NO in S322), the CPU proceeds to S140. Other processes are the same as those in FIG.

(Specific case; Fig. 10)
With reference to FIG. 10, the specific case implement | achieved by a present Example is shown. Specific cases realized when the account flag 130 is “OFF” are the same as T140 to T170 and cases A1 to A4 in FIG. 5 of the first embodiment.

  The initial state of FIG. 10 is the same as the initial state of FIG. T442 is the same as T342 in FIG. In T444, the CPU 122 supplies related information including the authentication area information AI2 to the server 10 in response to the account flag 130 being changed from “OFF” to “ON”. Accordingly, at T446, the server 10 registers new related information including the authentication area information AI2 in the server 10 instead of the related information including the authentication area information AI1. The authentication area information AI2 is information for causing the terminal device 20 to display an authentication area that does not include a box for inputting a user ID and includes a box for inputting a password. When the terminal device 20 logs in at T450, the server 10 generates screen data representing the input screen SC4 including the authentication area AR3 using the new related information registered at T446 at T452, and generates the data at T454. The completed screen data is supplied to the terminal device 20.

  In T456, the terminal device 20 displays the input screen SC4 using the screen data. The authentication area AR3 in the input screen SC4 does not include a box for inputting a user ID and includes a box for inputting a password. That is, at T460, the terminal device 20 accepts the print condition input operation, the password input operation, and the OK button selection without accepting the user ID input operation. In this case, in T462, the terminal device 20 supplies the print mediation server 10 with a job ticket including condition information, a login ID, and a password together with a file to be printed. T464 to T468 are the same as T164 to T168 in FIG. In T470, a print job including print data, a login ID, and a password is communicated. When acquiring a print job at T470, the CPU executes the job acquisition processing shown in FIG.

  In this case, the account flag is “ON” (T442). Therefore, the CPU determines whether to allow the user to execute the printing function based on the login ID in the print job, the password in the print job, and the print permission information (FIG. 7). YES in S112, S322, S226, S130).

  For example, as shown in case B1, when the print job includes the password “P5”, the CPU uses the password “P5” in the print job and the login ID “Alice@example.com” in the print job. It is determined that the associated password “P5” matches (YES in S322). Then, since the print permission information associated with the login ID indicates “OK” (YES in S226 and S130), the CPU causes the print engine 106 to execute the print function according to the print data in the print job at T480. .

  For example, as shown in case B2, when the print job includes the password “P6”, the password “P6” in the print job and the password “P5” associated with the login ID in the print job. Are not matched (NO in S322). As a result, in T482, the CPU supplies an authentication error notification to the print mediation server 10 (S140). In T484, the server 10 supplies an authentication error notification to the terminal device 20.

(Effect of this embodiment)
In this embodiment, the administrator does not register the individual information including the user ID and password for the individual user in the restriction table 132, but the individual information including the account ID and password for the individual user is stored in the restriction table 132. If it is registered, the use restriction for the individual user can be set. Administrator convenience can be improved. In this embodiment, since not only the account ID but also the password is registered in the restriction table 132, the MFP 100 can also execute password authentication. Therefore, the MFP 100 can execute the print function more securely.

  Further, the authentication area AR3 in the input screen SC4 does not include a box for inputting a user ID. For this reason, it is not necessary for the user to input the user ID, so that convenience for the user can be improved. In the present embodiment, the account flag 130 is an example of “second setting information”. The related information of T444 is an example of “third related information”. The input screen SC4 and the authentication area information AI3 are examples of “third input screen” and “second display information”, respectively. The print job at T470 is an example of “third execution information”. The case where the CPU changes the account flag 130 from “OFF” to “ON” at T442 is an example of “when a predetermined condition is satisfied”.

  Specific examples of the present invention have been described in detail above, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. For example, the following modifications are included.

(Modification 1) In the above embodiment, the communication system 2 includes the print mediation server 10. Instead of this, the communication system 2 may include a scan mediation server. The scan mediation server is a server for mediating communication for causing the communication device (for example, the terminal device 20) to cause the MFP 100 to execute the scan function. The CPU 122 acquires a scan job from the scan mediation server, and determines whether to allow the user to execute the scan function based on the user information in the scan job and the scan permission information in the restriction table 132. May be. In this modification, the scan mediation server, the scan function, the scan engine 108, the scan job, and the scan permission information are “server”, “specific function”, “function execution engine”, “first execution information”, “ It is an example of “allowable information”. In another modification, use restriction of the FAX function may be executed. In this case, the communication system 2 may include a FAX mediation server for mediating communication that causes the communication device to cause the MFP 100 to execute the FAX function.

(Modification 2) The authentication areas AR1 and AR2 in FIG. 5 and the like include only a box for inputting a user ID, and may not include a box for inputting a password. In this case, processes such as S22 in FIG. 4 and S122 and S222 in FIG. 7 may be omitted. In this modification, the user ID is an example of “user information”.

(Modification 3) The restriction table 132 may not be stored in the memory 124 of the MFP 100. For example, it may be stored in a memory in a server connected to the LAN 4 to which the MFP 100 belongs, or a memory in a server on the Internet. That is, the “storage unit” may be provided inside the “function execution device” as in each of the above embodiments, or may be provided outside the “function execution device” as in the present modification. It may be.

(Modification 4) The MFP 100 does not include the restriction flag 128 and does not need to execute the process of S10 of FIG. That is, the “function execution device” may not use the “first setting information”.

(Modification 5) Related information such as T44 in FIG. 3 and T144 in FIG. 5 may not include capability information. The authentication area information and the capability information may be registered in the server 10 at different timings, or the capability information may not be registered. In this case, the input screen SC may not include the condition area. That is, the “function execution device” may not use the “capability information”.

(Modification 6) The related information of T444 in FIG. 6 may not include the authentication area information AI2. In this case, the MFP 100 may not execute the process of S322 in FIG. That is, the “function execution device” may not use the “third related information”.

(Modification 7) As another embodiment, an embodiment in which each of the first to sixth embodiments is combined can be implemented. For example, each of the second embodiment and the fourth to sixth embodiments may be combined with the third embodiment. In this case, the MFP 100 may use the input screen SC3 of FIG. 5 instead of the input screen SC1 used in the second embodiment and the fourth to sixth embodiments. Further, the fifth embodiment and the fourth embodiment may be combined. In this case, the MFP 100 may execute the process in the fourth embodiment of S40 in FIG. 4 instead of the process in S130 of FIG. Further, the sixth embodiment and the fourth embodiment may be combined. In this case, the MFP 100 may execute the process in the fourth embodiment of S40 in FIG. 4 instead of the process in S130 of FIG.

(Modification 8) The “function execution device” is not limited to the MFP 100, and a device (for example, a printer, a scanner, or the like) having a function execution engine for executing a specific function (for example, a scan function, a print function, a FAX function, etc.) , FAX machine, etc.).

  The technical elements described in this specification or the drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology illustrated in the present specification or the drawings achieves a plurality of objects at the same time, and has technical utility by achieving one of the objects.

2: Communication system, 6: Internet, 10: Print mediation server, 20, 30: Terminal device, 34: Driver program, 100: MFP, 102: Operation unit, 104: Display unit, 106: Print engine, 108: Scan engine , 120: control unit, 122: CPU, 124: memory, program: 126, 128: restriction flag, 130: account flag, 132: restriction table

Claims (11)

A function execution device,
A function execution engine for executing a specific function;
An operation unit;
When the operation unit accepts an input operation for inputting the first user information from the first user, the first user information and the permissible information stored in the storage unit are one or more. It is determined whether to allow the first user to execute the specific function based on the permission information indicating whether the user is permitted to execute the specific function for each of the users. A first determination unit;
When it is determined that the first user is allowed to execute the specific function, the function execution engine is caused to execute the specific function, and it is determined that the first user is not allowed to execute the specific function. A function control unit that prevents the function execution engine from executing the specific function;
A registration unit that registers, in a server, first related information related to the function execution device via the Internet, wherein the first related information includes a first area for inputting user information. Including the first display information for causing the terminal device to display one input screen;
After the terminal device logs into the server and displays the first input screen, second user information and an instruction to execute the specific function are displayed on the first input screen by a second user of the terminal device. An acquisition unit that acquires first execution information including the second user information from the server via the Internet;
When the first execution information is acquired, the specific function is based on the second user information included in the first execution information and the permissible information stored in the storage unit. A second determination unit that determines whether or not the second user is allowed to execute
When it is determined that the second user is allowed to execute the specific function, the function control unit causes the function execution engine to execute the specific function and execute the specific function. A function execution device that does not cause the function execution engine to execute the specific function when it is determined that the user does not allow.   The first determination unit further obtains the first user information and an execution instruction for the specific function from an information processing apparatus including a driver program for causing the function execution apparatus to execute the specific function. And determining whether to allow the first user to execute the specific function based on the first user information and the permission information stored in the storage unit. Item 4. The function execution device according to Item 1. The first related information is further capability information indicating the capability of the function execution engine, and the first input screen including a second area for inputting a function execution condition is displayed on the terminal device. Including the ability information to
The acquisition unit is configured to execute the second user information, a specific function execution condition, and the specific function by the second user after the terminal device logs into the server and displays the first input screen. When the instruction is input to the first input screen, the server includes the second user information and the condition information indicating the specific function execution condition from the server via the Internet. 1 execution information,
When it is determined that the second user is allowed to execute the specific function, the function control unit executes the specific function in the function execution engine according to the specific function execution condition indicated by the condition information. The function execution device according to claim 1, wherein: The registration unit further registers new first related information in the server instead of the first related information via the Internet when a predetermined condition is satisfied,
The new first related information includes new first display information for causing the terminal device to display a new first input screen including a new first area for inputting user information. ,
4. The method according to claim 1, wherein the first area included in the first input screen is different from the new first area included in the new first input screen. 5. The function execution device described. The function execution device further includes:
A memory for storing first setting information indicating whether to use the permission information;
The first determination unit includes:
When the operation unit accepts the input operation, it is determined whether or not the first user is allowed to execute the specific function when the first setting information indicates that the permission information is used. And
In the case where the operation unit accepts the input operation, it is determined whether or not the first user is allowed to execute the specific function when the first setting information indicates that the permission information is not used. Without
The second determination unit includes:
Whether or not to allow the second user to execute the specific function when the first setting information is acquired and the first setting information indicates that the permission information is used. Judgment
Whether or not to allow the second user to execute the specific function when the first execution information is acquired and the first setting information indicates that the permission information is not used. Without judging
The function control unit further includes:
When the operation unit accepts the input operation, when the first setting information indicates that the permission information is not used, the function execution engine executes the specific function,
5. When the first execution information is acquired, the function execution engine is caused to execute the specific function when the first setting information indicates that the permission information is not used. The function execution apparatus as described in any one of Claims. The function execution device further includes:
A memory for storing first setting information indicating whether to use the permission information;
The first determination unit includes:
When the operation unit accepts the input operation, it is determined whether or not the first user is allowed to execute the specific function when the first setting information indicates that the permission information is used. And
In the case where the operation unit accepts the input operation, it is determined whether or not the first user is allowed to execute the specific function when the first setting information indicates that the permission information is not used. Without
The registration unit further includes, via the Internet, when the first setting information is changed from a state indicating that the permission information is used to a state indicating that the permission information is not used. In place of the first related information, second related information related to the function execution device is registered in the server,
The second related information is a second input screen that does not include an area for inputting user information, and the second input screen for inputting an execution instruction for the specific function is displayed on the terminal device. Information to display,
The acquisition unit further inputs an instruction to execute the specific function to the second input screen by the second user after the terminal device logs in to the server and displays the second input screen. The second execution information not including user information is acquired from the server via the Internet,
The function control unit further includes:
When the operation unit accepts the input operation, when the first setting information indicates that the permission information is not used, the function execution engine executes the specific function,
5. The method according to claim 1, wherein when the second execution information is acquired, the function execution engine is caused to execute the specific function without executing a determination based on the permission information. 6. Function execution device. The acquisition unit further includes a specific account ID registered in the server by the second user from the terminal device via the Internet after the terminal device logs in to the server, Obtaining third execution information including the specific account ID used by the terminal device to log in to the server;
The function execution device further includes:
When the third execution information is acquired, based on the specific account ID included in the third execution information and the permission information stored in the storage unit, the specific function A third determination unit that determines whether or not the second user is allowed to execute the operation;
The function control unit further includes:
When it is determined that the second user is allowed to execute the specific function when the third execution information is acquired, the function execution engine is caused to execute the specific function,
7. The function execution device according to claim 1, wherein when it is determined that the second user does not allow execution of the specific function, the function execution engine is not allowed to execute the specific function.   After the terminal device logs in the server and displays the first input screen, the acquisition unit does not input user information to the first input screen by the second user, and thus the specific function When the execution instruction is input to the first input screen, the third execution information including the specific account ID and not including the user information is acquired from the server via the Internet. The function execution device according to claim 7. The function execution device further includes:
A memory for storing second setting information indicating whether or not to execute the determination based on the account ID;
The registration unit
When the second setting information indicates that the determination based on the account ID is not performed, the first related information including the first display information is registered in the server,
When the second setting information indicates that the determination based on the account ID is executed, the third related information related to the function execution device is registered in the server,
The first display information is information for causing the terminal device to display the first input screen including the first area for inputting user information including both a user ID and a password,
The third related information includes second display information for causing the terminal device to display a third input screen that does not include an area for inputting a user ID and includes an area for inputting a password. ,
After the terminal device logs into the server and displays the third input screen, the acquisition unit displays a specific password and an instruction to execute the specific function by the second user. The function execution device according to claim 7, wherein the third execution information including the specific account ID and the specific password is acquired from the server via the Internet. The first display information is information for causing the terminal device to display the first input screen including the first area for inputting user information including both a user ID and a password,
The second determination unit includes a specific user ID in the second user information included in the first execution information and a specific user ID in the second user information included in the first execution information. Based on the password and the permission information stored in the storage unit, determine whether to allow the second user to execute the specific function,
When the third execution information is acquired, the third determination unit does not perform a determination based on a password, and the specific account ID included in the third execution information and the storage unit The function execution device according to claim 7, wherein it is determined whether or not the second user is allowed to execute the specific function based on the permission information stored in the storage device. The permissible information includes sheet number information relating to the remaining number of prints permitted by the user,
The second determination unit includes:
Based on the second user information and the permissible information included in the first execution information, the remaining number of prints allowed for the second user is printed according to the first execution information. If the number is greater than or equal to the number of sheets, it is determined that the second user is allowed to execute the specific function,
Based on the second user information and the permissible information included in the first execution information, the remaining number of prints permitted for the second user is in accordance with the first execution information. 11. The function execution device according to claim 1, wherein when the number of printed sheets is less than the number of prints, the second function is determined not to allow the second user to execute the specific function.

Images