JP7196599B2 - Function-performing device and computer program for the function-performing device - Google Patents

Description

This specification relates to a function execution device capable of storing, in a memory, user identification information for identifying a user and relational information relating to whether or not execution of a function is permitted to the user in association with each other. Disclose technology.

Japanese Unexamined Patent Application Publication No. 2002-200010 discloses an MFP (abbreviation for Multi-Function Peripheral) that receives a print job from a server by logging into a server using an account ID. The MFP stores a restriction table, and in the restriction table, for each of one or more users, the user's account ID, print permission information indicating whether or not the user is permitted to execute the print function, are stored in association with each other. When the MFP receives a print job including an account ID from the server, it determines whether or not to execute the print function based on print permission information related to the account ID.

JP 2017-49718 A

In the above technique, for example, an administrator of the MFP operates the operation unit of the MFP to input the account ID and the print permission information into the MFP, thereby storing the account ID and the print permission information in the restriction table. .

This specification provides a technique for easily storing in memory account identification information and related information relating to whether or not a user is permitted to execute a function.

The function execution device disclosed in this specification includes a first function execution unit for executing a first function, and when specific user identification information for identifying a specific user is input, the specific and specific relationship information relating to whether or not the specific user is permitted to execute the first function are associated with each other and stored in a memory, The memory associates and stores, for each of one or more users, user identification information identifying the user and related information relating to whether or not the user is permitted to execute the first function. and when server usage information including first account identification information for a first user to use the server is registered in the server, the server a first information receiving unit that receives the first account identification information from the server; and the first account identification information as the user identification information when the first account identification information is received from the server , and first relationship information relating to whether or not the execution of the first function is permitted to the first user, in association with each other and stored in the memory; After the account identification information and the first relationship information are stored in the memory, an instruction to execute the first function including the first account identification information is received from the server, and in the memory the If the first relationship information stored in association with the first account identification information indicates that the first user is permitted to execute the first function, the first function is performed by the first user. and a first function control unit that causes one function execution unit to execute.

According to the above configuration, the function execution device receives the first account identification information from the server when the server usage information is registered in the server. In this case, the function execution device associates the first account identification information with the first relationship information and stores them in the memory. Therefore, the first account identification information and the first relationship information relating to whether or not the user is permitted to execute the first function can be easily stored in the memory.

A computer program for realizing the above-described function execution device and a computer-readable recording medium storing the computer program are also novel and useful. The methods performed by the above-described function-performing devices are also novel and useful.

1 shows the configuration of a communication system; FIG. 10 is a sequence diagram of processing for registering device information; FIG. 3 shows a sequence diagram continued from FIG. 2 ; FIG. 10 shows a sequence diagram of processing for registering a share user; 4 shows a flowchart of server print processing. 4 shows a flowchart of account print processing. 4 shows a flowchart of general print processing. A specific case realized by server print processing is shown. 4 shows a flowchart of table update processing. 4 shows a sequence diagram of deletion processing. FIG.

(Configuration of communication system 2; Fig. 1)
As shown in FIG. 1 , the communication system 2 includes a multi-function device 10 , an intermediary server 100 , and PCs (abbreviation for Personal Computer) 200 and 210 . Hereinafter, the multi-function device 10 may be referred to as "MFP (abbreviation for Multi-Function Peripheral) 10", and the mediation server 100 may simply be referred to as "server 100". The MFP 10 and PCs 200 and 210 are connected to LAN4. LAN 4 is connected to Internet 6 . Server 100 is connected to Internet 6 . Therefore, the MFP 10 and each of the PCs 200 and 210 can communicate with the server 100 via the Internet 6. FIG. Each of the PCs 200 and 210 is a stationary terminal device (for example, a desktop PC, etc.) in this embodiment, but in a modified example, a mobile phone (for example, a smart phone), a PDA, a notebook PC, a portable terminal such as a tablet PC. It may be a device.

(Configuration of MFP 10)
The MFP 10 is a peripheral device capable of executing multiple functions (for example, a peripheral device of the PC 200). The multiple functions include a print function and a scan function. The MFP 10 is assigned a model name MN indicating the model of the MFP 10, a device name DN for identifying the MFP 10, and a MAC address AD. The MFP 10 includes an operation section 12 , a display section 14 , a network interface 16 , a print execution section 18 , a scan execution section 20 and a control section 30 . Each unit 12 to 30 is connected to a bus line (reference numerals omitted). Below, an interface is described as "I/F."

The operation unit 12 has a plurality of keys. A user can input various instructions to the MFP 10 by operating the operation unit 12 . The display unit 14 is a display for displaying various information. Network I/F 16 is connected to LAN 4 . The print execution unit 18 includes a printing mechanism such as an inkjet method or a laser method. The scan execution unit 20 has a scan mechanism such as a CCD and a CIS.

The control unit 30 has a CPU 32 and a memory 34 . The CPU 32 executes various processes according to programs 36 stored in the memory 34 . The memory 34 is composed of a volatile memory, a nonvolatile memory, or the like. Memory 34 also stores a limit table 40 and limit flags 42 .

The restriction table 40 is a table that stores one or more pieces of combination information. The combination information includes user relationship information and restriction information. Combination information may include a password. User-related information consists of user identification information (for example, "John") that identifies individual users (that is, individual users), and general user information (for example, "Public") that indicates general users who are all users other than individual users. , is divided into The general user information is stored in advance in the restriction table 40 from the shipping stage of the MFP 10 . If the user-related information is general user information, the combination information does not contain the password. Note that in a modification, the user-related information may be divided into group identification information indicating a group (for example, a department within a company) to which one or more individual users belong, and general user information. In this case, the restriction table 40 may store combination information including group identification information and restriction information, and the combination information may not include passwords. Memory 34 may then store a user table in addition to limit table 40 . The user table may store, for each of a plurality of pieces of user identification information, associated user identification information and group identification information identifying a group to which the user identified by the user identification information belongs. The user table may further store a password in association with the user identification information, or may not store the password when the user identification information is an account name to be described later.

User identification information is stored in the restriction table 40 by the administrator of the MFP 10 . For example, when an administrator executes a login operation on PC 200 to access MFP 10, PC 200 displays an input screen for inputting user identification information and a password. When the user identification information "John" and the password "aaa" are entered on the input screen, the PC 200 transmits a storage instruction including the user identification information "John" and the password "aaa" to the MFP 10 (T2). When the MFP 10 receives the storage instruction from the PC 200 at T2, the MFP 10 newly stores each information included in the storage instruction (that is, the user identification information “John” and the password “aaa”) in the restriction table 40 . The MFP 10 also displays an input screen for inputting user identification information and a password when the administrator inputs authentication information for authenticating the administrator to the operation unit 12 of the MFP 10 and the administrator is successfully authenticated. may be displayed on the display unit 14 . Then, when the user identification information “John” and the password “aaa” are entered on the input screen, the MFP 10 may newly store the user identification information “John” and the password “aaa” in the restriction table 40 . Note that the password "aaa" may not be entered by the user, and may be generated by the PC 200 or MFP 10, for example.

The restriction information includes print execution information indicating whether or not the user is permitted to execute the print function, an allowable number of prints that the user is permitted to print during a predetermined period (for example, one month), and a predetermined and scan execution information indicating whether or not the user is permitted to execute the scan function. Each of the print execution information and the scan execution information indicates a value of either "OK" indicating that the user is allowed to execute the function or "NG" indicating that the user is not allowed to execute the function. . The print execution information, scan execution information, and allowable number of sheets are set by the administrator.

For example, after the user identification information "John" and the password "aaa" are stored in the restriction table 40, the MFP 10 receives a print instruction including the user identification information "John" and the password "aaa" from the PC 200 at T4. . In this case, the MFP 10 determines whether or not the restriction table 40 stores the combination of the user identification information “John” and the password “aaa” in the print instruction. When the MFP 10 determines that the combination is stored in the restriction table 40 , the MFP 10 identifies print execution information associated with the combination from the restriction table 40 . The MFP 10 executes printing according to the print instruction when the specified print execution information indicates "OK", and does not perform printing when the specified print execution information indicates "NG". That is, by using the restriction table 40, the MFP 10 can implement usage restriction of functions according to each user.

Also, the restriction table 40 can store an account name (for example, "Ken@server.com") for an individual user to use the server 100 as user identification information. As a result, even when a print instruction (that is, a job notification, which will be described later) is received from the server 100, it is possible to restrict the use of functions according to each user. Here, the account name is stored in the restriction table 40 when the account name is received from the server 100 . Processing for storing the account name in the restriction table 40 will be described later. Note that when the user identification information is an account name, the combination information does not contain the password.

The restriction flag 42 is set to "ON" to indicate that the restriction table 40 is used to restrict the use of functions according to each user, and to indicate that the restriction table 40 is not used (i.e., to restrict the use of functions according to each user). or "OFF" indicating that the The restriction flag 42 is set to “ON” or “OFF” by the administrator of the MFP 10 .

Memory 34 may also store access information 44 . The access information 44 is information for accessing the server 100 .

(Configuration of mediation server 100)
The server 100 is a server installed on the Internet, and is, for example, a GCP (abbreviation for Google Cloud Print) server provided by Google (registered trademark). However, in a modification, the server 100 may be a server provided by an operator other than Google, or may be a server provided by the vendor of the MFP 10, for example. The server 100 is a server for mediating printing between the MFP 10 and the PC 200 or the like. For example, the server 100 converts an image file received from the PC 200 to generate print data having a data format interpretable by the MFP 10 and transmits a print job including the print data to the MFP 10 . Therefore, the PC 200 or the like does not have to have a printer driver for converting an image file into print data. The user registers account information (for example, Google Account) for using the server 100 in advance in the memory 134 of the server 100 . Account information includes an account name and password. In this embodiment, the account information AI1 (that is, account name "Ken@server.com" and password "xxx") is account information registered by the administrator of the MFP10.

In addition, server 100 can register in memory 134 device information for each of one or more peripheral devices including MFP 10 so that the peripheral device uses server 100 . Processing for registering device information will be described later.

(Processing for registering device information; FIGS. 2 and 3)
A registration process for registering device information in the server 100 will be described with reference to FIGS. 2 and 3. FIG. In the following, for ease of understanding, when describing the processing executed by the CPU 32 of the MFP 10 according to the program 36, the CPU 32 will not be described mainly, but the MFP 10 will be mainly described. All communications performed by MFP 10 are performed via network I/F 16 . Therefore, below, description of "via network I/F16" is abbreviate|omitted.

At T10, PC 200 transmits a login request including account information AI1 to server 100 in response to input of account information AI1 and an instruction to log in to server 100 from the administrator of MFP 10 . Since the account information AI1 is registered in the server 100, the PC 200 is logged in to the server 100 using the account information AI1.

When server 100 receives a login request from PC 200 at T10, server 100 transmits search screen data to PC 200 at T12. The search screen data is screen data representing a search screen. The search screen includes a search button for searching for peripheral devices existing around the PC 200 .

Upon receiving the search screen data from server 100 at T12, PC 200 displays the search screen represented by the search screen data at T14. When the PC 200 receives an operation to select the search button in the search screen from the administrator at T16, the PC 200 broadcasts a search signal for searching for printers to the LAN 4 at T18.

Upon receiving the search signal from PC 200 at T18, MFP 10 transmits the device name DN to PC 200, which is the source of the search signal, at T20.

Upon receiving the device name DN from the MFP 10 at T20, the PC 200 displays a search result including the device name DN of the MFP 10 and the device names of peripheral devices other than the MFP 10 at T22. The PC 200 receives the selection of the device name DN from the administrator at T24, and transmits a registration instruction to the MFP 10 at T26. The registration instruction is a command for instructing MFP 10 to register with server 100 . The registration instruction includes account information AI1 currently logged in to server 100 .

Upon receiving the registration instruction from PC 200 at T26, MFP 10 executes a process for authenticating the administrator at T28. For example, the process includes a process of displaying an input screen for inputting authentication information for authenticating the administrator on the display unit 14, and a process of authenticating the authentication information input to the input screen. . When the authentication succeeds, the MFP 10 executes the processing after T30 described later, and when the authentication fails, the MFP 10 does not execute the processing after T30 and transmits a notification indicating that the authentication has failed to the PC 200. .

At T30, the MFP 10 transmits a registration request to the server 100. FIG. A registration request is a command requesting the server 100 to register device information. The registration request includes MAC address AD of MFP 10, model name MN of MFP 10, and function information FI. The function information FI includes a plurality of functions executable by the MFP 10 (ie, print function, scan function), user-selectable conditions (e.g., number of colors for printing, presence/absence of double-sided printing, number of colors for scanning, etc.). , indicates.

When server 100 receives the registration request from MFP 10 at T30, server 100 determines whether MAC address AD included in the registration request has already been registered with server 100 at T32. In this case, the server 100 determines that the MAC address AD has not yet been registered, and executes the processing from T34 onwards. Incidentally, if it is determined that the MAC address AD has already been registered, the processes after T72 are not executed, and the processes in FIGS. 2 and 3 are terminated.

At T34, the server 100 generates a management identifier MI and a registration token RT. The management identifier is an identifier assigned to MFP 10 by server 100 to manage MFP 10 . A registration token is a token used to register device information including an account name. The server 100 generates a unique management identifier MI and registration token RT so as not to duplicate management identifiers and registration tokens generated in the past. At T36, the server 100 stores the device information DI. The device information DI includes each information included in the registration request of T30 (ie MAC address AD, model name MN, function information FI), the generated management identifier MI, and the generated registration token RT. At T38, the server 100 transmits the management identifier MI and the registration token RT to the MFP10.

Upon receiving the management identifier MI and the registration token RT from the server 100 at T38, the MFP 10 transmits the registration token RT to the PC 200 at T100 in FIG. Further, after transmitting registration token RT to PC 200, MFP 10 periodically transmits to server 100 a registration confirmation signal (see T114 described later) for confirming whether device information registration has been completed.

When PC 200 receives registration token RT from MFP 10 at T100, PC 200 transmits a registration request including account information AI1 currently logged into server 100 and the received registration token RT to server 100 at T110. The registration request is a command requesting the server 100 to register device information including account information AI1.

Upon receiving the registration request from PC 200 at T110, server 100 determines at T112 whether or not the registration token RT included in the registration request matches the registration token RT stored at T36. In this case, the server 100 determines that these registration tokens match and updates the device information DI. Specifically, server 100 further stores account information AI1 included in the registration request in association with each piece of information stored in T36. As a result, the device information DI including the account information AI1 is registered in the server 100. FIG. The updated device information DI includes the account information AI1 included in the registration request and information "owner" indicating that the account information AI1 is the owner's account information. Since the registration token RT is not used in subsequent processing, the illustration of the registration token RT is omitted in the device information shown in T112. As will be described later in detail, the device information DI may further include shared user account information. A shared user means a user who is permitted by the owner to have the MFP 10 execute printing using the server 100 .

After updating device information DI at T112, server 100 receives a registration confirmation signal from MFP 10 at T114, and transmits a registration notification including account information AI1 to MFP 10 as a response to the registration confirmation signal at T120. A registration notification is a notification indicating that registration of device information has been completed.

When the MFP 10 receives the registration notification from the server 100 at T120, it transmits a token request to the server 100 at T130. A token request is a command requesting the server 100 to transmit an access token.

When the server 100 receives a token request from the MFP 10 at T130, it generates an access token AT, which is a unique character string, at T140. Furthermore, the server 100 further stores the generated access token AT in association with each piece of information updated in T112, and updates the device information DI. The server 100 then transmits the access token AT to the MFP 10 at T150.

Upon receiving the access token AT from the server 100 at T150, the MFP 10 transmits a connection request including the access token AT to the server 100 at T160. The connection request is a command requesting the server 100 to establish an XMPP (abbreviation for eXtensible Messaging and Presence Protocol) connection, which is a so-called constant connection.

When the server 100 receives the connection request from the MFP 10 at T160, the server 100 determines that the access token AT included in the connection request has been registered as the device information DI (see T140), and establishes the XMPP connection. When the XMPP connection is established in this way, the server 100 uses the XMPP connection to send a signal (for example, job T330 in FIG. notification) can be sent to the MFP 10 .

After receiving the access token AT from the server 100, the MFP 10 stores the access information 44 in the memory 34 at T172. The access information 44 includes account information AI1, management identifier MI, and access token AT. MFP 10 then transmits a storage completion notification to PC 200 at T180. The storage completion notification is a notification indicating that storage of the access information 44 has been completed.

Subsequently, at T190, the MFP 10 determines whether or not the limit flag 42 in the memory 34 indicates "ON". When the MFP 10 determines that the limit flag 42 indicates "ON" (YES in T190), it executes the process of T192, and when it determines that the limit flag 42 indicates "OFF" (NO in T190), The process of T192 is skipped and the processes of FIGS. 2 and 3 are terminated.

At T192, the MFP 10 stores the account name "Ken@server.com" in the account information AI1 in the restriction table 40 as user identification information. The MFP 10 further associates the account name "Ken@server.com" with the print execution information indicating "OK", the number of allowable sheets indicating "unlimited", the number of printed sheets indicating "0", and "OK". is stored in the limit table 40 . As described above, the account name “Ken@server.com” is the account name of the MFP 10 administrator. Normally, the administrator does not need to restrict the use of functions. Therefore, in this embodiment, the administrator is permitted to execute the print function and the scan function, and the allowable number of sheets is set to "unlimited".

Further, according to the above configuration, when the restriction flag 42 indicates "OFF" (NO in T190), the MFP 10 does not store the account name "Ken@server.com" in the restriction table 40 (that is, executes T192). do not). According to the configuration of this embodiment, it is possible to prevent the account name "Ken@server.com" from being unnecessarily stored in the limit table 40 even though the limit table 40 is not used.

Further, according to the above configuration, when the device information DI is registered in the server 100, the MFP 10 receives the account name "Ken@server.com" from the server 100 (T120 in FIG. 3), and the user identification information account name "Ken@server.com" and the restriction information are stored in the restriction table 40 (T192). Here, after the device information DI is registered in the server 100, the MFP 10 does not accept the operation of inputting the account name "Ken@server.com" to the operation unit 12 of the MFP 10, and furthermore, the account name " store the account name "Ken@server.com" and the restriction information in the restriction table 40 without receiving a storage instruction (see T2 in FIG. 1) containing "Ken@server.com". Therefore, after the device information DI is registered in the server 100, the user (that is, the administrator) registers the account name "Ken@server.com" and the restriction information in the restriction table 40 with the account name "Ken@server.com". Ken@server.com" to the operation unit 12 or to the PC 200 or the like. For this reason, the MFP 10 can simply store the account name “Ken@server.com” and the restriction information in the restriction table 40 .

(Processing for registering a share user; Fig. 4)
A process of registering a share user in the server 100 will be described with reference to FIG. FIG. 4 is a continuation of FIG. Therefore, the server 100 stores device information DI including MAC address AD, model name MN, function information FI, management identifier MI, account information AI1, and access token AT.

T200 is the same as T10 in FIG. At T202, PC 200 transmits a registration list request to server 100. FIG. The registration list request is a command for requesting a list including model names and management identifiers stored in association with account information AI1.

When the server 100 receives the registration list request from the PC 200 at T202, the server 100 transmits the registration list information to the PC 200 at T204. In this case, one piece of device information DI including account information AI1 is registered in the server 100 . Therefore, the registration list information includes the model name MN and management identifier MI.

Upon receiving the registration list information including the model name MN and the management identifier MI from the server 100 at T204, the PC 200 displays the registration list represented by the registration list information at T206. When PC 200 accepts selection of a combination of model name MN and management identifier MI in the registration list in T208, PC 200 displays a share screen in T210. The share screen is a screen for inputting the account name of the share user. When PC 200 receives the input of the share user's account name "Bob@server.com" at T212, at T214 PC 200 transmits a share request including the management identifier MI and the account name "Bob@server.com" to server 100. do. A share request is a command requesting addition of a share user's account name to the device information DI.

When the server 100 receives the share request from the PC 200 at T214, the server 100 stores in the memory 134 the share information (that is, the management identifier MI and the account name “Bob@server.com”) included in the share request. The share information is stored in server 100 until server 100 receives an OK notification, which will be described later, from PC 210 logging into server 100 using account information AI2 including the account name "Bob@server.com". .

Subsequently, at T230, PC 210 transmits a login request including account information AI2 to server 100 in response to receiving the input of account information AI2 and the instruction to login to server 100 from the share user. Since the account information AI2 is registered in the server 100, the PC 210 is logged in to the server 100 using the account information AI2.

When server 100 receives the login request from PC 200 at T230, server 100 transmits confirmation screen information representing a confirmation screen to PC 210 at T232. The confirmation screen is a screen for confirming with the share user whether or not to add the share user's account name "Bob@server.com" to the device information DI. The confirmation screen includes an OK button and a Cancel button.

Upon receiving the confirmation screen information from the server 100 at T232, the PC 210 displays the confirmation screen at T234. When the PC 210 accepts selection of the OK button in the confirmation screen in T236, it transmits an OK notification indicating that the OK button has been selected to the server 100 in T238. Note that if the Cancel button in the confirmation screen is selected, the PC 210 transmits an NG notification to the server 100 . Upon receiving the NG notification, the server 100 deletes the share information from the memory 134 and terminates the process of FIG. 4 without executing the process of T240, which will be described later.

Upon receiving the OK notification from PC 210 at T238, server 100 identifies share information including the account name "Bob@server.com" from memory 134 at T240. Then, the server 100 identifies the device information DI including the management identifier MI included in the identified share information from the memory 134, and adds the account name "Bob@server.com" to the identified device information DI. Further, the server 100 adds information "share" indicating that the account information AI2 is the account information of the share user to the device information DI. When the process of T240 ends, the process of FIG. 4 ends.

(Server print processing; Fig. 5)
Server print processing executed by the CPU 32 of the MFP 10 will be described with reference to FIG. Server print processing can be executed after an XMPP connection is established with the server 100 (T170 in FIG. 3) and the access information 44 is stored in the memory 34 (T172). The server print process is triggered by receiving a job notification from the server 100 using the XMPP connection. The job notification is information for notifying the MFP 10 that a print job has been generated. The job notification includes a management identifier, login account name, and owner account name. The login account name is the account name currently logged into the server 100 . The owner account name is the owner's account name included in the device information including the management identifier in the job notification. Also, if the job notification is received after the process of FIG. 4 is performed, the job notification further includes the share account name. The share account name is the share user account name included in the device information including the management identifier in the job notification. A login account name is either an owner account name or a share account name. Note that when the login account name is the owner account name, the job notification may not include the share account name.

In S10, CPU 32 transmits a job request for requesting a print job to server 100 as a response to the job notification. The CPU 32 then receives a print job from the server 100 as a response to the job request. The job request includes the management identifier included in the job notification and the access token AT included in the access information 44. FIG.

In S12, the CPU 32 determines whether or not the limit flag 42 in the memory 34 indicates "ON". When the CPU 32 determines that the limit flag 42 indicates "OFF" (NO in S12), the process proceeds to S80. In S<b>80 , the CPU 32 executes printing according to the print job without using the limit table 40 . Specifically, the MFP 10 supplies the print data in the print job to the print execution unit 18 and instructs the print execution unit 18 about the print settings in the print job. As a result, the print executing unit 18 executes printing according to the print settings of the image represented by the print data. When the process of S80 ends, the process of FIG. 5 ends.

Further, when the CPU 32 determines that the restriction flag 42 indicates "ON" (YES in S12), the process proceeds to S14. At S<b>14 , the CPU 32 determines whether or not the owner account name in the job notification is stored in the restriction table 40 . When the CPU 32 determines that the owner account name in the job notification is stored in the restriction table 40 (YES in S14), in S20, the CPU 32 executes account printing processing (see FIG. 6), which will be described later. Further, when the CPU 32 determines that the owner account name in the job notification is not stored in the restriction table 40 (NO in S14), in S50, the general printing process (see FIG. 7) described later is executed. When the process of S20 or S50 ends, the process of FIG. 5 ends.

According to the above configuration, when the owner account name in the job notification is not stored in the restriction table 40 (NO in S14), printing can be executed by the general printing process (S50). In other words, it is possible to prevent the occurrence of non-execution of printing even though the job notification has been sent to the MFP 10 .

Further, according to the above configuration, when the owner account name in the job notification is not stored in the restriction table 40 (NO in S14), the account printing process, which will be described later, is not executed. Not stored in limit table 40. That is, it is possible to prevent the share account name from being stored in the restriction table 40 when the owner account name is not stored in the restriction table 40 .

Further, according to the above configuration, when it is determined that the restriction flag 42 indicates "OFF" (NO in S12), the account printing process, which will be described later, is not executed, and the share account name is not stored in the restriction table 40. . That is, it is possible to prevent unnecessary storage of the share account name in the limit table 40 when the limit table 40 is not used.

(Account print processing; Fig. 6)
The account printing process will be described with reference to FIG. In S22, the CPU 32 determines whether or not the job notification includes the share account name. When determining that the job notification does not include the share account name (NO in S22), the CPU 32 skips the processes of S24 and S26 described later and proceeds to S28. On the other hand, when the CPU 32 determines that the job notification includes the share account name (YES in S22), the process proceeds to S24.

At S<b>24 , the CPU 32 determines whether or not the share account name in the job notification is stored in the restriction table 40 . When determining that the share account name in the job notification is stored in the restriction table 40 (YES in S24), the CPU 32 skips the processing of S26 described later and proceeds to S28. On the other hand, when the CPU 32 determines that the share account name in the job notification is not stored in the restriction table 40 (NO in S24), the process proceeds to S26.

In S26, the CPU 32 stores the share account name in the job notification in the restriction table 40 as user identification information. Then, the CPU 32 acquires restriction information associated with the owner account name in the job notification from the restriction table 40 . The CPU 32 associates the share account name with print execution information that is the same as the print execution information included in the already acquired limit information (for example, "OK") and the same allowable number of sheets as the allowable number of sheets that is included in the acquired limit information (for example, “Unlimited”) and the number of prints indicating “0” are stored in the limit table 40 . As a result, it is possible to impose the same restrictions on the use of the print function on the share users as on the owner.

Furthermore, the CPU 32 stores scan execution information indicating "NG" in the restriction table 40 in association with the share account name regardless of whether the scan execution information included in the obtained restriction information indicates "OK". do. As a result, the scan function can be used more restrictedly than the owner by the share user. Also, as described above, when a job notification is received from the server 100, the process of FIG. 6 is executed. Even if the job notification is received, it is unclear whether the server 100 can mediate scanning. In situations where it is unclear whether or not the server 100 can mediate scanning, unnecessary storage of scan execution information indicating “OK” in the restriction table 40 can be suppressed.

As described above, the server 100 is a server that performs printing mediation. Here, the registration of the share user with the server 100 means that the share user has been permitted by the owner to use the server 100 for printing. Therefore, when the job notification includes the share account name, the CPU 32 stores print execution information indicating "OK" in the restriction table 40 in association with the share account name (S26). In addition, if the server 100 is a server that mediates not only printing but also scanning, registration of a share user with the server 100 means that the share user can use the server 100 to perform scanning. It also means that the owner has given permission to do so. In this case, the CPU 32 stores scan execution information indicating "OK" in the restriction table 40 in association with the share account name in S26. That is, the CPU 32 may store, in the restriction table 40, function execution information related to services that become available when a share user is registered in the server 100, in association with the share account name.

In S28, the CPU 32 determines whether or not the print execution information associated with the login account name (that is, owner account name or share account name) in the restriction table 40 indicates "OK". When the CPU 32 determines that the print execution information associated with the login account name indicates "NG" (NO in S28), the CPU 32 transmits an error notification indicating that printing cannot be executed to the server 100 in S36. When S36 ends, the process of FIG. 6 ends.

When the CPU 32 determines that the print execution information associated with the login account name indicates "OK" (YES in S28), the process proceeds to S30. In S30, the CPU 32 adds the number of printed sheets according to the print job received in S10 of FIG. An expected number of sheets, which is the expected number of printed sheets after the printing, is calculated. Then, the CPU 32 determines whether or not the expected number of sheets is equal to or less than the allowable number of sheets associated with the login account name in the limit table 40 . When the expected number of sheets is larger than the allowable number of sheets (NO in S30), the CPU 32 proceeds to S36. On the other hand, when the expected number of sheets is equal to or less than the allowable number of sheets (YES in S30), the CPU 32 proceeds to S32. S32 is the same as S80 in FIG.

In S34, the CPU 32 adds the number of printed sheets printed in S32 to the number of printed sheets in the limit table 40 to calculate a new number of printed sheets. Then, the CPU 32 updates the number of printed sheets in the limit table 40 to the new number of printed sheets. When S34 ends, the process of FIG. 6 ends.

(General print processing; Fig. 7)
General print processing will be described with reference to FIG. In S52, the CPU 32 determines whether the print execution information associated with the general user information in the restriction table 40 indicates "OK". When the CPU 32 determines that the print execution information associated with the general user information indicates "NG" (NO in S52), the process proceeds to S66. S66 is the same as S36 in FIG. When S66 ends, the process of FIG. 7 ends.

If the CPU 32 determines that the print execution information associated with the general user information indicates "OK" (YES in S52), the process proceeds to S60. In S60, the CPU 32 adds the number of printed sheets according to the print job received in S10 of FIG. Then, the CPU 32 determines whether or not the expected number of sheets is equal to or less than the allowable number of sheets associated with the general user information in the limit table 40 . When the expected number of sheets is larger than the allowable number of sheets (NO in S60), the CPU 32 proceeds to S66. On the other hand, when the expected number of sheets is equal to or less than the allowable number of sheets (YES in S60), the CPU 32 proceeds to S62. S62 is the same as S80 in FIG.

In S64, the CPU 32 adds the number of printed sheets printed in S62 to the number of printed sheets in the limit table 40 to calculate a new number of printed sheets. Then, the CPU 32 updates the number of printed sheets in the limit table 40 to the new number of printed sheets. When S64 ends, the process of FIG. 7 ends.

(Specific case; Figure 8)
A specific case realized by the processing of FIGS. 5 to 7 will be described with reference to FIG. FIG. 8 is a continuation of FIG. Therefore, the server 100 stores device information DI including MAC address AD, model name MN, function information FI, management identifier MI, account information AI1, access token AT, and account information AI2. ing.

T300 is the same as T230 in FIG. At T302, the PC 210 transmits a selection screen request to the server 100. FIG. The selection screen request is a command for requesting selection screen information representing a selection screen for selecting a peripheral device to be printed from among a plurality of peripheral devices.

When the server 100 receives the selection screen request from the PC 210 at T302, at T304, the server 100 identifies one or more pieces of device information including the account information AI2 included in the login request of T300 from the memory 134 . Then, server 100 transmits to PC 210 selection screen information representing a selection screen including information (that is, model name and management identifier) included in the identified one or more pieces of device information. In this case, one piece of device information DI including account information AI2 is registered in the server 100 . Therefore, the selection screen includes the model name MN and management identifier MI.

Upon receiving the selection screen information from the server 100 at T304, the PC 210 displays the selection screen at T306. When the PC 210 accepts the selection of the combination of the model name MN and management identifier MI in the selection screen at T308, it transmits a setting screen request including the management identifier MI to the server 100 at T310. The setting screen request is a command for requesting setting screen information representing a setting screen for selecting print settings.

When server 100 receives the setting screen request from PC 210 at T310, server 100 identifies function information FI associated with management identifier MI included in the setting screen request from memory 134 at T320. The server 100 generates setting screen information representing a setting screen including a print condition selection button indicated by the specified function information FI. The server 100 then transmits the generated setting screen information to the PC 210 .

Upon receiving the setting screen information from the server 100 at T320, the PC 210 displays the setting screen at T322. The setting screen includes, for example, a monochrome button for selecting monochrome printing and a color button for selecting color printing. At T324, PC 210 accepts selection of the color button in the setting screen, and then accepts selection of image file IF representing an image to be printed. In T326, the PC 210 transmits the image file IF and the print setting "color" indicating color printing to the server 100. FIG.

The server 100 receives the image file IF and the print setting "color" from the PC 210 in T326, and converts the image file IF according to the print setting "color" to generate the print data PD in T328. Next, the server 100 stores in the memory 134 the print job PJ including the management identifier MI received at T310, the generated print data PD, and the print setting "color" received at T326. Then, in T330, the server 100 uses the XMPP connection to transfer the management identifier MI, the login account name "Bob@server.com", the owner account name "Ken@server.com", and the share account name "Bob @server.com” to the MFP 10.

Upon receiving the job notification from the server 100 at T330, the MFP 10 transmits to the server 100 a job request including the management identifier MI and the access token AT included in the access information 44. FIG. Then, the MFP 10 receives the print job PJ including the management identifier MI as a response to the job request from the server 100 (S10 in FIG. 5).

In this case, the restriction flag indicates "ON" when the process of FIG. 3 is executed. Therefore, the process of T192 is executed, and the restriction table 40 stores the owner account name "Ken@server.com". In addition, the restriction flag indicates "ON" even at this time. Therefore, the MFP 10 determines that the restriction flag indicates "ON" (YES in S12 of FIG. 5), determines that the owner account name is stored in the restriction table 40 (YES in S14), and performs account printing processing. (S20).

In this case, the share account name “Bob@server.com” is not stored in the restriction table 40. Therefore, the MFP 10 determines that the job notification includes the share account name (YES in S22 of FIG. 6), and determines that the share account name "Bob@server.com" is not stored in the restriction table 40 (S24). YES). As a result, the MFP 10 stores the share account name "Bob@server.com" and the restriction information in the restriction table 40 at T336 (S26). In this case, the MFP 10 sets the print execution information “OK” which is the same as the print execution information of the owner account name “Ken@server.com” and the allowable number of sheets “unlimited” which is the same as the allowable number of sheets of the owner account name “Ken@server.com”. , number of prints “0”, and scan execution information “NG” are stored in the limit table 40 .

Subsequently, the MFP 10 determines that the print execution information for the login account name "Bob@server.com" indicates "OK" (YES in S28), and determines that the predicted number of sheets is equal to or less than the allowable number of sheets "unlimited" ( YES in S30). As a result, the MFP 10 executes printing according to the print job PJ at T338 (S32). Then, the MFP 10 updates the number of printed sheets for the login account name "Bob@server.com" to the new number of printed sheets (S34).

According to this case, the MFP 10 receives the job notification including the share account name from the server 100 after the share user account information AI2 is added to the device information DI (T330). Then, when the share account name is received from server 100, MFP 10 stores the share account name in restriction table 40 (T336). Here, the MFP 10 does not accept an operation to input the share account name to the operation unit 12 of the MFP 10, and furthermore, without receiving a storage instruction (see T2 in FIG. 1) including the share account name from the PC 200 or the like, the share account name is entered. The account name is stored in the restriction table 40. Therefore, the share account name can be easily stored in the restriction table 40 .

Also, according to this case, the MFP 10 receives a job notification including the share account name from the server 100 (T330). For example, when a predetermined notification different from the job notification described above and including a share account name is received from the server 100, a comparative example is assumed in which the share account name is stored in the restriction table 40. . The predetermined notification is different from the job notification, and is, for example, a notification received from the server 100 when the user inputs a predetermined instruction to store the share account name in the restriction table 40 . In this comparative example, the user is required to perform a predetermined operation for inputting a predetermined instruction in addition to the operation of T324 that triggers the transmission of the job notification. On the other hand, in this case, the user can store the share account name in the restriction table 40 simply by executing the operation of T324, which is the trigger for sending the job notification. User convenience is improved.

(Table update processing; Fig. 9)
The table update process executed by the CPU 32 of the MFP 10 will be described with reference to FIG. The MFP 10 executes table update processing triggered by the arrival of a predetermined cycle after the power of the MFP 10 is turned on.

In S100, the CPU 32 determines whether or not the limit flag 42 in the memory 34 indicates "ON". If the CPU 32 determines that the limit flag 42 indicates "ON" (YES in S100), the CPU 32 proceeds to S102. The process is skipped and the process of FIG. 9 ends.

At S<b>102 , the CPU 32 determines whether or not the access information 44 is stored in the memory 34 . If the CPU 32 determines that the access information 44 is stored in the memory 34 (YES in S102), it proceeds to S104; if it determines that the access information 44 is not stored in the memory 34 (NO in S102) , skip the processing after S104, and terminate the processing of FIG.

At S<b>104 , the CPU 32 determines whether or not the account name in the access information 44 is stored in the restriction table 40 . When the CPU 32 determines that the account name in the access information 44 is stored in the restriction table 40 (YES in S104), the CPU 32 proceeds to S106, and the account name in the access information 44 is not stored in the restriction table 40. (NO in S104), skip the process of S106 and proceed to S108.

S106 is the same as T192 in FIG. 3 except that the account name in the access information 44 is stored in the restriction table 40. FIG.

Subsequently, in S108, the CPU 32 transmits to the server 100 a registration information request including the management identifier in the access information. A registration information request is a command for requesting the contents of device information registered in the server 100 . Upon receiving the registration information request from MFP 10, server 100 identifies device information including the management identifier included in the registration information request. Then, server 100 transmits registration information including the account name included in the identified device information to MFP 10 . Here, if the specified device information includes information indicating "owner" and information indicating "share", the registration information includes the owner account name and the share account name. If the identified device information does not include information indicating "share", the registration information includes only the owner account name.

At S110, the CPU 32 receives registration information from the server 100 as a response to the registration information request. In S112, the CPU 32 determines whether the registration information includes a share account name. If the CPU 32 determines that the share account name is included in the registration information (YES in S112), the CPU 32 proceeds to S114. , and the processing of FIG. 9 is terminated.

At S<b>114 , CPU 32 determines whether or not the share account name in the registration information is stored in restriction table 40 . If the CPU 32 determines that the share account name is stored in the restriction table 40 (YES in S114), it proceeds to S116, and if it determines that the share account name is not stored in the restriction table 40 (NO in S114). ), the process of S116 is skipped and the process of FIG. 9 ends.

S116 is the same as S26 in FIG. 6 except that the share account name in the registration information is stored in the restriction table 40. If the registration information contains multiple share account names, the CPU 32 executes the processes of S114 and S116 for each of the multiple share account names. When the process of S116 ends, the process of FIG. 9 ends.

For example, when it is determined at T190 in FIG. 3 that the restriction flag indicates "OFF", the MFP 10 stores the access information 44 in the memory 34 but does not store the account name in the restriction table 40. FIG. In such a situation, when the restriction flag is changed from "OFF" to "ON" and a predetermined cycle arrives, the MFP 10 stores the account name in the access information 44 in the restriction table 40 (S106). ). Here, the MFP 10 does not accept an operation to input the account name to the operation unit 12 of the MFP 10, and furthermore, without receiving a storage instruction (see T2 in FIG. 1) including the account name from the PC 200 or the like, , the account name is stored in the restriction table 40. Therefore, account names can be easily stored in the restriction table 40 .

Also, the MFP 10 transmits a registration information request to the server 100 and receives the registration information from the server 100 when a predetermined cycle arrives (S110). Then, when the registration information includes the share account name (YES in S112), the MFP 10 stores the share account name in the restriction table 40 (S116). Here, the MFP 10 does not accept an operation to input the share account name to the operation unit 12 of the MFP 10, and furthermore, without receiving a storage instruction (see T2 in FIG. 1) including the share account name from the PC 200 or the like, the predetermined period comes, the share account name is stored in the restriction table 40. - 特許庁Therefore, the share account name can be easily stored in the restriction table 40 .

(Deletion processing; Fig. 10)
Deletion processing for deleting an account name from the restriction table 40 will be described with reference to FIG. T400 is similar to T300 in FIG. 8, except that account information AI1 is included in the login request. T402-T406 are the same as T302-T306 in FIG. At T408, the PC 210 receives the selection of the combination of the model name MN and management identifier MI in the selection screen and the deletion instruction for deleting the device information DI including the management identifier MI.

Upon receiving the deletion instruction in T408, the PC 210 transmits a deletion request including the management identifier MI to the server 100 in T410. The deletion request is a command requesting deletion of the device information DI including the management identifier MI.

When the server 100 receives the deletion request from the PC 200 at T410, it deletes the device information DI including the management identifier MI from the memory 134 at T412.

When the server 100 receives the deletion request from the PC 200 at T410, at T414 the server 100 uses the XMPP connection to transmit a deletion notification notifying that the device information DI will be deleted to the MFP 10. FIG. The deletion notification contains the management identifier MI.

Upon receiving the deletion notification from the server 100 at T414, the MFP 10 deletes the access information 44 from the memory 34 at T416.

Further, when the MFP 10 receives the deletion notification from the server 100 in T414, it deletes the owner account name and the restriction information associated with the owner account name from the restriction table 40 in T418. As a result, unnecessary information (that is, the owner account name and the restriction information) can be deleted from the restriction table 40 without receiving an operation for deleting the owner account name from the restriction table 40 .

Also, when the share account name is stored in the limit table 40, the MFP 10 deletes the share account name and the limit information associated with the share account name from the limit table 40. FIG. As a result, unnecessary information (that is, the share account name and the restriction information) can be deleted from the restriction table 40 without receiving an operation to delete the share account name from the restriction table 40 .

(correspondence relationship)
The MFP 10, the print execution unit 18, the scan execution unit 20, and the memory 34 are examples of the "function execution device", the "first function execution unit", the "second function execution unit", and the "memory", respectively. The mediation server 100 is an example of a "server". The user identification information “John” and the restriction information associated with the user identification information “John” are examples of “specific user identification information” and “specific related information”, respectively. The account name "Ken@server.com" and the restricted information associated with the account name "Ken@server.com" are examples of "first account identification information" and "first relationship information", respectively. . Device information DI is an example of "server usage information". The job notification of T330 in FIG. 8 is an example of the "execution instruction".

A state in which the limit flag 42 indicates "ON" and a state in which the limit flag 42 indicates "OFF" are examples of the "first state" and the "second state," respectively. Restriction information associated with general user information "Public" is an example of "general relationship information." Restriction information associated with the share account name "Bob@server.com" and the share account name "Bob@server.com" are examples of "second account identification information" and "second relationship information", respectively. is. The registration information request in S108 of FIG. 9 is an example of an "inquiry request." The print execution information and the allowable number of sheets are examples of the "function execution information" and the "allowed number of prints", respectively. The deletion notification of T414 in FIG. 10 is an example of "deletion notification".

The process of storing the user identification information "John" in the restriction table 40 in response to the reception of the storage instruction in T2 of FIG. 1 is an example of the process realized by the "first storage control unit". T120 in FIG. 3, T192 in FIG. 3, and S32 in FIG. An example.

(Second embodiment)
The second embodiment is the same as the first embodiment, except that part of the server print process in FIG. 5 and part of the table update process in FIG. 9 are different.

(Server print processing; Fig. 5)
In this embodiment, the processes of S14 and S50 are not executed. That is, when the CPU 32 determines that the restriction flag 42 indicates "ON" (YES in S12), the CPU 32 executes the account printing process in S20, and determines that the restriction flag 42 indicates "OFF" (S12). NO), in S80, printing is executed according to the print job.

(Table update processing; Fig. 9)
In this embodiment, the table update process is triggered by the user operating the operation unit 12 of the MFP 10 to change the restriction flag 42 from "OFF" to "ON". Further, in the present embodiment, the processes after S102 are executed without executing the process of S100.

For example, when it is determined at T190 in FIG. 3 that the restriction flag indicates "OFF", the MFP 10 stores the access information 44 in the memory 34 but does not store the account name in the restriction table 40. FIG. According to the configuration of this embodiment, in such a situation, the account name can be stored in the restriction table 40 when the restriction flag is changed from "OFF" to "ON". That is, the account name can be quickly stored in the limit table 40 compared to the first embodiment in which the account name is stored in the limit table 40 when a predetermined cycle arrives.

Although specific examples of the present invention have been described in detail above, 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. Modifications of the above embodiment are listed below.

(Modification 1) The "function execution device" may not be the MFP 10, but may be, for example, a printer, a scanner, or a FAX device.

(Modification 2) At T192 in FIG. 3, the MFP 10 stores restriction information including print execution information indicating "OK" in the restriction table 40. FIG. Alternatively, the MFP 10 may store restriction information including print execution information indicating "NG" in the restriction table 40. FIG. In this modified example, restriction information including print execution information indicating "NG" is an example of "first relationship information."

(Modification 3) At T336 in FIG. 8, the MFP 10 stores restriction information including print execution information indicating "OK" in the restriction table 40. FIG. Alternatively, the MFP 10 may store restriction information including print execution information indicating "NG" in the restriction table 40. FIG. In this modified example, restriction information including print execution information indicating "NG" is an example of "second relationship information".

(Modification 4) When the print execution information indicates "OK", does the restriction information allow the user to execute the printing function using the specific printing conditions along with the allowable number of sheets or instead of the allowable number of sheets? It may include conditional execution information indicating whether or not. Specific printing conditions include, for example, the number of printing colors (for example, color printing or monochrome printing), the presence or absence of double-sided printing, and the like. Then, in T336 of FIG. 8, the MFP 10 may store restriction information including the same conditional execution information as the conditional execution information associated with the owner account name "Ken@server.com" in the restriction table 40. FIG. In this modification, the conditional execution information associated with the owner account name "Ken@server.com" and the conditional execution information same as the conditional execution information are respectively "first conditional execution information" and "second conditional execution information". This is an example of "conditional execution information".

(Modification 5) The process of T190 in FIG. 3 may not be executed. In this modified example, the "first determination unit" can be omitted.

(Modification 6) The MFP 10 may send an error notification to the server 100 when determining that the owner account name in the job notification is not stored in the restriction table 40 (NO in S14). In this modified example, the "second function control unit" can be omitted.

(Modification 7) The process of S14 in FIG. 5 may not be executed. Generally speaking, the second account identification may be stored in memory when the second account identification is received from the server and the first account identification is not stored in memory. .

(Modification 8) The process of FIG. 4 may not be executed, and the MFP 10 may not receive the share account name from the server 100 . In this modified example, the "second information receiving section" and the "fourth storage control section" can be omitted.

(Modification 9) The processes from S22 to S26 in FIG. 6 may not be executed. Generally speaking, the "execution instructions" may not include the second account identification information.

(Modification 10) The process of FIG. 9 may not be executed. In this modified example, the “transmitting unit” can be omitted.

(Modification 11) In each of the above embodiments, the MFP 10 executes printing in S80 without executing the account printing process when the restriction flag 42 indicates "OFF" (NO in S12). Alternatively, when the restriction flag 42 indicates "OFF" (NO in S12), the MFP 10 may execute printing in S80 after executing the processes of S22 to S26 of FIG. Generally speaking, the second account identification information and the second relationship information may be stored in the memory when the state of the function performing device is determined to be in the second state.

(Modification 12) In each of the above embodiments, the MFP 10 stores limit information including the same allowable number of sheets as the allowable number of sheets of the owner account name in the limit table 40 (S26 in FIG. 6). Alternatively, the MFP 10 may store, in the limit table 40, limit information including the number of sheets allowed, which is less than the number of sheets allowed for the owner account name. Generally speaking, the "second relationship information" may include an allowable number of prints different from the first allowable number of prints.

(Modification 13) The process of FIG. 10 may not be executed. In this modified example, the “notification receiving unit” and the “deletion unit” can be omitted.

(Modification 14) In each of the above embodiments, the MFP 10 deletes the share account name from the restriction table 40 (T418 in FIG. 10). Alternatively, the MFP 10 does not have to delete the share account name from the restriction table 40. Generally speaking, the "deletion unit" may not delete the second account identification information.

(Modification 15) In each of the above-described embodiments, the CPU 32 of the MFP 10 executes the program 36 (that is, software) to implement the processes shown in FIGS. Alternatively, any processing may be implemented by hardware such as logic circuits.
The features of the technology disclosed in this specification are listed below.
(Item 1)
A function performing device,
a first function execution unit for executing a first function;
When specific user identification information for identifying a specific user is input, the specific user identification information and a specification related to whether or not the specific user is allowed to execute the first function A first storage control unit that associates and stores in a memory the relationship information of the the first storage control unit configured to associate and store relational information relating to whether or not execution is permitted to the user;
a first information reception for receiving the first account identification information from the server when server usage information including the first account identification information for a first user to use the server is registered in the server; Department and
When the first account identification information is received from the server, the first account identification information as the user identification information and whether or not the first user is allowed to execute the first function a second storage control unit that associates and stores in the memory the first relationship information related to
After the first account identification information and the first relationship information are stored in the memory, an instruction to execute the first function including the first account identification information is received from the server; and when the first relationship information stored in the memory in association with the first account identification information indicates that the first user is permitted to execute the first function, the first a first function control unit that causes the first function execution unit to execute a function;
A function performing device comprising:
(Item 2)
The function execution device further
when the first account identification information is received from the server, whether the state of the function execution device is the first state using the relationship information or the second state not using the relationship information; A first judgment unit for judging whether there is
The second storage control unit associates the first account identification information with the first relationship information and stores the information in the memory when it is determined that the state of the function execution device is in the first state. stored in
Function execution according to item 1, wherein the first account identification information and the first relationship information are not stored in the memory when the state of the function execution device is determined to be the second state. Device.
(Item 3)
The memory is further configured to store general relationship information related to whether or not to allow general users to perform the first function;
The function execution device further
after the state of the function-performing device is determined to be the second state, the state of the function-performing device is changed from the second state to the first state, and the first account identification an instruction to perform the first function including the first account identification information is received from the server, and the general relationship information indicates that the information is not stored in the memory; Item 3. The function execution device according to item 2, further comprising: a second function control section that causes the first function execution section to execute the first function when indicating that the general user is allowed to perform the function.
(Item 4)
The function execution device further
the first account when the state of the function execution device is changed from the second state to the first state after the state of the function execution device is determined to be the second state; 3. The function execution device according to item 2, further comprising a third storage control unit that associates identification information with the first relationship information and stores the information in the memory.
(Item 5)
The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
When the second account identification information is received from the server and the first account identification information is stored in the memory, the second account identification information as the user identification information; a fourth storage control unit that associates and stores in the memory second relationship information related to whether or not the execution of the first function is permitted to the second user;
with
When the second account identification information is received from the server and the first account identification information is not stored in the memory, the second account identification information and the second relationship information are: 5. A function performing device according to any one of items 2-4, not stored in the memory.
(Item 6)
The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
When the second account identification information is received from the server, the second account identification information as the user identification information and whether or not the second user is permitted to execute the first function a fourth storage control unit that associates and stores in the memory the second relationship information related to
A function-performing device according to any one of items 1 to 5, comprising:
(Item 7)
The second information receiving unit receives an execution instruction of the first function including the second account identification information from the server after the second account identification information is added to the server usage information. 7. The function performing device according to item 6, wherein the second account identification information is received by:
(Item 8)
The function execution device further
a transmission unit for transmitting an inquiry request to the server after the first account identification information and the first relationship information are stored in the memory, wherein the inquiry request is for the second account; comprising the transmitting unit, which is a request for inquiring whether identification information has been added to the server usage information;
The second information receiving unit is a response to the inquiry request from the server after the second account identification information is added to the server usage information and includes the second account identification information. 7. The function-performing device of item 6, receiving the second account identification information by receiving the response.
(Item 9)
The function execution device further
When the second account identification information is received from the server, whether the state of the function execution device is the first state using the relationship information or the second state not using the relationship information A second judgment unit for judging whether there is
The fourth storage control unit associates the second account identification information with the second relational information when the state of the function execution device is determined to be the first state, and stores the information in the memory. stored in
Any of items 6 through 8, wherein the second account identification information and the second relationship information are not stored in the memory when the state of the function performing device is determined to be the second state. A function execution device according to claim 1.
(Item 10)
the first function is a print function;
the first relationship information includes first function execution information indicating whether or not the first user is permitted to execute the print function;
When the first function execution information indicates that the first user is permitted to execute the printing function, the first relational information is further configured to allow the first user to execute the print function. including at least one of a certain first allowable number of prints and first conditional execution information indicating whether or not the first user is permitted to execute the printing function using specific printing conditions. ,
the second relationship information includes second function execution information indicating whether or not the second user is permitted to execute the print function;
When the second function execution information indicates that the second user is permitted to execute the printing function, the second relational information is further configured to allow the second user to execute the print function. allowing the second user to execute the printing function using a certain second allowable number of prints, which is the same as the first allowable number of prints, and the specific print condition; any of items 6 to 9, including at least one of: second conditional execution information indicating whether to 1. A function execution device according to claim 1.
(Item 11)
The function execution device further
a notification receiving unit that receives a deletion notification from the server when the server usage information is deleted from the server;
a deletion unit that deletes the first account identification information and the first relationship information from the memory when the deletion notification is received from the server;
A function-performing device according to any one of items 1 to 10, comprising:
(Item 12)
The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
When the second account identification information is received from the server, the second account identification information as the user identification information and whether or not the second user is permitted to execute the first function a fourth storage control unit that associates and stores in the memory the second relationship information related to
with
12. The function execution device according to item 11, wherein the deletion unit further deletes the second account identification information and the second relationship information from the memory when the deletion notification is received from the server. .
(Item 13)
The function execution device further comprises a second function execution unit for executing a second function different from the first function,
The memory stores, for each of the one or more users, the user identification information that identifies the user and whether or not the user is permitted to execute the first function, and the second function. and the relevant information relating to whether or not execution is permitted to the user, and are stored in association with each other,
When the first account identification information is received from the server, the second storage control unit controls execution of the first function with the first account identification information as the user identification information. from item 1 to store in the memory in association with the first relationship information indicating that the first user is permitted and that the execution of the second function is permitted by the first user. 13. A function performing device according to any one of 12.
(Item 14)
The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
allowing the second user to execute the first function with the second account identification information as the user identification information when the second account identification information is received from the server; a fourth storage control unit for storing in the memory in association with second relationship information indicating that the second user is not allowed to execute the second function, and
14. A function-performing device according to item 13, comprising:
(Item 15)
By receiving the execution instruction of the first function including the second account identification information after the second account identification information is added to the server usage information, 15. A function performing device according to item 14, receiving the second account identification information.
(Item 16)
A computer program for a function performing device, comprising:
The function execution device comprises a first function execution unit for executing a first function,
The computer of the function execution device has the following parts, namely:
When specific user identification information for identifying a specific user is input, the specific user identification information and a specification related to whether or not the specific user is allowed to execute the first function A first storage control unit that associates and stores in a memory the relationship information of the the first storage control unit configured to associate and store relational information relating to whether or not execution is permitted to the user;
a first information reception for receiving the first account identification information from the server when server usage information including the first account identification information for a first user to use the server is registered in the server; Department and
When the first account identification information is received from the server, the first account identification information as the user identification information and whether or not the first user is allowed to execute the first function a second storage control unit that associates and stores in the memory the first relationship information related to
After the first account identification information and the first relationship information are stored in the memory, an instruction to execute the first function including the first account identification information is received from the server; and when the first relationship information stored in the memory in association with the first account identification information indicates that the first user is permitted to execute the first function, the first a first function control unit that causes the first function execution unit to execute a function;
A computer program that acts as

2: Communication system, 6: Internet, 10: MFP, 12: Operation unit, 14: Display unit, 16: Network I/F, 18: Print execution unit, 20: Scan execution unit, 30: Control unit, 32: CPU , 34: memory, 36: program, 40: restriction table, 42: restriction flag, 44: access information, 100: mediation server, 134: memory, AD: MAC address, AI1, AI2: account information, AT: access token, DI: device information, DN: device name, FI: function information, MI: management identifier, MN: model name, PD: print data, PJ: print job, RT: registration token

Claims (16)

A function performing device,
a first function execution unit for executing a first function;
When specific user identification information for identifying a specific user is input, the specific user identification information and a specification related to whether or not the specific user is allowed to execute the first function A first storage control unit that associates and stores in a memory the relationship information of the the first storage control unit configured to associate and store relational information relating to whether or not execution is permitted to the user;
a first information reception for receiving the first account identification information from the server when server usage information including the first account identification information for a first user to use the server is registered in the server; Department and
When the first account identification information is received from the server, the first account identification information as the user identification information and whether or not the first user is allowed to execute the first function a second storage control unit that associates and stores in the memory the first relationship information related to
After the first account identification information and the first relationship information are stored in the memory, an instruction to execute the first function including the first account identification information is received from the server; and when the first relationship information stored in the memory in association with the first account identification information indicates that the first user is permitted to execute the first function, the first a first function control unit that causes the first function execution unit to execute a function;
A function performing device comprising: The function execution device further
when the first account identification information is received from the server, whether the state of the function execution device is the first state using the relationship information or the second state not using the relationship information; A first judgment unit for judging whether there is
The second storage control unit associates the first account identification information with the first relationship information and stores the information in the memory when it is determined that the state of the function execution device is in the first state. stored in
2. The function of claim 1, wherein the first account identification information and the first relationship information are not stored in the memory when the state of the function performing device is determined to be the second state. execution device. The memory is further configured to store general relationship information related to whether or not to allow general users to perform the first function;
The function execution device further
after the state of the function-performing device is determined to be the second state, the state of the function-performing device is changed from the second state to the first state, and the first account identification an instruction to perform the first function including the first account identification information is received from the server, and the general relationship information indicates that the information is not stored in the memory; 3. The function execution device according to claim 2, further comprising a second function control section that causes said first function execution section to execute said first function when indicating that said general user is permitted to perform said function. The function execution device further
the first account when the state of the function execution device is changed from the second state to the first state after the state of the function execution device is determined to be the second state; 3. The function execution device according to claim 2, further comprising a third storage control unit that associates identification information with said first relationship information and stores them in said memory. The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
When the second account identification information is received from the server and the first account identification information is stored in the memory, the second account identification information as the user identification information; a fourth storage control unit that associates and stores in the memory second relationship information related to whether or not the execution of the first function is permitted to the second user;
with
When the second account identification information is received from the server and the first account identification information is not stored in the memory, the second account identification information and the second relationship information are: 5. A function performing device as claimed in any one of claims 2 to 4, not stored in the memory. The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
When the second account identification information is received from the server, the second account identification information as the user identification information and whether or not the second user is permitted to execute the first function a fourth storage control unit that associates and stores in the memory the second relationship information related to
5. A function performing device according to any one of claims 1 to 4 , comprising a . The second information receiving unit receives an execution instruction of the first function including the second account identification information from the server after the second account identification information is added to the server usage information. 7. The function performing device of claim 6, receiving the second account identification information by: The function execution device further
a transmission unit for transmitting an inquiry request to the server after the first account identification information and the first relationship information are stored in the memory, wherein the inquiry request is for the second account; comprising the transmitting unit, which is a request for inquiring whether identification information has been added to the server usage information;
The second information receiving unit, after the second account identification information has been added to the server usage information, receives from the server a response to the inquiry request in which the second account identification information is the 7. The function execution device according to claim 6, wherein said second account identification information is received by receiving said response indicating that it has been added to server usage information and including said second account identification information. The function execution device further
When the second account identification information is received from the server, whether the state of the function execution device is the first state using the relationship information or the second state not using the relationship information A second judgment unit for judging whether there is
The fourth storage control unit associates the second account identification information with the second relational information when the state of the function execution device is determined to be the first state, and stores the information in the memory. stored in
The second account identification information and the second relationship information are not stored in the memory when the state of the function execution device is determined to be the second state. 1. A function execution device according to claim 1. the first function is a print function;
the first relationship information includes first function execution information indicating whether or not the first user is permitted to execute the print function;
When the first function execution information indicates that the first user is permitted to execute the printing function, the first relational information is further configured to allow the first user to execute the print function. including at least one of a certain first allowable number of prints and first conditional execution information indicating whether or not the first user is permitted to execute the printing function using specific printing conditions. ,
the second relationship information includes second function execution information indicating whether or not the second user is permitted to execute the print function;
When the second function execution information indicates that the second user is permitted to execute the printing function, the second relational information is further configured to allow the second user to execute the print function. allowing the second user to execute the printing function using a certain second allowable number of prints, which is the same as the first allowable number of prints, and the specific print condition; 10. The second conditional execution information that indicates whether or not to execute the conditional execution, the second conditional execution information being the same as the first conditional execution information, and at least one of: A function performing device according to any one of the preceding claims. The function execution device further
a notification receiving unit that receives a deletion notification from the server when the server usage information is deleted from the server;
a deletion unit that deletes the first account identification information and the first relationship information from the memory when the deletion notification is received from the server;
11. A function-performing device according to any one of claims 1 to 10, comprising a . The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
When the second account identification information is received from the server, the second account identification information as the user identification information and whether or not the second user is permitted to execute the first function a fourth storage control unit that associates and stores in the memory the second relationship information related to
with
12. The function execution according to claim 11, wherein said deletion unit further deletes said second account identification information and said second relationship information from said memory when said deletion notification is received from said server. Device. The function execution device further comprises a second function execution unit for executing a second function different from the first function,
The memory stores, for each of the one or more users, the user identification information that identifies the user and whether or not the user is permitted to execute the first function, and the second function. and the relevant information relating to whether or not execution is permitted to the user, and are stored in association with each other,
When the first account identification information is received from the server, the second storage control unit controls execution of the first function with the first account identification information as the user identification information. and said first relational information indicating permission for said first user and said first relational information indicating permission for said first user to execute said second function are stored in said memory in association with said first relational information. 13. A function performing device according to any one of 12 to 13. The function execution device further
receiving the second account identification information from the server after the second account identification information for a second user different from the first user to use the server is added to the server usage information; a second information receiving unit;
allowing the second user to execute the first function with the second account identification information as the user identification information when the second account identification information is received from the server; a fourth storage control unit for storing in the memory in association with second relationship information indicating that the second user is not allowed to execute the second function, and
14. The function-performing device of claim 13, comprising: By receiving the execution instruction of the first function including the second account identification information after the second account identification information is added to the server usage information, the second information receiving unit 15. The function performing device of claim 14, receiving the second account identification information. A computer program for a function performing device, comprising:
The function execution device comprises a first function execution unit for executing a first function,
The computer of the function execution device has the following parts, namely:
When specific user identification information for identifying a specific user is input, the specific user identification information and a specification related to whether or not the specific user is allowed to execute the first function A first storage control unit that associates and stores in a memory the relationship information of the the first storage control unit configured to associate and store relational information relating to whether or not execution is permitted to the user;
a first information reception for receiving the first account identification information from the server when server usage information including the first account identification information for a first user to use the server is registered in the server; Department and
When the first account identification information is received from the server, the first account identification information as the user identification information and whether or not the first user is allowed to execute the first function a second storage control unit that associates and stores in the memory the first relationship information related to
After the first account identification information and the first relationship information are stored in the memory, an instruction to execute the first function including the first account identification information is received from the server; and when the first relationship information stored in the memory in association with the first account identification information indicates that the first user is permitted to execute the first function, the first a first function control unit that causes the first function execution unit to execute a function;
A computer program that acts as

Images