Image forming apparatus, system, control method of the image forming apparatus, and program

Abstract

To provide a mechanism capable of allowing a user to change contract information regarding use of a function of an image forming apparatus managed by a server in a flow when the function is used by the image forming apparatus.SOLUTION: In a MFP 101 that acquires contract information managed by a device management server 102 or a service management server 103 and restricts or disables use of a function according to the contract information, a CPU 201 receives the change of the contract information at a predetermined timing (step S512).SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to an image forming apparatus, a system, a control method for an image forming apparatus, and a program. [Background technology]

[0002] Image forming devices with network capabilities are offering a variety of services that are realized by transmitting device information and user usage history from the image forming device to a server. Examples of such services include, for example, a defect analysis and billing system, as well as a service that manages consumables such as ink on a server and automatically delivers the consumables to the user of the image forming device when the remaining amount of the consumables becomes low.

[0003] In recent years, the introduction of subscription contracts has led to the widespread provision of fixed-price services in which devices and consumables are rented to users who sign a service contract, eliminating initial investment and maintenance costs. In contract-based flat-rate services, an image forming device communicates with a server to acquire contract information indicating the status of the contract from the server, and controls the image forming device in accordance with the acquired contract information. In this case, control of the image forming device may include, for example, limiting or disabling the use of functions and settings (including settings within functions) of the image forming device in accordance with the contract information. In this specification, the functions and settings of the image forming device are abbreviated as "functions of the image forming device."

[0004] Furthermore, in a configuration in which the image forming device cooperates with a server in this manner, it is important for the image forming device to obtain contract information as quickly as possible. Therefore, Patent Document 1 proposes a technology in which contract information is sent to the image forming device by push notification from the server using a communication protocol such as Message Queueing Telemetry Transport. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2018-92548 Summary of the Invention [Problem to be solved by the invention]

[0006] However, while using an image forming apparatus, a user may wish to exceed the upper limit of the functions restricted by the contract information, or may wish to use a function that is prohibited by the contract information. In these cases, the user must change the contract information managed by the server using a device other than the image forming apparatus (for example, a personal computer or a smartphone). This requires the user to stop using the image forming apparatus.

[0007] The present invention has been made in view of the above-mentioned problems, and aims to provide a mechanism that allows a user to change contract information related to the use of functions of an image forming device, which is managed by a server, during the process of using the functions on the image forming device. [Means for solving the problem]

[0008] In order to achieve the above object, the image forming apparatus of the present invention is an image forming apparatus that acquires contract information managed by a server and restricts or disables the use of functions according to the contract information, and is characterized by having a reception means that receives changes to the contract information at a predetermined timing. [Effects of the Invention]

[0009] According to the present invention, the user can change the contract information related to the use of the functions of the image forming apparatus, which is managed by the server, during the process of using the functions on the image forming apparatus. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of the overall configuration of an information processing system. [Figure 2] FIG. 1 is a diagram illustrating an example of the hardware configuration of a multifunction peripheral (hereinafter referred to as "MFP"). [Figure 3] FIG. 2 illustrates an example of a schematic hardware configuration of a device management server. [Figure 4] FIG. 2 illustrates an example of a schematic hardware configuration of a service management server. [Figure 5] FIG. 10 is a diagram showing an example of a sequence from signing a service contract to becoming able to use the functions of the MFP. [Figure 6] FIG. 10 is a diagram showing an example of a counter created and saved in the MFP. [Figure 7] 10 is a flowchart showing each process from acquisition to change of contract information in the MFP. [Figure 8] 10 is a flowchart showing a process for changing contract information. [Figure 9] FIG. 10 is a diagram showing an example of a contract change screen displayed on the operation unit of the MFP. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. However, not all of the combinations of features described in the following embodiments are necessarily essential to the solution of the invention. Furthermore, the configurations described in the embodiments are merely exemplary, and the scope of the present invention is not limited to the configurations described in the embodiments. For example, each component constituting the present invention can be replaced with any configuration that can perform the same function. Furthermore, any component may be added. Furthermore, any two or more configurations (features) of the present embodiments can be combined. Note that in the present embodiments, an MFP having a printing function (including a copying function), a scanning function, a fax function, etc. will be described as an example of the image forming apparatus of the present invention. However, the image forming apparatus of the present invention is not limited to an MFP, and may be an apparatus having one or more functions such as a printing function, a copying function, a scanning function, and a fax function.

[0012] Figure 1 is a diagram showing an example of the overall configuration of an information processing system (system). The information processing system 100 has an MFP 101, a device management server 102 (server), and a service management server 103 (server). The MFP 101, the device management server 102, and the service management server 103 are communicably connected via a communication network 104 such as the Internet. The MFP 101 stores contract information in an HDD (204 in Figure 2) described below, and controls the MFP 101 in accordance with the stored contract information. The MFP 101 acquires the contract information by communicating with the device management server 102 via the communication network 104.

[0013] The device management server 102 stores the contract information notified by the service management server 103, and provides the contract information to the MFP 101 based on the stored contract information. A communication protocol such as Hypertext Transfer Protocol (hereinafter referred to as "HTTP") is used for communication between the device management server 102 and the MFP 101, and a known control method is used. A communication protocol such as HTTP is also used for communication between the device management server 102 and the service management server 103. As shown in FIG. 5 (described later), the communication between the MFP 101 and the service management server 103 is configured to include the device management server 102, but this is not limiting. For example, the MFP 101 and the service management server 103 may directly exchange contract information and the like via a communication network 104 such as the Internet. In this case, a communication protocol such as HTTP is also used for communication between the MFP 101 and the service management server 103.

[0014] 2 is a diagram illustrating an example of the hardware configuration of MFP 101. MFP 101 has a control unit 200. The control unit 200 has a CPU 201, a ROM 202, a RAM 203, a HDD 204, an operation unit I / F 205, a reading unit I / F 206, a printing unit I / F 207, a wireless communication unit I / F 208, a FAX unit I / F 209, and a communication unit I / F 210. MFP 101 also has an operation unit 211, a reading unit 212, a printing unit 213, a wireless communication unit 214, a FAX communication unit 215, and a communication unit 216. The control unit 200 controls the overall operation of MFP 101 using the CPU 201 and other components. The CPU 201 is a computer that performs various types of control, such as reading control and printing control, by loading a control program stored in ROM 202 or HDD 204 into RAM 203 and executing it.

[0015] The ROM 202 stores control programs and the like. The ROM 202 also stores a boot program, font data, and the like. The RAM 203 is the main memory of the CPU 201 and is used as a work area. The RAM 203 is also used as a temporary storage area for expanding various control programs stored in the ROM 202 or the HDD 204. The HDD 204 stores image data, print data, various programs, various addresses, various setting data, and the like. The HDD 204 is a storage medium. Note that instead of the HDD 204, for example, an SSD or eMMC may be used. In the MFP 101, one CPU 201 executes each process described below using one memory (RAM 203), but this is not limiting. For example, each process may be executed by multiple CPUs, RAMs, ROMs, and HDDs working together. Furthermore, some processes may be executed by hardware circuits such as ASICs or FPGAs.

[0016] The operation unit I / F 205 connects the control unit 200 to the operation unit 211. The operation unit 211 includes, for example, a display unit such as a touch panel and hard keys, and displays information to the user and detects input from the user. The reading unit I / F 206 connects the control unit 200 to the reading unit 212. The reading unit 212 is, for example, a scanner, and reads an image of a document. The image read by the reading unit 212 is converted into image data such as binary data by the CPU 201. The image data generated in this manner is sent to an external device or printed on recording paper.

[0017] The printing unit I / F 207 connects the control unit 200 to the printing unit 213. The printing unit 213 is, for example, a printer. The CPU 201 transfers image data (print data) stored in the RAM 203 to the printing unit 213 via the printing unit I / F 207. The printing unit 213 prints an image based on the transferred image data on recording paper fed from a paper feed cassette (not shown). The wireless communication unit I / F 208 is an I / F for controlling the wireless communication unit 214 and connects the control unit 200 to an external wireless device via wireless communication. The FAX unit I / F 209 controls the FAX communication unit 215 to be connected to the public line network 217. The FAX unit I / F 209 is an I / F for controlling the FAX communication unit 215 and controls a modem and NCU for facsimile communication, thereby enabling connection to the public line network 217, control of the facsimile communication protocol, and the like.

[0018] The communication unit I / F 210 connects the control unit 200 to the communication network 104 via the communication unit 216. The communication unit I / F 210 transmits image data and various types of information inside the MFP 101 to external devices on the communication network 104, and receives print data and information on the communication network 104 from external devices on the communication network 104, using the communication unit 216. Methods for transmitting and receiving data via the communication network 104 include transmission and reception using electronic mail (E-mail) and file transmission using other protocols (e.g., FTP, SMB, WEBDAV, etc.). Furthermore, the communication unit I / F 210 can also transmit and receive image data, various setting data, contract information, etc. over the communication network 104 by accessing the device management server 102 or the service management server 103 via HTTP communication.

[0019] FIG. 3 illustrates an example of the schematic hardware configuration of the device management server 102. The device management server 102 includes a CPU 301, a ROM 302, a RAM 303, a HDD 304, and a network connection unit 305. The CPU 301 is a computer that performs processes such as calculation, judgment, and control of data and commands in accordance with a control program stored in the ROM 302 or the HDD 304. The ROM 302 stores the control program and other programs. The RAM 303 is used as a temporary storage area when the CPU 301 performs various processes. The HDD 304 stores an operating system (OS), application software, and control programs. The HDD 304 also stores device information for each device and contract information indicating the status of service contracts. The network connection unit 305 uses a wireless LAN or a wired LAN compatible with standards such as IEEE802.11a to exchange data with devices on the same network or the Internet using protocols such as TCP / IP.

[0020] FIG. 4 is a diagram illustrating an example of a schematic hardware configuration of the service management server 103. The service management server 103 includes a CPU 401, a ROM 402, a RAM 403, a HDD 404, and a network connection unit 405. The schematic hardware configuration of the service management server 103 is similar to that of the device management server 102 described above, and therefore a detailed description thereof will be omitted. Note that the schematic hardware configurations illustrated in FIGS. 3 and 4 are not limited to the above configuration. For example, the services that can be provided by the device management server 102 or the service management server 103 may be realized by a server on a cloud. Furthermore, the device management server 102 and the service management server 103 do not need to each be configured as a single server. In other words, the functions provided by the device management server 102 and the service management server 103 may be realized by a server system consisting of three or more servers, or by a single server that aggregates all of the functions.

[0021] Fig. 5 is a diagram showing an example of a sequence from when a service contract is made until the functions of MFP 101 can be started. Each step of MFP 101 in Fig. 5 (a control method of an image forming apparatus) is realized by CPU 201 (a computer) loading a control program (a program) read from ROM 202 or HDD 204 into RAM 203 and executing the program. Each step of device management server 102 in Fig. 5 is realized by CPU 301 loading a control program read from ROM 302 or HDD 304 into RAM 303 and executing the program. Each step of service management server 103 in Fig. 5 is realized by CPU 401 loading a control program read from ROM 402 or HDD 404 into RAM 403 and executing the program.

[0022] In step S501, a user accesses a system that manages services on service management server 103 using a personal computer, smartphone, or the like, and concludes a service contract on the system. The service contract concluded by the user is a subscription contract for MFP 101 and relates to the use of functions of MFP 101. In step S502, in service management server 103, in response to the user's conclusion of the service contract, CPU 401 performs service registration processing that links user information with MFP 101. The user information includes contract information (hereinafter simply referred to as "contract information") regarding the service contract concluded by the user. The contents of the service registration processing are saved in HDD 404. In step S503, when service management server 103 completes the service registration processing, the service provider delivers MFP 101 registered in step S502 to the user. In step S504, upon receiving MFP 101, the user unpacks MFP 101 and begins initial installation of MFP 101.

[0023] In step S505, in the MFP 101, the CPU 201 performs initial installation processing in accordance with instructions from the user during initial installation of the MFP 101. In this initial installation processing, the CPU 201 performs initial settings such as network settings for connecting to the Internet. In step S506, when the network connection is completed during initial settings in the MFP 101, the CPU 201 communicates a device registration request to the device management server 102. In this device registration request communication, the CPU 201 transmits identification information such as the product serial number of the MFP 101 along with the device registration request. In step S507, in the device management server 102, in response to the device registration request communication from the MFP 101, the CPU 301 performs device registration processing based on the identification information received from the MFP 101. Furthermore, when the device registration processing is completed, the CPU 301 returns the registration result to the MFP 101.

[0024] In step S508, CPU 301 in device management server 102 notifies service management server 103 of the completion of device registration. At this time, CPU 301 transmits identification information such as the product serial number of MFP 101 along with the device registration completion notification to service management server 103. Note that if service management server 103 is made up of multiple servers, this device registration completion notification may be configured to be sent to the server responsible for each service.

[0025] In step S509, in the service management server 103, in response to the device management server 102 notifying the device management server 102 of the completion of device registration, the CPU 401 notifies the device management server 102 of the contract information. In this contract information notification, the CPU 401 notifies the device management server 102 of the contract information linked to the MFP 101. In this embodiment, the contract information includes information for determining that a contract has been concluded to be used for activation after the initial setting of the MFP 101, and information on the upper limit number for creating a counter in FIG. 6 (described later). In the device management server 102, the CPU 301 saves the contract information notified from the service management server 103 in the HDD 304.

[0026] In step S510, in the MFP 101, the CPU 201 transmits a contract information acquisition request to the device management server 102. Note that this contract information acquisition request is a request to acquire multiple pieces of contract information collectively, and is not a request made for each contract for multiple services. Furthermore, in the device management server 102, in response to the MFP 101 transmitting the contract information acquisition request, the CPU 301 (transmission means) notifies the MFP 101 of each piece of contract information stored in the HDD 304 in an HTTP response.

[0027] In step S511, when the CPU 201 (receiving means) of the MFP 101 receives each piece of contract information from the device management server 102, the CPU 201 stores the received piece of contract information in the HDD 204. Furthermore, in the MFP 101, the CPU 201 reflects control according to the received piece of contract information in various controls such as subsequent reading control and printing control.

[0028] Specifically, for example, once CPU 201 confirms that a service contract has been concluded, it releases functions related to the service that have been unavailable until then, making them available to the user. This embodiment is an example in which MFP 101 is provided to a user on the condition that the user has concluded a service contract. Therefore, until it is confirmed in step S511 that a service contract has been concluded, all basic functions of MFP 101, such as the print function, scan function, and fax function, are unavailable. Then, after step S511, these functions become available according to the contract information for the service contract that has been confirmed to have been concluded.

[0029] In this embodiment, there are cases where the contract information can be changed in the MFP 101. In this case, in step S512, the CPU 201 (reception means) of the MFP 101 changes the contract information stored in the HDD 204 (reception step). Note that step S512 will be described in detail later with reference to the flowcharts of FIGS. 7 and 8. In step S513, the CPU 201 (transmission means) of the MFP 101 notifies the device management server 102 of the changed contract information using the HTTP PUT / POST method. As a result, the contract information stored in the HDD 304 of the device management server 102 is updated. In step S514, the CPU 301 of the device management server 102 notifies the service management server 103 of the contract information notified from the MFP 101 using the HTTP PUT / POST method. As a result, the contract information stored in the HDD 404 of the service management server 103 is updated. In this embodiment, the order has been described as the conclusion of a service contract followed by the device registration process, but the order may be reversed, with the device registration process being performed first and the service contract being concluded second.

[0030] 6 is a diagram showing an example of counters created by the MFP 101 and stored in the HDD 204. In the MFP 101, the CPU 201 creates each of the counters 601 to 604 in accordance with the contract information acquired from the device management server 102. Furthermore, the CPU 201 creates upper limit numbers for each of the counters 601 to 604 by file format and print type in accordance with the contract information acquired from the device management server 102.

[0031] Counter 601 is a counter for each format in normal scanning, which can be used without restrictions. When a scan job is executed in which the format (setting within the scan function) for sending a file by email or the like is specified as PDF, TIFF, or the like, counter 601 counts up the number of scanned pages for the specified format. Counter 602 is a counter for each print type in normal printing, which can be used without restrictions. When a print job is executed in which the print type (setting within the print function) is specified as COPY, PDL, or media print, counter 602 counts up the number of printed pages for the specified print type.

[0032] Counter 603 is a counter for each format in optional scanning, which has a set upper limit. In this embodiment, encrypted PDF and machine-signed PDF are used as examples of formats in optional scanning. When a scan job is executed in which the format for sending a file via email or the like is specified as encrypted PDF or machine-signed PDF, counter 603 counts up the number of scanned pages for the specified file format.

[0033] Counter 604 is a counter for each print type in optional printing, which has a set upper limit. In this embodiment, BarDIMM is used as an example of a print type in optional printing. BarDIMM refers to page description language printing that supports a specific barcode font. When a print job in which BarDIMM is specified as the print type is executed, counter 604 counts up the number of printed sheets for the specified print type. Note that in this embodiment, counters 601 to 604 are created for each file format and print type, but counters may also be created for each post-processing step, such as stapling.

[0034] Fig. 7 is a flowchart showing each process from acquisition to change of contract information in MFP 101. The flowchart shown in Fig. 7 provides a detailed explanation of each process in MFP 101 from step S510 to step S512 in Fig. 5. Each step in Fig. 7 is realized by CPU 201 in MFP 101 loading a control program read from ROM 202 or HDD 204 into RAM 203 and executing it. This also applies to each step shown in the flowchart in Fig. 8, which will be described later.

[0035] In step S701, CPU 201 acquires contract information from device management server 102. Furthermore, CPU 201 releases available functions according to the acquired contract information. In step S702, CPU 201 determines whether the contract information includes a function with a set upper limit. If CPU 201 determines that the contract information includes a function with a set upper limit, processing proceeds to step S703. On the other hand, if CPU 201 determines that the contract information does not include a function with a set upper limit, processing proceeds to step S704.

[0036] In step S703, the CPU 201 (creation means) creates limit counters (counters) for functions whose upper limit numbers are determined in the contract information. Specifically, counters 603 and 604 shown in FIG. 6 are created as limit counters. The CPU 201 (creation means) also creates limit counters (counters) for functions whose use is prohibited in the contract information. In this case, the upper limit number of the limit counter is set to 0, which is the initial value of the limit counter. Counters 601 and 602 shown in FIG. 6 are normal counters, which will be described later, and are created separately from the limit counters.

[0037] In step S704, CPU 201 determines whether the user has instructed to submit a job. If CPU 201 determines that the user has not instructed to submit a job, the process returns to step S704. On the other hand, if CPU 201 determines that the user has instructed to submit a job, the process proceeds to step S705. In step S705, CPU 201 determines whether the submitted job uses a function whose upper limit is determined in the contract information. If CPU 201 determines that the submitted job does not use a function whose upper limit is determined in the contract information, the process proceeds to step S706. On the other hand, if CPU 201 determines that the submitted job uses a function whose upper limit is determined in the contract information, the process proceeds to step S707.

[0038] In step S706, CPU 201 increments the count of a normal counter according to the number of scanned sheets or the number of printed sheets when the submitted job is executed. Specifically, the counts of counters 601 and 602 shown in FIG. 6 are incremented. The flowchart in FIG. 7 then ends. In step S707, CPU 201 determines whether the count of a limit counter for a function used by the submitted job is the same as the upper limit. If CPU 201 determines that the count of the limit counter is not the same as the upper limit, the process proceeds to step S708. On the other hand, if CPU 201 determines that the count of the limit counter is the same as the upper limit, the process proceeds to step S710.

[0039] In step S708, CPU 201 (counting means) increments the count of a limit counter according to the number of scanned sheets or the number of printed sheets when the submitted job is executed. Specifically, the counts of counters 603 and 604 shown in FIG. 6 are incremented. In step S709, CPU 201 determines whether the count of the limit counter for the function used by the submitted job has reached or exceeded its upper limit. If CPU 201 determines that the count of the limit counter has reached or exceeded its upper limit, the process proceeds to step S710. On the other hand, if CPU 201 determines that the count of the limit counter has not reached or exceeded its upper limit, the flowchart in FIG. 7 ends. In step S710, CPU 201 performs a process to change the contract information. Details of this process to change the contract information will be described using the flowchart in FIG. 8.

[0040] 8 is a flowchart showing a contract information change process. In step S801, the CPU 201 determines whether the count number and upper limit number of the limit counter for the function used by the submitted job are the initial values ​​of 0. If the CPU 201 determines that the count number and upper limit number of the limit counter are the initial values ​​of 0, the process proceeds to step S802. On the other hand, if the CPU 201 determines that the count number and upper limit number of the limit counter are not the initial values ​​of 0, the process proceeds to step S803. In step S802, the CPU 201 recognizes (at a predetermined timing) that an instruction to use a function that is prohibited from use in the contract information has been issued, and displays a first screen (901 in FIG. 9) (UI screen) described below on the operation unit 211 without executing the submitted job. Thereafter, the process returns to the flowchart of FIG. 7.

[0041] In step S803, CPU 201 determines whether the process of step S709 has been performed. If CPU 201 determines that the process of step S709 has not been performed, the process proceeds to step S804. On the other hand, if CPU 201 determines that the process of step S709 has been performed, the process proceeds to step S805. In step S804, CPU 201 recognizes (at a predetermined timing) that the use of the function whose use is limited by the contract information is at the upper limit before the submitted job is executed, and displays a second screen (902 in FIG. 9) (UI screen) described below on operation unit 211. Thereafter, the process returns to the flowchart of FIG. 7. In step S805, CPU 201 recognizes (at a predetermined timing) that the use of the function whose use is limited by the contract information is at or has exceeded the upper limit after the submitted job is executed. Furthermore, CPU 201 displays a third screen (302 in FIG. 9) (UI screen) described below on operation unit 211. Thereafter, the process returns to the flowchart of FIG. 7. Returning to the description of Fig. 7, after the CPU 201 performs the contract information change process in step S710, the flowchart of Fig. 7 ends.

[0042] FIG. 9 shows an example of a contract change screen displayed on operation unit 211 of MFP 101. A first screen 901 is a contract change screen that pops up on operation unit 211 before a submitted job is executed, when the count value and upper limit of the limit counter for a function used in the job are 0. That is, first screen 901 is a pop-up window that is displayed when a command to use a function that is prohibited in the contract information is issued. When a user presses a Yes button 902 on first screen 901, CPU 201 of MFP 101 changes the contract information to the content of the message displayed on first screen 901 in step S512 of FIG. 5. This allows the user to use the function that was prohibited in the contract information before the change. In contrast, when a user presses a No button 903, CPU 201 of MFP 101 cancels the submitted unexecuted job without changing the contract information.

[0043] The second screen 904 is a contract change screen that pops up on the operation unit 211 when the count value of the limit counter is not 0 and is equal to the upper limit before the submitted job is executed. That is, the second screen 904 is a pop-up window that is displayed when the usage of a function whose usage is limited by the contract information is at the upper limit before the submitted job is executed. When the user presses the Yes button 905 on the second screen 904, the CPU 201 of the MFP 101 changes the contract information in accordance with the content of the message displayed on the second screen 904 in step S512 of FIG. 5 . This allows the user to increase the upper limit of the limit counter for a function whose usage is limited by the contract information when the usage of that function is at the upper limit. In contrast, when the user presses the No button 906, the CPU 201 of the MFP 101 cancels the submitted job before execution without changing the contract information.

[0044] Third screen 907 is a contract change screen that pops up on operation unit 211 when, after a submitted job has been executed, the count value of the limit counter is not 0 but equals or exceeds the upper limit. That is, third screen 907 is a pop-up window that is displayed when, after a submitted job has been executed, the usage limit of a function whose usage is limited by the contract information has been reached or exceeded. When a user presses Yes button 908 on third screen 907, CPU 201 of MFP 101 changes the contract information in accordance with the contents of the message displayed on third screen 907 in step S512 of FIG. 5 . This allows the user to increase the upper limit of the limit counter for a function whose usage is limited by the contract information when the upper limit has been reached or exceeded. On the other hand, when a user presses No button 909, CPU 201 of MFP 101 does not change the contract information.

[0045] As described above, in this embodiment, the user can change contract information related to the use of functions of MFP 101, which is managed by service management server 103 or the like, during the process of using the functions on MFP 101. In other words, the user can change the contract information on operation unit 211 of MFP 101 that is in use when the user wants to use a function that is prohibited from use in the contract information, or when the user wants to use a function whose use is limited in the contract information beyond that upper limit.

[0046] While the preferred embodiment of the present invention has been described above, the present invention is not limited to this embodiment, and various modifications and variations are possible within the spirit and scope of the present invention. For example, in step S707, CPU 201 of MFP 101 determines whether the count value of the limit counter for the function used by the submitted job is the same as the upper limit before the job is executed. In this regard, CPU 201 of MFP 101 may also determine whether the count value of the limit counter for the function used by the submitted job will be equal to or greater than the upper limit if the submitted job is executed. In this case, when CPU 201 of MFP 101 determines that the count value of the limit counter for the function used by the job will be equal to or greater than the upper limit (at a predetermined timing), second screen 904 is displayed as a pop-up on operation unit 211 of MFP 101.

[0047] Furthermore, in step S709, CPU 201 of MFP 101 determines whether the count number of the limit counter for the function used by the submitted job has reached or exceeded the upper limit after the submitted job is executed. In this regard, CPU 201 of MFP 101 may determine whether the count number of the limit counter for the function used by the submitted job has reached the upper limit while the submitted job is being executed. In this case, when CPU 201 of MFP 101 determines that the count number of the limit counter for the function used by the job has reached the upper limit (at a predetermined timing), third screen 907 is displayed as a pop-up on operation unit 211 of MFP 101. At this time, if a Yes button 908 is pressed by the user on third screen 907, CPU 201 of MFP 101 changes the contract information so that the currently executing job can continue. In contrast, if a No button 909 is pressed by the user, CPU 201 of MFP 101 cancels the currently executing job without changing the contract information.

[0048] Furthermore, CPU 201 (display means) of MFP 101 may display, for example, a grayed-out button for using a function that is disabled in the contract information on operation unit 211 of MFP 101. The grayed-out button display allows the user to visually recognize that a function that would be available by pressing the button is unavailable. In this case, when the button is pressed by the user (at a predetermined timing), CPU 201 (reception means) of MFP 101 displays, for example, first screen 901 as a pop-up on operation unit 211 of MFP 101.

[0049] Furthermore, CPU 201 (display means) of MFP 101 may display, by graying out or the like, a button for using a function that has been used up to the upper limit among the functions whose use is limited by the contract information on operation unit 211 of MFP 101. The user can visually recognize from the grayed-out button display that a function that would be available by pressing the button is not available. In this case, when the button is pressed by the user (at a predetermined timing), CPU 201 (reception means) of MFP 101 displays, for example, third screen 907 as a pop-up on operation unit 211 of MFP 101.

[0050] Furthermore, in this embodiment, contract information is changed based on the content of a message displayed on operation unit 211 of MFP 101, but this is not limited to this and may be changed based on content entered by the user using hard keys included in operation unit 211, for example. The present invention can also be realized by supplying a program that realizes one or more functions of this embodiment to a system or device via a network or storage medium, and having one or more processors of a computer in that system or device read and execute the program. The present invention can also be realized by a circuit (for example, an ASIC) that realizes one or more functions.

[0051] The disclosure of the present embodiment includes the following configurations, systems, methods, and programs. (Configuration 1) An image forming apparatus that acquires contract information managed by a server and limits or disables use of functions according to the contract information, The image forming apparatus further comprises a receiving unit that receives a change to the contract information at a predetermined timing. (Configuration 2) The image forming device described in Configuration 1 is characterized in that the receiving means recognizes the specified timing as when it determines that the usage of a function whose usage is limited in the contract information has reached or exceeded the upper limit, or when it determines that an instruction has been given to use a function whose usage is prohibited in the contract information. (Configuration 3) The image forming apparatus according to configuration 1 or 2, wherein the accepting unit accepts changes to the contract information on a UI screen displayed at the predetermined timing. (Configuration 4) The image forming apparatus according to Configuration 3, wherein the UI screen is a pop-up window. (Configuration 5) A creating means for creating a counter for each function whose use is restricted or prohibited by the contract information, with the counter having an upper limit corresponding to the contract information; a counting unit that, when a function whose use is restricted by the contract information is used in a job, counts up the count number of the counter for the function used in the job, 5. The image forming apparatus according to any one of configurations 1 to 4, wherein the accepting unit recognizes the predetermined timing by making a determination using the count number of the counter and an upper limit number. (Configuration 6) The image forming apparatus according to Configuration 5, wherein the reception means recognizes, as the predetermined timing, a time when it is determined that the count number of the counter is equal to an upper limit number before the job is executed. (Configuration 7) The image forming apparatus according to configuration 5 or 6, wherein the reception means recognizes the predetermined timing as a time when it is determined, before the job is executed, that the count number of the counter will be equal to or greater than an upper limit number when the job is executed. (Configuration 8) The image forming apparatus according to any one of configurations 5 to 7, wherein the reception means recognizes the predetermined timing as the time when it is determined that the count number of the counter has reached an upper limit during execution of the job. (Configuration 9) The image forming apparatus according to any one of configurations 5 to 7, wherein the reception means recognizes the predetermined timing as the time when it is determined that the count number of the counter has reached or exceeded an upper limit number after the job is executed. (Configuration 10) The creation means sets the upper limit number of the counter for the function that is disabled in the contract information as an initial value of the counter, The image forming apparatus according to any one of configurations 5 to 9, wherein the reception unit recognizes, as the predetermined timing, a time when it is determined that the count number and the upper limit number of the counter for the function used in the job are the initial values ​​of the counter before the job is executed. (Configuration 11) An image forming device according to any one of configurations 1 to 10, characterized in that the reception means recognizes the predetermined timing as the pressing of a button to use a function that is disabled in the contract information. (Configuration 12) An image forming device described in any one of configurations 1 to 11, characterized in that the receiving means recognizes the predetermined timing as when a button is pressed to use a function whose use is limited in the contract information and which has been used to the maximum extent. (Configuration 13) The image forming apparatus according to configuration 11 or 12, further comprising a display means for displaying the button in gray. (Configuration 14) The image forming apparatus according to any one of configurations 1 to 13, wherein the function whose use is restricted or prohibited in the contract information is a scan function. (System 1) A system having a server and an image forming apparatus that limits or disables the use of functions according to contract information managed by the server, The server a transmission unit for transmitting the contract information to the image forming device; the image forming apparatus, a receiving means for receiving the contract information from the server; a receiving means for receiving a change to the contract information at a predetermined timing; a transmission means for transmitting the contract information changed by the reception means to the server. (Method 1) A control method for an image forming apparatus that acquires contract information managed by a server and limits or disables use of functions according to the contract information, The method for controlling an image forming apparatus further comprises a receiving step of receiving a change to the contract information at a predetermined timing. (Program 1) A program for causing a computer to execute the means of the image forming apparatus according to any one of configurations 1 to 14. [Explanation of symbols]

[0052] 101 MFP (image forming device) 102 Device Management Server (Server) 103 Service Management Server (Server) 201 CPU (reception method)

Claims

1. An image forming apparatus that acquires contract information managed by a server and limits or disables use of functions according to the contract information, The image forming apparatus further comprises a receiving unit that receives a change to the contract information at a predetermined timing.

2. The image forming apparatus according to claim 1, characterized in that the receiving means recognizes the specified timing as when it determines that the usage of a function whose usage is restricted in the contract information has reached or exceeded the upper limit, or when it determines that the use of a function whose usage is prohibited in the contract information has been instructed.

3. 2. The image forming apparatus according to claim 1, wherein the accepting unit accepts the change of the contract information on a UI screen displayed at the predetermined timing.

4. 4. The image forming apparatus according to claim 3, wherein the UI screen is a pop-up window.

5. a creation means for creating a counter for each function whose use is restricted or prohibited by the contract information, the counter having an upper limit corresponding to the contract information; a counting unit that, when a function whose use is restricted by the contract information is used in a job, counts up the count number of the counter for the function used in the job, 2. The image forming apparatus according to claim 1, wherein the accepting unit recognizes the predetermined timing by making a determination using the count number of the counter and an upper limit number.

6. 6. The image forming apparatus according to claim 5, wherein the reception unit recognizes, as the predetermined timing, a time when it is determined that the count number of the counter is equal to an upper limit number before the job is executed.

7. 6. The image forming apparatus according to claim 5, wherein the reception unit recognizes, before the job is executed, a time when it is determined that the count number of the counter will be equal to or greater than an upper limit number when the job is executed, as the predetermined timing.

8. 6. The image forming apparatus according to claim 5, wherein the reception unit recognizes, as the predetermined timing, a time when it is determined that the count number of the counter has reached an upper limit during execution of the job.

9. 6. The image forming apparatus according to claim 5, wherein the reception unit recognizes, as the predetermined timing, a time when it is determined that the count number of the counter has reached an upper limit number after the job has been executed.

10. the creation means sets the upper limit number of the counter for the function that is disabled in the contract information as the initial value of the counter; The image forming apparatus according to claim 5, characterized in that the reception unit recognizes the predetermined timing as a time when, before the job is executed, it is determined that the count number and upper limit number of the counter for the function used in the job are the initial values ​​of the counter.

11. 2. The image forming apparatus according to claim 1, wherein the accepting unit recognizes, as the predetermined timing, when a button for using a function that is disabled in the contract information is pressed.

12. The image forming apparatus according to claim 1, wherein the reception means recognizes the predetermined timing as the pressing of a button to use a function whose use is limited in the contract information and which has been used up to its upper limit.

13. 13. The image forming apparatus according to claim 11, further comprising a display unit that displays the button in gray.

14. A system including a server and an image forming apparatus that limits or disables use of functions according to contract information managed by the server, The server a transmission unit for transmitting the contract information to the image forming device; the image forming apparatus, a receiving means for receiving the contract information from the server; a receiving means for receiving a change to the contract information at a predetermined timing; a transmission means for transmitting the contract information changed by the reception means to the server.

15. A control method for an image forming apparatus, which acquires contract information managed by a server, and limits or disables use of a function according to the contract information, The method for controlling an image forming apparatus further comprises a receiving step of receiving a change to the contract information at a predetermined timing.

16. 2. A program for causing a computer to execute the means of the image forming apparatus according to claim 1.

Images