Management server, control method of management server and program

Abstract

To solve such a problem that, during a subscription contract, a printer cannot be used since exchangeable ink runs out until delivery resumes when such a situation that delivery of dedicated ink stops for a certain period of time occurs due to issues such as physical distribution issues in a case where an image formation apparatus can only use the delivered ink.SOLUTION: A management server which is communicably connected to an image formation apparatus via a network and manages contract information for delivery service of consumable supplies, comprises: detection means which detects a state change in the service; and setting means which extracts the contract information corresponding to the state change in the service when the detection means detects the state change in the service, and updates the state of the service to the extracted contract information.SELECTED DRAWING: Figure 8A

Description

[Technical field]

[0001] The present invention relates to a management server, a control method for the management server, and a program. [Background technology]

[0002] In image forming devices equipped with network capabilities, various services such as defect analysis and billing systems are being developed by transmitting device information and user usage history to a management server. For example, in order to reduce the management costs of consumables such as ink, a management server manages the consumables and automatically delivers them when the remaining amount is low. In recent years, with the introduction of subscription contracts, a business model in which ink, which is a consumable, is provided to users who subscribe to the service at a fixed price has become widespread. In order to realize such a flat-rate service of managing and automatically delivering ink, the image forming device needs to transmit ink information to a server, and the management server needs to manage the ink information and determine whether to deliver a replacement ink. For example, Patent Document 1 proposes an ink management system that uses individual identification information for each ink to manage the prevention of multiple deliveries on the server side. In order to prevent multiple deliveries of ink, the image forming device is required to measure and transmit usage information of delivered ink independently. A simple configuration for realizing this is, for example, a configuration in which the image forming device is allowed to use only delivered ink and restricts the use of other commercially available inks during the flat-rate service contract. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-54155 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, such a configuration poses a problem if the delivery of the special ink is suspended for a certain period of time due to some reason such as a logistics problem. In a configuration in which only the special ink can be used during the contract, if the special ink is used up, there will be no ink to replace it until delivery resumes, and the user will be unable to use the printer. SUMMARY OF THE PRESENT DISCLOSURE In order to solve the above problems, it is an object of the present invention to provide a means for lifting the restrictions in a printing system that restricts the use of ink other than that delivered exclusively during a fixed-price service contract, depending on the service situation, such as a delivery problem. [Means for solving the problem]

[0005] The present invention is a management server that is communicatively connected to an image forming device via a network and manages contract information for a consumable delivery service, characterized in that the management server has a detection means for detecting a change in the status of the service, and a setting means for, when the detection means detects a change in the status of the service, extracting contract information corresponding to the change in the status of the service and updating the status of the service in the extracted contract information. Effect of the Invention

[0006] In a service management system that restricts the use of ink other than that for exclusive delivery during a fixed-price service contract, it is possible to provide a means for lifting the restriction depending on the service status. [Brief description of the drawings]

[0007] [Figure 1] Overall configuration diagram of a service management system according to an embodiment [Diagram 2] FIG. 1 is a block diagram showing a hardware configuration of a printer according to an embodiment of the present invention. [Diagram 3] FIG. 1 is a block diagram showing a hardware configuration of a service management server according to an embodiment. [Figure 4] FIG. 1 is a block diagram showing a hardware configuration of a device management server according to an embodiment. [Diagram 5]Sequence diagram from system service contract to printer control start [Figure 6] Flowchart showing printer control after contract information is acquired [Figure 7] Example of contract information held by the device management server [Figure 8A] Flowchart on the server side when a delivery problem occurs and is restored [Figure 8B] Flowchart for the printer when a delivery problem occurs and is then restored [Figure 9] Example of user notification using the main unit display DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the present invention, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the present invention.

[0009] [Embodiment 1] Overall configuration of the service management system FIG. 1 is a diagram showing the overall configuration of a service management system according to the present embodiment. This management system is configured by connecting a printer 100, which is an image forming apparatus, a device management server 200, and a service management server 300 via a communication network 400 such as the Internet. The printer 100 records the contract information in the NVM 104 of the printer 100, which will be described later, and controls the printer 100 according to the recorded contract information. The printer 100 receives the contract information by communicating with the device management server 200 via the communication network 400. The device management server 200 holds the contract information notified by the service management server 300, and provides the contract information to the printer 100 based on the contract information. The communication between the printer 100, the device management server 200, and the service management server 300 uses a communication protocol such as Hypertext Transfer Protocol (hereinafter referred to as "HTTP"), and the control method thereof is a known method. Also, although the device management server 200 is interposed between the printer 100 and the service management server 300, the present embodiment is not limited to this. For example, the printer 100 and the service management server 300 may directly exchange contract information via the Internet. Details of the contract information and the control of the printer 100 according to the contract information will be described later.

[0010] Printer hardware configuration FIG. 2 is a block diagram showing the hardware configuration of the printer 100. As shown in FIG. The printer 100 includes a CPU 101 , a ROM 102 , a RAM 103 , an NVM 104 , a network connection unit 105 , a display unit 106 , and an operation unit 107 . The CPU 101 is a central processing unit for controlling each section within the printer 100 . The ROM 102 stores various program codes. When each service is executed, data such as image data is temporarily stored or buffered in the RAM 103. The RAM 103 also stores image data received by a network connection unit 105, which will be described later. NVM 104 is a non-volatile memory and stores non-volatile information. For example, NVM 104 stores individual identification information of printer 100, shipping destination information, language settings to be displayed on display unit 106, etc. In printer 100 of this embodiment, contract information for each service, which will be described later, is also stored in NVM 104. The network connection unit 105 connects to an external device via a USB or a communication network 400. In this embodiment, the printer 100 uses the network connection unit 105 to communicate with the device management server 200 via the communication network 400. The display unit 106 is configured, for example, by a liquid crystal display, and is capable of displaying characters, figures, indicators, and the like. The display unit 106 is not limited to a liquid crystal display, and can also be configured using LEDs or other displays. Information displayed by the display unit 106 includes, for example, setting information for the printer 100, and information about the ink contained in each ink tank (remaining ink amount), and the like. The driving of the display unit 106 is controlled by the CPU 101. The operation unit 107 is made up of switches, hard keys, etc., for the user to perform various input operations. It is also possible to configure the display unit 106 to function as an operation unit for performing input operations, such as a touch panel.

[0011] The printer 100 also has a scanner unit 108 , a printer unit 109 , an ink tank unit 110 , a waste ink tank unit 111 , and a paper cassette unit 112 . Scanner unit 108 optically reads an original placed on a platen and converts it into electronic data, and further converts the image data into a specified file format and transmits the converted image data to an external device via communication network 400 or stores it in a storage area such as a hard disk (not shown). Printer 100 also has a copy function, which is realized by scanning an original placed on a platen with scanner unit 108 and transferring the generated image data to printer unit 109, which then records an image on a recording medium based on the image data. In printer 100, the scanner function is realized by scanner unit 108, and the print function is realized by printer unit 109. Printer unit 109 receives ink from ink tank unit 110 and performs printing on a recording medium such as printing paper. Printer unit 109 also prints an image on a recording medium by inkjet printing based on image data received from the outside, image data read by scanner unit 108, etc. Note that the printing method of printer unit 109 is not limited to inkjet printing, and may be other printing methods such as electrophotography. An ink cartridge 113 filled with ink is attached to the ink tank section 110, and the ink in this ink cartridge is supplied to the printer section 109 for printing. The ink cartridge 113 includes a memory 114. Information on the type of ink cartridge is stored in memory 114, and information on the type of the installed ink cartridge is transmitted to printer unit 109. This allows printer unit 109 to determine the type of the installed ink cartridge, specifically whether it is ink for a fixed-rate service or not. As another possible configuration, printer 100 may include a carriage that scans printer unit 109 over the recording medium, and the carriage with the ink cartridge installed constitutes the ink tank unit in this embodiment. As another possible configuration for ink tank unit 110, the ink tank unit 110 may include an ink inlet, and ink may be stored by injecting ink from an ink bottle.

[0012] The waste ink tank unit 111 stores waste ink generated when the printer unit 109 performs printing processing using ink supplied from the ink tank unit 110. Waste ink refers to ink that is used for purposes other than ejection onto a recording medium, such as ink suction performed before ink is ejected onto a recording medium in order to stabilize ink ejection. Status information indicating the remaining capacity of the waste ink tank unit 111 is calculated based on the amount of waste ink used by the printer unit 109 outside the recording medium and the capacity of the waste ink tank unit 111. In this case, the calculation result of the remaining capacity may be corrected by mounting a sensor that detects the amount of waste ink in the waste ink tank unit 111, or the remaining capacity that can be stored in the waste ink tank unit 111 may be calculated using only the sensor. Paper cassette unit 112 stores recording media such as print paper to be supplied to printer unit 109. Printer unit 109 prints on the supplied paper to form an image. Paper information such as the number of remaining sheets in paper cassette unit 112 is calculated based on the number of sheets supplied to printer unit 109 and the number of sheets stored in paper cassette unit 112. Note that a sensor that detects the number of sheets stored in paper cassette unit 112 may be installed to correct the calculation result of the remaining number of sheets, or the remaining number of sheets may be found based only on the sensor result. The various components of the printer 100 are interconnected via a bus 113, enabling them to transmit and receive data to and from each other.

[0013] -Hardware configuration of device management server FIG. 3 is a block diagram showing a schematic hardware configuration of the device management server 200. As shown in FIG. The CPU 201 loads software stored in the ROM 202 or the hard disk 204 into the RAM 203 and executes it to perform processes such as calculations, judgments, and controls of data and instructions. The RAM 203 is used as a temporary storage area when the CPU 201 performs various processes. The ROM 202 and hard disk 204 record an operating system (OS), application software, programs, etc. The hard disk 204 also records device information for each printer, which will be described later, and a record table of the contract status of each service. A system bus 206 transmits and receives data between the CPU 201 and information storage devices such as a ROM 202, a RAM 203, and a hard disk 204. Furthermore, the network connection unit 205 uses a wireless LAN or a wired LAN that complies with standards such as IEEE802.11a, and transmits and receives data to and from devices on the same network or the Internet using protocols such as TCP / IP.

[0014] Service Management Server Hardware Configuration FIG. 4 is a block diagram showing the hardware configuration of the service management server 300. As shown in FIG. As in FIG. 3, a CPU 301 is made up of a ROM 302, a RAM 303, a hard disk 304, a network connection unit 305, and a system bus 306, and each module is also the same as in FIG. 3, so a description thereof will be omitted. 3 and 4, a configuration in which separate dedicated servers are provided may be used to realize the services that the device management server 200 or the service management server 300 can provide. Also, the device management server 200 and the service management server 300 do not have to be configured as a single server each. In other words, the functions provided by the device management server 200 and the service management server 300 may be realized by a server system consisting of three or more servers or a single server that aggregates all of the servers.

[0015] - Sequence from signing a contract for a service to starting printer control according to the contract information FIG. 5 illustrates the sequence from when a service contract is made to when printer control starts in accordance with the contract information, using an example of a flat-rate ink usage service. First, in S501, a user 500 makes a contract for a service on the service management system. When the user 500 makes a contract for the service, the service management server 300 performs a service registration process in S502 to link the user information with the printer to be registered. When the service registration process is completed, the printer 100 registered in S502 is delivered to the user 500 in S503. In S504, the user 500 who has received the printer 100 starts the initial setup of the printer 100. In S505, the printer 100 proceeds with the initial installation process in accordance with instructions from the user 500, and performs initial settings such as network settings for connecting to the Internet. When the printer 100 completes the network connection in the initial settings, in S506 it transmits a device registration request to the device management server 200 together with identification information such as the product serial number of the printer. In step S507, the device management server 200 that has received the device registration request performs registration processing based on the identification information received from the printer. When the registration processing is completed, the device management server 200 returns the registration result to the printer 100. Next, in S508, the device management server 200 notifies the service management server 300 of the completion of device registration. This notification of the completion of device registration to the service management server 300 may be configured to be sent to multiple service management servers 300 for each service. In S509, the service management server 300 receives a device registration completion notification from the device management server 200, and notifies the device management server 200 of the contract information of the associated service based on the device identifier of the printer 100 received at that time. The device management server 200 stores the contract information notified by the service management server 300 therein. In S510, the printer 100 requests the device management server 200 to acquire contract information. This contract information acquisition request is an HTTP client communication, and at least the device identifier information of the printer 100 is included in the communication. When the device management server 200 receives a request for contract information from the printer 100 in S510, the device management server 200 notifies the printer 100 of the contract information corresponding to the transmitted device identifier in an HTTP response. In S511, the printer 100 receives the contract information from the device management server 200, stores the notified contract information in the printer 100, and reflects control according to the contract information in subsequent printer control. 5, the contract information is acquired in S510 after the device registration process, but the contract information acquisition process may be performed at any time other than this timing.Specific examples include communication every time the network is connected, communication every time a certain period of time has elapsed, etc.

[0016] - Switching to contracted services on the printer The flow chart of Fig. 6 will explain the control of the printer after the contract information is acquired in S510 of Fig. 5. Here, an ink delivery service will be explained as an example of a flat-rate service. This process is realized by the CPU 101 of the printer 100 expanding a program on the RAM 103 and executing it. In S601, the printer 100 receives contract information from the device management server 200. In S602, the CPU 101 checks whether or not the service contract is made based on the received contract information. If the service contract is made (Yes in S602), the CPU 101 advances the process to S603, and if the service contract is not made (No in S602), the CPU 101 advances the process to S605. If the service contract is in progress, in step S603, the CPU 101 changes the printer control to that for a flat-rate service user. The control for flat-rate service users will be explained with a concrete example. Until the contract is confirmed, basic functions such as print, scan, and copy functions are restricted, and after the contract is confirmed, all of these functions become available. In addition, since this is an ink delivery service, the ink consumption of the device is measured. In the next step S604, in order to link the ink consumption amount with delivery, the CPU 101 allows only the delivery ink to be used during the fixed-price service contract, and then ends this process. On the other hand, if the service contract is not in effect, in S605 CPU 101 switches printer control to control when no flat-rate service contract is in effect. As a specific example, when a flat-rate service including the device is cancelled, all basic functions are restricted again and the measurement of ink consumption for the delivery service is stopped. The ink usage restrictions may or may not be lifted. As another example, when a flat-rate contract is cancelled due to a device purchase contract or the like, all basic function restrictions are lifted, but the measurement of ink consumption for the delivery service is stopped. The ink usage restrictions are lifted, and it becomes possible to use other services besides the ink for delivery.

[0017] (Service contract information) Figure 7 is an example of service contract information stored by a device management server for a flat-rate ink delivery service. The service contract information stored by the server has, for each record of a contracting user, at least the "contract device identifier" and the "contract status" of the flat-rate service, as well as the "delivery area" of the ink delivery service and the "state of the delivery service" of that contract. Specific examples of the state of the delivery service may include states that indicate whether or not there is a problem with the logistics system, such as "operating" or "disturbed / stopped." Alternatively, multiple factors, such as ink not being delivered, may be combined to have only two states, indicating whether or not the contracting device is in a state where the ink delivery restriction should be lifted. In addition, when detailed "consumable delivery address" of the ink delivery service and information on the individual contract user are registered in the service registration process (S502) or the like, the device management server may hold basic information on the delivery service contract as contract information. Also, the device management server does not need to respond with all of the contract information it holds when a contract information acquisition request is made from the printer in S510 or the like. For example, when a contract information acquisition request is made with a "contract device identifier" attached, the device management server may be configured to respond with only information on the "contract status" of the flat-rate service and information on the "status of the ink delivery service" from the contract information corresponding to the device identifier.

[0018] - Processing in response to changes in service status on the service management server 8A is a flowchart explaining the server-side control from when the service management server 300 detects a change in the service status to when the ink delivery control of the service contract printer is changed. This process is realized by the CPU 301 of the service management server 300 expanding a program on the RAM 303 and executing it. In S801, the CPU 301 of the service management server 300 detects a change in the state of a flat-rate service set by an administrator or the like. In S802, the CPU 301 extracts the contract that is the subject of the notified state change. In S803, it is determined whether the detected status change is "a status change that requires lifting the restriction on the use of the dedicated ink tank" (delivery service is stopped). If the status change is a status change that requires lifting the restriction (Yes in S803), the CPU 301 proceeds to S804, and if the status change is not a status change that requires lifting the restriction (No in S803), the CPU 301 proceeds to S805. In step S804, the CPU 301 updates the status of the ink delivery service in the extracted contract information to the side that lifts the restriction on the dedicated ink ("suspended"). If the status change does not require lifting the restriction, in step S805, the CPU 301 determines whether the detected status change is "a status change that requires restriction on the use of the dedicated ink tank" (delivery service is in operation). If the situation requires restriction of use of the dedicated ink tank (Yes in S805), the CPU 301 advances the process to S806, and if not (No in S805), the CPU 301 ends this process. In step S806, the CPU 301 updates the status of the delivery service in the extracted contract information to the dedicated ink restriction side ("in operation"), and ends this process. As a specific example, the above flow will be described using an example in which the service status is temporarily changed for an area where delivery is difficult. In S801, for example, a service manager inputs information from the administrator page of the service management server, and the information is detected by the CPU 301. An example of information about a change in the status of a service is a change such as "the delivery service in a specific area A has transitioned from in operation to suspended" due to a cause such as a disaster, and the server specifically detects and recognizes this information about the change in the status of the service. Then, in the contract information extraction in S802, contract information in which the delivery area is the specific area A is extracted from the information held by the device management server. The determination in S803 is made as to whether "transition to a state where delivery service is stopped" is a YES condition. In step S804, if the "state of delivery service" in the contract information specifically indicates a state transition between "operating" and "stopped", the state is updated to "stopped" and the process is terminated. The next example of a status change is when the aforementioned disaster factor is recovered and "the delivery service in specific area A transitions from stopped to operating." Similarly, a status change is detected in S801 due to input from the service manager, etc. Contract information is extracted in S802, a NO determination is made in S803, and a YES condition is set in S805 for "transition of delivery service to operating." In S806, if the "status of delivery service" in the contract information is specifically a status transition between "operating" and "stopped," the status is updated to "operating" and the process ends.

[0019] - Changes in ink phase control with changes in printer service conditions FIG. 8B is a flow chart illustrating the control on the printer side from when the service management server detects a change in the state of the service until when the ink delivery control of the service contract printer is changed. This process is executed by the printer 100 at any given opportunity. First, in S810, the CPU 101 of the printer 100 checks the contract status of the printer 100. Next, in step S811, the CPU 101 of the printer 100 executes confirmation of the contract information of the printer itself with the device management server 300. In S812, the CPU 101 determines whether the contract status (state of the delivery service) of the acquired contract information and the contract information stored in the main body has changed. If the contract status has changed (Yes in S812), CPU 101 advances the process to S813, and if not (No in S812), this process ends. In step S813, the CPU 101 determines whether the contract status is "only dedicated ink is usable." If the contract status is the side that restricts the use of shipping ink only (Yes in S813), CPU 101 proceeds to S814, and if the status is the side that lifts the restriction on shipping ink (No in S813), CPU 101 proceeds to S815. In step S814, the CPU 101 sets the printer control so that only the delivered ink can be used. In step S815, the CPU 101 sets the printer so that it can be controlled for use with items other than the delivered ink. To give a specific example, the device receives contract information for its own device from the device management server, and if the last stored "status of delivery service" was "operating" and is currently "stopped," the ink usage restriction is lifted (S815). This allows the printer to continue to be used by using other inks, such as mass-produced inks, even if delivery ink runs out in the event of a delivery problem. If the last stored "status of delivery service" was "stopped" and is currently "operating," ink usage is restricted to delivery ink only (S814). As a result, after recovery from the delivery problem, the device is controlled in the same way as it was during the original flat-rate service contract.

[0020] Furthermore, when the ink usage restriction is released in S815, information 901 (FIG. 9) may be displayed on the display unit 106 to notify the user that the ink delivery service has been stopped. Furthermore, when the use of ink is restricted to only delivered ink in step S814, information 902 (FIG. 9) may be displayed to notify the user that the ink delivery service has been restored.

[0021] [Embodiment 2] As another embodiment of the present invention, the contract information described in FIG. 7 may have multiple hashtag information as attribute information to which the contract belongs. The hashtag information may be a single or multiple character strings with a region attribute, such as #JP or #kawasaki. The method of extracting the target of the status change notified in S802 is configured to compare the information specifying the target of the status change with the contract information held by the device management server, and extract a contract having tag information corresponding to the target. By adopting such a configuration, it becomes possible to further divide the delivery area held by the device management server and specify a stop, or to collectively specify region information higher than the delivery area.

[0022] [Embodiment 3] As yet another embodiment of this embodiment, the contract information described in Fig. 7 may have organizational container information as attribute information to which a device belongs. The organizational container is information having a hierarchical structure such as [XX Company, YY Division, ZZ Section] in a corporate contract, etc. As a specific example of a method for extracting targets of the status change notified in S802, a form may be adopted in which information specifying the target of the status change is collated with contract information held by the device management server, and a contract having an organizational container corresponding to the target is extracted. More specifically, a use case in which ink delivery to XX Company's YY Division is stopped will be exemplified. The service manager notifies the management server of the stop of delivery to XX Company's YY Division. This can be detected in 901, and in S802, devices contracted by XX Company's YY Division are extracted from the device management server, and the delivery service status for these contracts is set to stopped. This makes it possible to perform operations such as stopping delivery to only one of XX Company's YY Division and YY2 Division that are in the same delivery area. (Other Examples) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) a management server that is communicably connected to the image forming apparatus via a network and that manages contract information for a delivery service of consumables, A detection means for detecting a change in a state of the service; When the detection means detects a change in the state of the service, the detection means extracts contract information corresponding to the change in the state of the service, and updates and sets the state of the service in the extracted contract information. 13. A management server comprising: (Configuration 2) The contract information includes at least identification information of the image forming device, information on the delivery area, and the status of the service. 2. The management server according to configuration 1. (Configuration 3) The contract information further includes information on a delivery address for consumables, The setting means extracts contract information having a delivery address corresponding to the change in the status of the service detected by the detection means, and updates and sets the status of the service in the contract information. 3. The management server according to configuration 2. (Configuration 4) the contract information has a plurality of hashtag information; The setting means extracts contract information having hash tag information corresponding to the change in the status of the service detected by the detection unit, and updates and sets the status of the service in the contract information. 4. The management server according to any one of configurations 1 to 3. (Configuration 5) The contract information includes information about an organization container to which the image forming apparatus belongs, The setting means extracts contract information having information on an organization container corresponding to a change in the status of the service detected by the detection unit, and updates and sets the status of the service in the contract information. 5. The management server according to any one of configurations 1 to 4. (Configuration 6) The consumable is delivery ink exclusively for a fixed-price service, and the status of the service is the status of the delivery service of the ink. 6. The management server according to any one of configurations 1 to 5. (Configuration 7) The server comprises a service management server and a device management server, The device management server stores contract information for delivery services. 7. The management server according to any one of configurations 1 to 6. (Method 1) A method for controlling a management server that is communicably connected to an image forming apparatus via a network and that manages contract information for a delivery service of a consumable product, comprising: a detection step of detecting a change in a state of the service; When a change in the state of the service is detected in the detection step, the method includes a setting step of extracting contract information corresponding to the change in the state of the service and updating the state of the service in the extracted contract information. A method for controlling a management server, comprising: (Program 1) A program for causing a computer to execute the method for controlling a management server according to the first method. [Explanation of symbols]

[0023] 100 Printers 200 Device Management Server 300 Service Management Server 400 Communication Network 500 users

Claims

1. a management server that is communicably connected via a network to the image forming apparatus controlled based on the received contract information and that manages contract information for a delivery service of consumables, A detection means for detecting a change in a state of the service; When the detection means detects a change in the state of the service, the service management system has a setting means for extracting contract information corresponding to the change in the state of the service and updating the extracted contract information to set the state of the service.

13. A management server comprising:

2. The contract information includes at least identification information of the image forming device, information on the delivery area, and the status of the service.

2. The management server according to claim 1 .

3. The contract information further includes information on a delivery address for consumables, The setting means extracts contract information having a delivery address corresponding to the change in the status of the service detected by the detection means, and updates and sets the status of the service in the contract information.

3. The management server according to claim 2.

4. the contract information has a plurality of hashtag information; The setting means extracts contract information having hash tag information corresponding to the change in the status of the service detected by the detection means, and updates and sets the status of the service in the contract information.

3. The management server according to claim 2.

5. The contract information includes information about an organization container to which the image forming apparatus belongs, The setting means extracts contract information having information on an organization container corresponding to a change in the status of the service detected by the detection means, and updates and sets the status of the service in the contract information.

2. The management server according to claim 1.

6. The consumable is delivery ink exclusively for a fixed-price service, and the status of the service is the status of the delivery service of the ink.

6. The management server according to any one of configurations 1 to 5.

7. The server comprises a service management server and a device management server, The device management server stores contract information for delivery services.

6. The management server according to claim 1,

8. A method for controlling a management server that is communicably connected via a network to an image forming apparatus that is controlled based on received contract information and that manages contract information for a delivery service of a consumable product, comprising: a detection step of detecting a change in a state of the service; When a change in the state of the service is detected in the detection step, the method includes a setting step of extracting contract information corresponding to the change in the state of the service and updating the state of the service in the extracted contract information.

23. A method for controlling a management server comprising:

9. A program for causing a computer to execute the method for controlling a management server according to claim 8.

Images