Systems, printers, management servers, methods for controlling them, and programs.

Abstract

Conventional technologies could not automatically adjust the connection time of the always-on connection according to the user's service contract status or printer usage, making it difficult to reduce the load on the server from the always-on connection as needed. [Solution] When the printer 200 requests printer registration from the printer management server 100 via HTTP (S401), the printer management server 100 performs the registration (S411). Also, when the printer 200 requests the printer management server 100 to obtain permanent connection information via HTTP (S402), the printer management server 100 determines the permanent connection maintenance time according to the elapsed time since printer registration (S413) and responds to the printer 200 (S416). The printer 200 establishes a permanent connection with the printer management server 100 via MQTT (S404), and disconnects the permanent connection when the permanent connection maintenance time has elapsed since the permanent connection was established (S406).

Description

Technical Field

[0001] The present invention relates to a system, a printer, a management server, their control methods, and a program.

Background Art

[0002] In recent years, a flat-rate printing service has been widely provided to users who use printers. The flat-rate printing service, also called a subscription service, is a service that can be subscribed to for each printer.

[0003] Generally, when using a flat-rate printing service, many users contract for the flat-rate printing service after purchasing a printer. After the contract, the printer management server notifies the printer of the contract information, and upon receiving the notification of the contract information, the printer operates for the flat-rate printing service. Also, when changing or canceling the contract of the flat-rate printing service, in many cases, the behavior of the printer is changed when the printer receives the notification of the contract change / cancellation information from the printer management server.

[0004] In order for the printer to receive notifications from the printer management server described above, the printer is always connected to the printer management server using a protocol such as MQTT (Message Queueing Telemetry Transport). The always-on connection between the printer and the printer management server leads to an increase in the load on the printer management server as the number of connected printers increases and as the connection maintenance time per printer increases. In particular, for a service such as a flat-rate printing service where contracts, contract changes, and cancellations are not frequently performed and it is unknown when they will be performed, continuously maintaining an always-on connection leads to an increase in the load on the printer management server.

[0005] As a technology for optimizing the connection maintenance time of an always-on connection, there is the technology of Patent Document 1. Patent Document 1 discloses a technology for connecting and disconnecting a constant connection based on pre-set schedule information. [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Japanese Patent Publication No. 2018-190169 [Overview of the project] [Problems that the invention aims to solve]

[0007] However, the technology described in Patent Document 1 connects and disconnects the always-on connection based on pre-set schedule information, so it does not automatically adjust the connection time according to the user's service contract status or printer usage status, making it difficult to reduce the load on the server from the always-on connection as needed.

[0008] This invention was made to solve the above-mentioned problems. The purpose of this invention is to provide a mechanism that can automatically adjust the duration of the always-on connection according to the user's service contract status and printer usage status, thereby reducing the load on the server's always-on connection. [Means for solving the problem]

[0009] The present invention relates to a system in which a printer and a management server that manages the printer can communicate, wherein the printer has request means for requesting the management server to register the printer by communication using a first communication method, connection means for establishing a permanent connection with the management server using a second communication method different from the first communication method, acquisition means for obtaining a maintenance time that indicates the time for which the permanent connection should be maintained from the management server by communication using the first communication method, and disconnection means for disconnecting the permanent connection when the maintenance time has elapsed since the permanent connection was established, wherein the management server has registration means for registering the printer in response to a registration request sent from the printer by the first communication method, first determination means for determining the maintenance time according to the elapsed time since the printer was registered with the registration means, and first transmission means for transmitting the maintenance time to the printer by the first communication method, wherein the first determination means makes the determination to shorten the maintenance time according to the elapsed time. [Effects of the Invention]

[0010] According to the present invention, the duration of the always-on connection can be automatically adjusted according to the user's service contract status and printer usage, thereby reducing the load on the server's always-on connection. [Brief explanation of the drawing]

[0011] [Figure 1] A diagram illustrating the overall configuration of the flat-rate printing service system according to this embodiment. [Figure 2] This diagram illustrates the schematic configuration of the printer management server and service server in this embodiment. [Figure 3] A diagram illustrating the schematic configuration of the printer according to this embodiment. [Figure 4] A sequence diagram illustrating the process from when the printer maintains a constant connection with the printer management server until the connection is terminated, according to the first embodiment. [Figure 5] A flowchart illustrating the calculation process for always-on connection and always-on connection maintenance time in the first embodiment. [Figure 6] Sequence diagram illustrating the process of updating the duration of maintaining a constant connection to the printer during registration of the fixed-rate printing service in the second embodiment. [Figure 7] Sequence diagram illustrating the process from printing log transmission to disconnection of the constant connection in the third embodiment. [Figure 8] Flowchart illustrating the calculation process of the constant connection extension time in the third embodiment. [Figure 9] Flowchart illustrating the calculation process of the constant connection extension time in the fourth embodiment. [Figure 10] Sequence diagram illustrating the process of updating the duration of maintaining a constant connection to the printer during registration / cancellation of the cloud print service in the fifth embodiment. [Figure 11] Flowchart illustrating the calculation process of the constant connection and the duration of maintaining a constant connection during registration of the fixed-rate printing service in the fifth embodiment. [Figure 12] Flowchart illustrating the calculation process of the constant connection and the duration of maintaining a constant connection in the fifth embodiment.

Embodiments for Carrying Out the Invention

[0012] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. 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 present invention according to the claims, and not all combinations of the features described in the present embodiments are essential for the solution means of the present invention.

[0013] 〔First Embodiment〕 In this embodiment, an example of a system is shown in which a printer, a service server, and a printer management server cooperate to provide a fixed-rate printing service to a user, and the duration of maintaining a constant connection is automatically adjusted according to the contract status of the user's fixed-rate printing service and the usage status of the printer.

[0014] Hereinafter, the configuration of the flat-rate printing service system in the present embodiment will be described with reference to FIG. 1. FIG. 1 is a diagram illustrating the overall configuration of a flat-rate printing service system according to an embodiment of the present invention. As shown in FIG. 1, the flat-rate printing service system in the present embodiment includes a printer management server 100, a service server 300, and a printer 200.

[0015] The network 1000 is a network that communicably connects the service server 300, the printer management server 100, and the printer 200. The network 1000 is, for example, a communication network realized by the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), a telephone line, a dedicated digital line, an ATM or frame relay line, a cable TV line, a wireless line for data broadcasting, or the like. The network 1000 may be of any type as long as data transmission and reception between each component are possible. The network 1000 may be wired or wireless. In the present embodiment, the network 1000 will be described as the Internet.

[0016] The service server 300 is a server on which an application program (hereinafter referred to as an "application") that provides services to users operates. The service server 300 provides a function for registering a flat-rate printing service such as a website to a user and accepts registration of a flat-rate printing service from the user.

[0017] The service server 300 includes a database. The database of the service server 300 stores various information for providing a flat-rate printing service to users, including contract information of the flat-rate printing service of the user and a list of models targeted for the flat-rate printing service. The service server 300 transmits registration, change, and cancellation of contract information of the flat-rate printing service to the printer management server 100 via the network 1000, and receives operation information such as a printing log of the printer 200 from the printer management server 100 to provide a flat-rate printing service to the user.

[0018] The printer management server 100 is connected to the printer 200 via the network 1000 and receives event information such as errors and alerts sent from the printer 200, as well as print logs. In this embodiment, it is explained that communication using the HTTP (Hyper Text Transfer Protocol) protocol is used for receiving these, but it is not limited to communication using the HTTP protocol, and other protocols may be used.

[0019] Furthermore, the printer management server 100 is also connected to the printer 200 via network 1000 for always-on communication, and notifies the printer 200 of contract information for the flat-rate printing service. In this embodiment, for example, MQTT (Message Queueing Telemetry Transport protocol) is used for always-on communication, but the communication protocol for always-on communication is not limited to the MQTT protocol and may be other protocols.

[0020] The printer management server 100 has a database. The database of the printer management server 100 records connection information for the printer 200 to connect to the printer management server 100, the connection history of the printer 200 to the printer management server 100, and the service registration status such as the contract information for the printer 200's flat-rate printing service.

[0021] The application on the printer management server 100 records the contract information for the flat-rate printing service in the printer management server 100's database based on the receipt of the flat-rate printing service registration request from the service server 300. Furthermore, the application on the printer management server 100 generates notification data for the flat-rate printing service contract information and notifies the printer 200 via the network 1000 using always-on communication. In addition, the application on the printer management server 100 also notifies the printer 200 via the network 1000, using always-on communication, of instructions to change the setting values ​​that the printer 200 uses to maintain its always-on connection.

[0022] Printer 200 is a printer that can be used both when the user does not have a contract with a flat-rate printing service provider, and when the user has a contract with a flat-rate printing service provider.

[0023] In the following, the state in which a user uses the service without entering into a contract with a flat-rate printing service provider will be referred to as "normal use," and the state in which a user uses the service after entering into a contract with a flat-rate printing service provider will be referred to as "contracted use."

[0024] A flat-rate printing service is a service that allows users to perform "flat-rate printing," an example of contract printing, for a fixed fee as specified in the contract terms, as long as it is within the usage period and maximum number of prints specified in the contract terms. For example, a flat-rate printing service may provide users with consumables and / or replacement items used for flat-rate printing at a fixed price, as long as it does not exceed the aforementioned usage period and maximum number of prints.

[0025] Furthermore, the printer 200 receives notifications of subscription information for the flat-rate printing service from the printer management server 100 via the network 1000, stores the received subscription information in the storage device 204 shown in Figure 3 (described later), and operates in a subscription usage state. Furthermore, when Printer 200 is in contract usage mode, it may behave differently than when it is in normal usage mode. For example, when Printer 200 is in contract usage mode, it may receive the print limit as part of the contract information for the flat-rate printing service, and if the number of pages Printer 200 prints for the current month exceeds the print limit, it may become unable to print.

[0026] Furthermore, the printer 200 receives notifications from the printer management server 100 regarding changes to the settings used to maintain a constant connection via the network 1000 using the HTTP protocol, and updates the settings related to the constant connection with the printer management server 100 (constant connection using the MQTT protocol) via the network 1000.

[0027] In Figure 1, for the sake of simplicity in explaining this embodiment, each component is shown as a single unit; however, there is no intention to limit or restrict the number of units in the configuration. Each component may be composed of one or more units.

[0028] Figure 2 is a diagram illustrating the schematic configuration of the printer management server 100 and the service server 300. The CPU101 is a central processing unit for controlling the following components. The disk device 102 stores applications 111, databases 112, the OS (Operating System), and various other files that are read by the CPU 101. The disk device 102 is composed of, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), or an eMMC (embedded MultiMediaCard).

[0029] The external storage disk reader 103 is a device for reading information such as files stored on an external storage medium, such as an SD card. Memory 104 consists of RAM and other components, and the CPU 101 performs temporary data storage and buffering as needed.

[0030] The display unit 105 is composed of, for example, an LCD (Liquid Crystal Display) and displays various types of information. The control unit 106 consists of a keyboard, mouse, and other devices for the user to perform various input operations. Furthermore, a configuration without a display unit 105 or an operation unit 106 is also acceptable.

[0031] The communication unit 107 is an interface to which LAN cables, etc., are connected, and is connected to a network such as network 1000 via a router, etc. (not shown), and performs various types of communication. The communication unit 107 is an interface that supports wired LAN and wireless LAN. The aforementioned parts 102 to 106 are interconnected by bus 108, enabling them to send and receive data to and from each other.

[0032] The service server 300 may have a different hardware configuration from the printer management server 100. Furthermore, while this example shows the printer management server 100 and service server 300 each consisting of a single server (information processing device), they may also consist of multiple servers. In other words, each function may be executed by multiple servers working in cooperation. For example, the printer management server 100 and service server 300 may be configured using cloud computing technology. In this embodiment, a configuration consisting of one or more servers is referred to as a server system.

[0033] Figure 3 is a diagram illustrating the schematic configuration of printer 200. The CPU 201 performs calculations, decisions, and controls on data and instructions according to the programs stored in the RAM 202 and ROM 203. RAM202 is used as temporary storage when CPU201 performs various processing tasks. ROM203 stores the OS and other application software. Alternatively, ROM203 may be a non-volatile memory that allows data to be rewritten, such as flash memory.

[0034] The communication unit 205 is an interface to which a LAN cable is connected, and is connected to a network such as network 1000 via a router (not shown), and performs data communication with the printer management server 100. This data communication may be performed wirelessly, for example, by using a wireless-compatible interface.

[0035] The display unit 208 is composed of, for example, an LCD and displays various types of information. The control unit 207 consists of buttons, a touch panel, and other elements for the user to perform various input operations. The printing unit 206 implements the printing function.

[0036] The printing unit 206 records (i.e., prints) an image onto a recording medium such as printing paper, for example, using an inkjet method, based on image data received from an external source or image data stored in the storage device 204. The printing method of the printing unit 206 is not limited to an inkjet method, but may also be an electrophotographic method, a dye-sublimation method, or other printing methods.

[0037] The system bus 209 handles data exchange between the CPU 201, RAM 202, ROM 203, communication unit 205, printing unit 206, display unit 208, operation unit 207, etc. The communication processing of the printer 200 is achieved by the CPU 201 reading and executing the program necessary for processing and controlling the communication unit 205.

[0038] In service subscriptions such as flat-rate printing services, the probability of subscribing to the service may decrease over time after the initial printer setup. Therefore, an example of reducing redundant constant connections by shortening the duration of the printer's always-on connection as time passes after the initial setup is explained below using Figure 4.

[0039] Figure 4 is a sequence diagram illustrating the process in the first embodiment, from when the printer 200 establishes a permanent connection with the printer management server 100 until when the permanent connection is terminated. In the sequence shown in Figure 4, the printer 200 processes by having the CPU 201 load a program stored in a computer-readable location in the ROM 203 or the like into the RAM 202 and execute it. The printer management server 100 processes by having the CPU 101 of the printer management server 100 load a program stored in a computer-readable location in the disk drive 102 or the like into the memory 104 and execute it.

[0040] This sequence is performed during the initial setup and when the network is reconnected, such as when the printer 200 is powered on or soft-off. However, the device information registration request shown in S401 is a process that is executed only during the initial setup, and is not performed when the printer 200 is powered on or soft-offed, or when the network is reconnected after the initial setup. Therefore, when the printer 200 is powered on or soft-offed after the initial setup and the network is reconnected, the process in S401 is skipped, and processing starts from S402.

[0041] In S401, the CPU 201 of the printer 200 sends device information, including the printer 200's identification information (e.g., serial number) and model information, to the printer management server 100 as a registration request using the HTTP protocol. Upon receiving this registration request, the CPU 101 of the printer management server 100 proceeds to process S411.

[0042] In S411, the CPU 101 of the printer management server 100 stores (registers) the printer 200's identification information, model information, and the date and time the processing was performed as the device information registration date and time, associating them with the database 112 of the printer management server 100. Furthermore, in S412, the CPU 101 of the printer management server 100 sends a registration completion response (HTTP response) to the printer 200. Upon receiving this registration completion response, the CPU 201 of printer 200 proceeds to process S402.

[0043] In S402, the CPU 201 of printer 200 sends a request to the printer management server 100 using the HTTP protocol to obtain permanent connection information, which includes the identification information of printer 200 in the data to be sent. Upon receiving this request to acquire always-on connection information, the CPU 101 of the printer management server 100 proceeds to process S413.

[0044] In S413, the CPU 101 of the printer management server 100 generates a permanent connection ID that uniquely identifies the printer 200. Furthermore, the CPU 101 of the printer management server 100 generates authentication information required when a connection request is made. Then, in S414, the CPU 101 of the printer management server 100 associates the identification information of the printer 200 with the permanent connection ID and authentication information generated in S413 and registers it in the database 112 of the printer management server 100. Note that the generation of the permanent connection ID and authentication information and the association process are performed only on the first call.

[0045] Next, in S415, the CPU 101 of the printer management server 100 performs the calculation process for always-on connection and always-on connection maintenance time shown in Figure 5, which will be described later, and obtains the always-on connection and always-on connection maintenance time. The always-on connection and always-on connection maintenance time include the setting value for whether or not to perform an always-on connection (ON or OFF), and the time to maintain the always-on connection when always-on connection = ON.

[0046] Subsequently, in S416, the CPU 101 of the printer management server 100 sends a response to the printer 200 containing the always-on connection ID, authentication information, and always-on connection information including the always-on connection and the always-on connection maintenance time (HTTP response). Upon receiving this response, the CPU 201 of printer 200 proceeds to process S403.

[0047] In S403, the CPU 201 of printer 200 stores the permanent connection information received as the above response in ROM 203. In S404, the CPU 201 of the printer 200 reads the always-on connection information from the ROM 203. If always-on connection is ON, it requests an always-on connection from the printer management server 100 and establishes an always-on connection between the printer 200 and the printer management server 100 using the MQTT protocol. If always-on connection is OFF, the CPU 201 of the printer 200 does not request an always-on connection from the printer management server 100 and terminates processing. After the permanent connection is established, in S405, the CPU 201 of the printer 200 starts counting the connection time for the permanent connection.

[0048] After establishing a permanent connection with the printer management server 100, the CPU 201 of the printer 200 disconnects the permanent connection with the printer management server 100 in S406 when the connection time of the permanent connection exceeds the permanent connection maintenance time included in the permanent connection information stored in the ROM 203. In other words, the permanent connection is disconnected in accordance with the time elapsed since the permanent connection was established.

[0049] Figure 5 is a flowchart illustrating the calculation process for always-on connection and always-on connection maintenance time in the first embodiment. The series of processes shown in the flowchart of Figure 5 are performed by the CPU 101 of the printer management server 100 loading a program stored in the disk device 102, etc., into RAM and executing it.

[0050] In S501, the CPU 101 of the printer management server 100 retrieves a list of printers eligible for the flat-rate printing service and the model information of the target printer 200 from the database 112 of the printer management server 100, and determines whether the target printer 200 is an eligible printer for the flat-rate printing service.

[0051] If the printer 200 is determined to be not a target model (the result in S501 is NO), the CPU 101 of the printer management server 100 proceeds to S502. In S502, the CPU 101 of the printer management server 100 returns Always-on = OFF, and the processing of this flowchart ends. In this case, it is also acceptable to return Always-on = OFF and Always-on maintenance time = 0.

[0052] On the other hand, if the printer 200 is determined to be a target model (if S501 is YES), the CPU 101 of the printer management server 100 proceeds to S503.

[0053] In S503, the CPU 101 of the printer management server 100 retrieves the contract information for the flat-rate printing service and the device information registration date and time for the target printer 200 from the database 112 of the printer management server 100. The device information registration date and time corresponds to the date and time when the initial setup was performed on the target printer 200, and is registered in the database 112 in S411 of Figure 4 described above. The CPU 101 of the printer management server 100 then uses this information to determine whether or not there is contract information for the flat-rate printing service for the target printer 200, that is, whether or not it is not registered for the flat-rate printing service. In addition, the CPU 101 of the printer management server 100 determines whether or not the difference between the device information registration date and time and the current date and time is within the "initial registration period" (it may also be less than the "initial registration period"). The "initial registration period" is a predetermined period that indicates the period during which registration for the flat-rate printing service is likely to occur immediately after the initial setup of the printer 200. For example, it may be set that the "initial registration period" = 30 days, assuming that registration for the flat-rate printing service is likely to occur for 30 days immediately after the initial setup. However, the "initial registration period" is not limited to 30 days. For example, the "initial registration period" may be configurable by the administrator of the printer management server 100. Alternatively, the printer management server 100 may collect statistics on the time from the initial setup until registration for the flat-rate printing service (this should be configured to be done automatically, but it may also be done manually), and automatically determine the "initial registration period" based on these statistics. For example, the printer management server 100 may be configured to determine and control (automatically update) the "initial registration period" at predetermined intervals (e.g., every three months) based on statistical values ​​(average or median values, etc.) from the initial setup until registration for the flat-rate printing service. Furthermore, the "initial registration period" may differ for each printer model or for each user.

[0054] In S503 above, if the result of both checks is true, that is, if the device is not registered for the flat-rate printing service and the difference between the device information registration date and time and the current date and time is within the "initial registration period" (if YES is found in S503), the CPU 101 of the printer management server 100 proceeds to S504. In S504, the CPU 101 of the printer management server 100 returns Always-on = ON, Always-on maintenance time = "Initial registration maintenance time", and terminates the processing of this flowchart.

[0055] On the other hand, if the result of at least one of the judgments is false, that is, if the device is already registered for the flat-rate printing service, or if the difference between the device information registration date and time and the current date and time is greater than the "initial registration period" (if NO in S503), the CPU 101 of the printer management server 100 proceeds to S506. In S505, the CPU 101 of the printer management server 100 returns "Always connected = ON" and "Always connected maintenance time = "Normal maintenance time", and terminates the processing of this flowchart.

[0056] Note that "Initial Registration Maintenance Time" and "Normal Maintenance Time" are the time the printer maintains a constant connection after it has been established. "Initial Registration Maintenance Time" is the maintenance time for constant connection during the "Initial Registration Period" and should be set to a longer time than "Normal Maintenance Time". For example, "Initial Registration Maintenance Time" could be 1 hour and "Normal Maintenance Time" could be 10 minutes. However, it is not limited to these. As mentioned above, "Initial Registration Maintenance Time" and "Normal Maintenance Time" are pre-set periods. For example, the administrator of the printer management server 100 may be able to set at least one of "Initial Registration Maintenance Time" or "Normal Maintenance Time". Also, at least one of "Initial Registration Maintenance Time" or "Normal Maintenance Time" may have different values ​​for each printer model or for each user.

[0057] As described above, according to the first embodiment, after the initial setup of the printer, it becomes possible to shorten the time the printer maintains a constant connection before registering for a flat-rate printing service, as time passes. For example, after a period of time when the flat-rate printing service is likely to be registered, such as 30 days immediately after the initial setup, the time the printer maintains a constant connection can be shortened compared to before the period when the flat-rate printing service is likely to be registered. Furthermore, even after registering for the flat-rate printing service, it becomes possible to shorten the time the printer maintains a constant connection. Furthermore, it becomes possible to restrict unnecessary always-on connections for models that are not covered by the flat-rate printing service. Furthermore, in this embodiment, the setting is to immediately change the always-on connection duration to the "normal connection duration" after the "initial registration period" has elapsed. However, the always-on connection duration may be shortened gradually over time (or shortened linearly or nonlinearly and continuously over time). In addition, it may be possible to set whether to immediately change the always-on connection duration to the "normal connection duration" after the "initial registration period" has elapsed, or to shorten the always-on connection duration gradually.

[0058] In this way, by shortening the connection duration of the printer's always-on connection and restricting always-on connections for models not covered by the flat-rate printing service, it becomes possible to reduce unnecessary always-on connections. As a result, the connection duration of always-on connections can be dynamically adjusted according to the user's service contract status and printer usage, and the load on the server's always-on connection can be appropriately reduced. Thus, according to this embodiment, the always-on connection duration between the printer and the management server in the printer management infrastructure can be optimized, thereby reducing the load on the management server.

[0059] [Second Embodiment] In the first embodiment, an example of optimizing the always-on connection duration during the period immediately after a user purchases a printer, when they are likely to subscribe to a flat-rate printing service, and during periods when they are not. In the first embodiment, the always-on connection duration of the printer 200 is updated when the network is reconnected after registration for the flat-rate printing service, such as when the power is turned on or the software is turned off. Until the network is reconnected, the always-on connection duration of the printer 200 is the "initial registration period". In the second embodiment, the printer management server 100 is configured to notify the printer 200 of the change in the always-on connection duration in response to the printer 200 being registered for the flat-rate printing service. This will be explained in detail below. In this embodiment, explanations of content common to the first embodiment will be omitted as appropriate, and the differences from the first embodiment will be mainly explained.

[0060] Figure 6 is a sequence diagram illustrating the process of updating the constant connection maintenance time to the printer 200 when registering for a fixed-rate printing service in the second embodiment. This makes it possible to shorten the constant connection maintenance time of the printer 200 when registering for a fixed-rate printing service. In the series of processes shown in the sequence of Figure 6, the printer 200 processes by having the CPU 201 load a program stored in a computer-readable location in the ROM 203 or the like into the RAM 202 and execute it. The printer management server 100 processes by having the CPU 101 of the printer management server 100 load a program stored in a computer-readable location in the disk device 102 or the like into the memory 104 and execute it. The service server 300 processes by having the CPU 101 of the service server 300 load a program stored in a computer-readable location in the disk device 102 or the like into the memory 104 and execute it.

[0061] In S601, the CPU 101 of the service server 300, upon receiving a registration from a user for a flat-rate printing service for the target printer 200, sends a flat-rate printing service registration request to the printer management server 100, which includes the identification information of the printer 200 that has been registered for the flat-rate printing service and the flat-rate printing service contract information.

[0062] Upon receiving a flat-rate printing service registration request (printer 200 identification information and flat-rate printing service contract information) from the service server 300, the CPU 101 of the printer management server 100 proceeds to process S611. In S611, the CPU 101 of the printer management server 100 links the identification information of the printer 200 received as a flat-rate printing service registration request with the flat-rate printing service contract information and saves (registers) it in the database 112 of the printer management server 100.

[0063] Next, in S612, the CPU 101 of the printer management server 100 notifies the printer 200 via the always-on connection of always-on connection maintenance information, which is set to always-on connection = ON and always-on connection maintenance time = "normal maintenance time", as well as the flat-rate printing service contract information. Upon receiving this notification, the CPU 201 of printer 200 proceeds to process S621.

[0064] In S621, the CPU 201 of printer 200 overwrites and saves the received constant connection maintenance information (constant connection = ON, constant connection maintenance time = "normal maintenance time") and the flat-rate printing service contract information to ROM 203. As a result, the printer 200 operates in contract usage mode. Then, when the continuous connection time of the printer 200 exceeds the continuous connection maintenance time (i.e., "normal maintenance time") included in the continuous connection maintenance information stored in the ROM 203, the CPU 201 of the printer 200 sends a request to disconnect the continuous connection to the printer management server 100 (S406 in Figure 4).

[0065] As described above, according to the second embodiment, even if a flat-rate printing service is registered during the "initial registration period," it becomes possible to notify the printer 200 of the constant connection maintenance information immediately after the registration of the flat-rate printing service. In response to this notification, the printer 200 can change the constant connection maintenance time, shortening the constant connection maintenance time and further reducing unnecessary constant connections.

[0066] [Third Embodiment] In the second embodiment, the time the printer 200 maintains a constant connection is shortened after registration for the flat-rate printing service. Therefore, it is possible that the printer 200 may have difficulty receiving notifications from the printer management server 100 when it tries to receive notifications regarding changes or cancellations of the flat-rate printing service contract. Thus, in the third embodiment, a configuration is described in which the printer 200 extends the time it maintains a constant connection after printing following registration for the flat-rate printing service. This will be explained in detail below. Note that in this embodiment, explanations of content common to the second embodiment will be omitted as appropriate, and the differences from the second embodiment will be explained mainly.

[0067] The following description, using Figure 7, explains how the printer 200 in the third embodiment extends the always-on connection time after printing following registration for the flat-rate printing service. Figure 7 is a sequence diagram illustrating the process from print log transmission to permanent connection disconnection in the third embodiment. In the series of processes shown in the sequence of Figure 7, the printer 200 processes by having the CPU 201 load a program stored in a computer-readable location in the ROM 203 or the like into the RAM 202 and execute it. The printer management server 100 processes by having the CPU 101 of the printer management server 100 load a program stored in a computer-readable location in the disk device 102 or the like into the memory 104 and execute it. The service server 300 processes by having the CPU 101 of the service server 300 load a program stored in a computer-readable location in the disk device 102 or the like into the memory 104 and execute it.

[0068] After completing the printing process, the CPU 201 of printer 200 proceeds to process S701. In S701, the CPU 201 of printer 200 sends a print log to the printer management server 100. The print log includes at least the identification information of printer 200 and the number of pages printed during the printing process. The CPU 101 of the printer management server 100 performs the S711 and S712 processes in response to the receipt of the print log.

[0069] In S711, the CPU 101 of the printer management server 100 retrieves the number of printed pages from the received print log, associates the number of printed pages with the printer 200's identification information and date and time, and saves (registers) it in the database 112 of the printer management server 100. In addition, in S712, the CPU 101 of the printer management server 100 sends print logs to the service server 300. Note that the execution order of S711 and S712 does not matter.

[0070] Furthermore, in S713, the CPU 101 of the printer management server 100 performs the calculation process for the continuous connection extension time, as shown in Figure 8, which will be described later. Then, in S714, the CPU 101 of the printer management server 100 responds to the printer 200 with the continuous connection extension time calculated in S704 (HTTP response).

[0071] Here, the calculation process for the continuous connection extension time in S713 described above will be explained using Figure 8. Figure 8 is a flowchart showing an example of the calculation process for the continuous connection extension time in the third embodiment. The series of processes shown in the flowchart of Figure 8 are performed by the CPU 101 of the printer management server 100, which loads the program code stored in the disk device or the like into RAM and executes it.

[0072] In S801, the CPU 101 of the printer management server 100 determines whether or not there is a flat-rate printing service contract information linked to the identification information of the printer 200 in the database 112 of the printer management server 100.

[0073] If it is determined that there is no subscription information for the flat-rate printing service, meaning the user is not registered for the flat-rate printing service (indicated as NO in S801), the CPU 101 of the printer management server 100 proceeds to process S802. In S802, the CPU 101 of the printer management server 100 terminates the processing of this flowchart by setting the continuous connection extension time to 0.

[0074] On the other hand, if it is determined that there is a subscription information for a flat-rate printing service, that is, that the user is registered for the flat-rate printing service (if S801 is YES), the CPU 101 of the printer management server 100 proceeds to process S803. In S803, the CPU 101 of the printer management server 100 terminates the processing of this flowchart, setting the always-on connection extension time to "extension time when flat-rate service is registered".

[0075] The "extended connection time for registered flat-rate services" is the time during which the always-on connection is extended so that the printer 200 can receive notifications from the printer management server 100 via the always-on connection. For example, this can be a period of one hour. However, the "extended connection time for registered flat-rate services" is not limited to one hour. For example, the "extended connection time for registered flat-rate services" may be configurable by the administrator of the printer management server 100. Furthermore, the printer management server 100 may actually collect statistics on the time from the receipt of print logs to the change or cancellation of the flat-rate printing service contract (or until the notification of the flat-rate printing service contract information associated with such a change or cancellation) (this should be configured to automatically process the statistics, but it may also be done manually), and automatically determine the "extended connection time for registered flat-rate services" based on the results of these statistics. For example, the printer management server 100 may be configured to determine and control (automatically update) the "extended time for registered flat-rate printing service" at predetermined intervals (e.g., every three months) based on a statistical value (such as an average or median) of the time from receiving the print log to changing or canceling the flat-rate printing service contract (or until notification of the flat-rate printing service contract information related to such change or cancellation). Furthermore, the "extended time for registered flat-rate printing service" may be a different value for each printer model or each user.

[0076] Now, let's return to the explanation of Figure 7. When the CPU 201 of printer 200 receives a response to the print log sent in S701 (i.e., the continuous connection extension time in S714), it proceeds to process S702. In S702, the CPU 201 of printer 200 determines whether a permanent connection has been established with printer management server 100.

[0077] If it is determined that a permanent connection has not yet been established (if the answer is NO in S702), the CPU 201 of the printer 200 requests a permanent connection from the printer management server 100 in S703, and establishes a permanent connection between the printer 200 and the printer management server 100 using the MQTT protocol. After a permanent connection is established, the CPU 201 of printer 200 in S704 starts counting the connection time for the permanent connection.

[0078] On the other hand, if S702 determines that a permanent connection has been established (if S702 is YES), the CPU 201 of the printer 200 skips the processes in S703 and S704.

[0079] The CPU 201 of printer 200 proceeds to process S705 when the connection time for the always-on connection exceeds the time of the always-on connection maintenance period plus the always-on connection extension period. In S705, the CPU 201 of printer 200 disconnects its permanent connection to the printer management server 100.

[0080] As described above, according to the third embodiment, after registering for the flat-rate printing service, it becomes possible to extend the always-on connection in accordance with the user's printing. This makes it easier for the printer 200 to receive notifications of contract changes or cancellations for the flat-rate printing service from the printer management server 100 via the always-on connection.

[0081] Furthermore, if the number of pages printed by printer 200 has reached the maximum print limit and printing is restricted, the printer management server 100 may send the print log with the number of pages printed set to 0 in S701 of Figure 7 without actually printing. Upon receiving a print log with a print count of 0, the printer management server 100 may perform only the calculation process for the continuous connection extension time in S713 (Figure 8) and respond to printer 200 with the continuous connection extension time. Furthermore, in this embodiment, the continuous connection extension time was passed to the printer 200 in the print log response, but it may also be passed at another time, for example, by notifying the printer 200 via the continuous connection, starting from the printer management server 100.

[0082] In the above explanation, after registering for the flat-rate printing service, the printer 200 sent a print log to the printer management server 100 via the HTTP protocol in response to printing by the user. The printer management server 100, upon receiving this print log, calculated the continuous connection extension time, responded to the printer 200 with the continuous connection extension time, and extended the continuous connection time on the printer 200. However, the system may also be configured such that the printer 200 sends notifications via the HTTP protocol to the printer management server 100 due to other uses of the printer 200, and upon receiving these notifications, the printer management server 100 calculates the continuous connection extension time, responds to the printer 200 with the continuous connection extension time, and extends the continuous connection time on the printer 200.

[0083] [Fourth Embodiment] Generally, in flat-rate printing services, if the number of pages printed by printer 200 this month is close to the print limit, users are likely to change their flat-rate printing service contract to relax the print limit. Therefore, in the fourth embodiment, when the number of pages printed by printer 200 this month is close to the print limit, a configuration is described in which the constant connection maintenance time is extended to a longer period, making it easier to receive notifications of contract changes for flat-rate printing services via constant connection communication. In this embodiment, explanations of aspects common to the third embodiment will be omitted as appropriate, and the differences from the third embodiment will be explained primarily.

[0084] Figure 9 is a flowchart of the calculation process for the continuous connection extension time in the fourth embodiment. The series of processes shown in the flowchart of Figure 9 are performed by the CPU 101 of the printer management server 100, which loads the program code stored in the disk device or the like into RAM and executes it. The same step numbers are used for steps that are the same as in Figure 8, and only steps that are different from those in Figure 8 will be explained.

[0085] In the fourth embodiment, if the answer to S802 is YES, the CPU 101 of the printer management server 100 proceeds to S901. In S901, the CPU 101 of the printer management server 100 retrieves the current month's print count for printer 200 and the print limit, which is the contract information for the flat-rate printing service, from the database 112 of the printer management server 100. It then determines whether the difference between the print limit and this month's print count is less than (or less than or equal to) the "print count nearing the limit". The "print count nearing the limit" is a reference value that indicates how close this month's print count is to the contracted print limit. It may be a fixed value or a percentage, such as 10% of the print limit. Furthermore, the "print count nearing the limit" may differ for each printer model or for each user.

[0086] If the difference between the maximum number of prints and the number of prints for this month is determined to be greater than or equal to the "number of prints approaching the limit" (i.e., NO in S901), the CPU 101 of the printer management server 100 proceeds to process S803.

[0087] On the other hand, if the difference between the maximum number of prints and the number of prints for this month is determined to be less than the "number of prints nearing the limit" (if S901 is YES), the CPU 101 of the printer management server 100 proceeds to S902. In S902, the CPU 101 of the printer management server 100 terminates processing with the continuous connection extension time = "extension time when the number of printed pages is approaching the limit".

[0088] In other words, in this embodiment, if the difference between the number of pages printed by the printer 200 during a predetermined period and the maximum number of pages for the fixed-rate printing service during a predetermined period is greater than the number of pages nearing the limit, the always-on connection extension time is set to "extension time when service registration is complete". If the difference is less than the number of pages nearing the limit, the always-on connection extension time is set to "extension time when the number of printed pages nearing the limit is reached".

[0089] Furthermore, the "extension time when the number of printed pages is nearing the limit" should be set to a longer period than the "extension time when the service is registered." For example, if the "extension time when the service is registered" is 1 hour, the "extension time when the number of printed pages is nearing the limit" may be set to 2 hours. However, the "extension time when the number of printed pages is nearing the limit" is not limited to this. For example, the "extension time when the number of printed pages is nearing the limit" may be set by the administrator of the printer management server 100. In addition, the printer management server 100 may collect statistics on the time from when the difference between the print limit and the number of printed pages for the current month falls below the "number of pages nearing the limit" until a contract change for the flat-rate printing service that increases the print limit is made (or until notification of the flat-rate printing service contract information accompanying that contract change) (this should be configured to perform statistical processing automatically, but it may also be done manually), and the "extension time when the number of printed pages is nearing the limit" may be automatically determined according to the statistical results. For example, the printer management server 100 may be configured to determine and control (automatically update) the "extension time when the print limit is approaching" at predetermined intervals (e.g., every three months) based on the above statistics (such as the average or median value). Furthermore, the "extension time when the print limit is approaching" may be a different value for each printer model or user.

[0090] As described above, according to the fourth embodiment, when the number of pages printed this month is close to the print limit, the connection maintenance time for the always-on connection can be extended to a longer period. This makes it easier for the printer 200 to receive notifications from the printer management server 100 regarding changes in the print limit and the flat-rate printing service contract information via the always-on connection.

[0091] [Fifth Embodiment] If the target printer 200 is subscribed not only to a flat-rate printing service but also to a service that requires a constant connection and frequently uses notifications for that connection, it is desirable to maintain a constant connection at all times. Therefore, in the fifth embodiment, an example of a configuration in which the printer 200 maintains a constant connection at all times when the printer 200 is registered to multiple services with different constant connection policies, and one of them has a connection policy that requires a constant connection. As an example of a service that requires a constant connection and frequently uses notifications for that connection, a cloud printing service that supports push printing will be used in the explanation, but it is not limited to this.

[0092] In this embodiment, explanations of aspects common to the third embodiment will be omitted as appropriate, and the differences from the third embodiment will be described primarily. In this embodiment, in addition to the configuration of the third embodiment, the database 112 of the service server 300 further stores various information for providing cloud printing services to users, such as registration information for the cloud print service. Furthermore, the application 111 of the service server 300 has the function of sending print requests to the printer management server 100 via the network 1000.

[0093] Furthermore, in this embodiment, in addition to the configuration of the third embodiment, the printer management server 100 further notifies the printer 200 of print jobs and other information via a constant connection. The database 112 of the printer management server 100 further stores print job information of the printer 200 and the registration status of the cloud print service. Furthermore, the application 111 of the printer management server 100 generates job data based on the print request received from the service server 300 and sends a job notification to the printer 200 via the network 1000 with a constant connection.

[0094] Furthermore, in this embodiment, in addition to the configuration of the third embodiment, the printer 200 receives job notifications from the printer management server 100 via the network 1000, and uses the job data access information included in the job notification to receive job data from the printer management server 100 via the network 1000. Furthermore, the printing unit 206 of the printer 200 processes the job data received by the communication unit 205 as described above and executes printing. The storage device 204 of the printer 200 also stores the job data.

[0095] Furthermore, the CPU 101 of the printer management server 100 shall call the process shown in Figure 12 as the calculation process for the always-on connection and the always-on connection maintenance time in S415 of Figure 4.

[0096] Figure 12 is a flowchart of the calculation process for always-on connection and always-on connection maintenance time in the fifth embodiment. The series of processes shown in the flowchart of Figure 12 are performed by the CPU 101 of the printer management server 100, which loads program code stored in a disk device or the like into RAM and executes it.

[0097] In S1201, the CPU 101 of the printer management server 100 retrieves the service registration status of the target printer 200 from the database 112 of the printer management server 100 and determines whether it is registered with the cloud print service.

[0098] If it is determined that the target printer 200 is not registered with the cloud print service (the answer in S1201 is NO), the CPU 101 of the printer management server 100 proceeds to S1202. In S1202, the CPU 101 of the printer management server 100 calls the calculation process for always-on connection and always-on connection duration shown in Figure 5, obtains the always-on connection and always-on connection duration, returns them as return values, and terminates the process in this flowchart.

[0099] On the other hand, if it is determined in S1201 that the target printer 200 is already registered with the cloud print service (if the answer in S1201 is YES), the CPU 101 of the printer management server 100 proceeds to S1203. In S1203, the CPU 101 of the printer management server 100 returns "Always connected = ON" and "Always connected duration = "Infinite", retrieves the Always connected status and Always connected duration as return values, and returns them, thus terminating the processing of this flowchart.

[0100] In other words, when the target printer 200 is registered with the cloud print service, the continuous connection maintenance time is set to the time during which the continuous connection will not be interrupted, regardless of the elapsed time since the continuous connection was established. Note that here, "infinite" is indicated as the time during which the continuous connection will not be interrupted, but it is not limited to this, as long as it is a sufficiently large time (for example, a time equivalent to the lifespan of the printer) that the continuous connection will not be interrupted in reality.

[0101] The continuous connection and continuous connection maintenance time calculated as described above are sent from the printer management server 100 to the printer 200 in S416 of Figure 4. Upon receiving this continuous connection and continuous connection maintenance time, the printer 200, which is registered with the cloud print service, saves the continuous connection maintenance time = "infinite" in the ROM 203 and operates accordingly thereafter. As a result, the printer 200, which is registered with the cloud print service, does not have the continuous connection maintenance time expired and does not disconnect the continuous connection (S406 of Figure 4). In other words, the continuous connection is maintained.

[0102] Furthermore, in S612 of Figure 6, the CPU 101 of the printer management server 100 acquires the fixed-rate printing service contract information and the always-on connection maintenance information, and notifies the printer 200 of the always-on connection maintenance information and the fixed-rate printing service contract information. In this embodiment, the acquisition of the always-on connection maintenance information is performed as follows. That is, the CPU 101 of the printer management server 100 acquires the cloud service registration information of the target printer 200 from the database 112 of the printer management server 100, and then acquires the always-on connection maintenance information according to the process shown in Figure 11.

[0103] Figure 11 is a flowchart showing an example of the calculation process for always-on connection and always-on connection maintenance time when registering for a flat-rate printing service in the fifth embodiment. The series of processes shown in the flowchart of Figure 11 are performed by the CPU 101 of the printer management server 100, which loads program code stored in a disk device or the like into RAM and executes it.

[0104] In S1101, the CPU 101 of the printer management server 100 determines whether the target printer 200 is registered with the cloud print service.

[0105] If it is determined that the target printer 200 is not registered with the cloud print service (the answer in S1101 is NO), the CPU 101 of the printer management server 100 proceeds to S1102. In S1102, the CPU 101 of the printer management server 100 sets the always-on connection and always-on connection maintenance time to "normal maintenance time" and terminates the processing of this flowchart.

[0106] On the other hand, if it is determined in S1101 that the target printer 200 is already registered with the cloud print service (if the answer in S1101 is YES), the CPU 101 of the printer management server 100 proceeds to S1103. In S1103, the CPU 101 of the printer management server 100 sets the always-on connection and always-on connection duration to "infinite" and terminates the processing of this flowchart. In this embodiment, at S612 in Figure 6, the printer 200, having received the information "Always-on" and "Always-on maintenance time" as always-on connection maintenance information, will not have the always-on connection maintenance time expire. Therefore, even after sending the print log, the printer will not disconnect the always-on connection (S705 in Figure 5). In other words, the always-on connection will be maintained.

[0107] Next, we will explain the process for changing the connection duration of the printer 200 when registering for or canceling the cloud print service in the fifth embodiment. Figure 10 is a sequence diagram showing an example of the process for updating the constant connection maintenance time to the printer 200 when registering for or canceling the cloud print service in the fifth embodiment. This makes it possible to shorten the constant connection maintenance time of the printer 200 when registering for the flat-rate printing service. In the series of processes shown in the sequence of Figure 6, the printer 200 processes by having the CPU 201 load a program stored in a computer-readable location in the ROM 203 or the like into the RAM 202 and execute it. The printer management server 100 processes by having the CPU 101 of the printer management server 100 load a program stored in a computer-readable location in the disk device 102 or the like into the memory 104 and execute it. The service server 300 processes by having the CPU 101 of the service server 300 load a program stored in a computer-readable location in the disk device 102 or the like into the memory 104 and execute it.

[0108] The CPU 101 of the service server 300 executes the S1001 process in response to receiving a user's request to register or unregister (cancel) the cloud print service for the target printer 200. In S1001, the CPU 101 of the service server 300 sends a cloud print service registration request to the printer management server 100 if it has received a cloud print service registration request, and a cloud print service cancellation request if it has received a cloud print service cancellation request. The cloud print service registration request includes the identification information of the printer 200 and the cloud print service registration information, while the cloud print service cancellation request includes the identification information of the printer 200.

[0109] When the printer management server 100 receives a cloud print service registration request or a cloud print service cancellation request, it proceeds to process S1011. In S1011, if the request received from the service server 300 is a cloud print service registration request, the CPU 101 of the printer management server 100 associates the received printer 200 identification information with the cloud print service registration information and stores it in the database 112 of the printer management server 100. On the other hand, if the request received from the service server 300 is a cloud print service cancellation request, the CPU 101 deletes the cloud print service registration information associated with the received printer 200 identification information from the database 112 of the printer management server 100.

[0110] Next, in S1012, the CPU 101 of the printer management server 100 calls the calculation process for always-on connection and always-on connection maintenance time shown in Figure 12, and obtains the always-on connection and always-on connection maintenance time. Furthermore, in S1013, the CPU 101 of the printer management server 100 notifies the printer 200 of the always-on connection and the always-on connection maintenance time acquired in S1012 as always-on connection maintenance information using always-on connection communication. Upon receiving this notification, the CPU 201 of printer 200 proceeds to process S1021.

[0111] In S1021, the CPU 201 of the printer 200 stores the received constant connection maintenance information in the ROM 203. As a result, if printer 200 is registered for the cloud print service, it will have an "unlimited" connection. If the cloud print service is canceled, the connection will be maintained according to the always-on connection policy of the flat-rate printing service.

[0112] As described above, according to the fifth embodiment, if the printer is registered with multiple services, including a cloud print service where notifications for always-on connections are frequently used and it is preferable to always maintain an always-on connection, and a flat-rate printing service where notifications for always-on connections are made but not frequently, the printer will always maintain an always-on connection. As a result, if the printer 200 is registered with multiple services with different always-on connection policies, and at least one of them has an always-on connection policy, the printer 200 will maintain an always-on connection.

[0113] As described above, according to each embodiment, the duration of the always-on connection can be automatically adjusted according to the user's service contract status and printer usage status, thereby reducing the load on the printer management server's always-on connection.

[0114] It should be noted that the structure and content of the various data described above are not limited to those mentioned, and it goes without saying that they can be composed of various structures and contents depending on the use and purpose. Although one embodiment has been described above, the present invention can take the form of, for example, a system, apparatus, method, program, or storage medium. Specifically, it may be applied to a system consisting of multiple devices, or to an apparatus consisting of a single device. Furthermore, any configurations combining the above embodiments are also included in the present invention.

[0115] [Other Embodiments] The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions. Furthermore, the present invention may be applied to a system consisting of multiple devices or to a device consisting of a single device. The present invention is not limited to the embodiments described above, and various modifications (including organic combinations of each embodiment) are possible based on the spirit of the invention, and these are not excluded from the scope of the invention. That is, all configurations that combine the above-described embodiments and their modified forms are included in the present invention.

[0116] This embodiment includes the following configurations, methods, and programs. (Composition 1) A system in which a printer and a management server that manages contract information for a predetermined service of the printer can communicate with each other, The aforementioned printer is A request means for requesting the registration of the printer from the management server via communication using the first communication method, Connection means for establishing a permanent connection with the management server using a second communication method different from the first communication method, An acquisition means for obtaining a maintenance time, which indicates the time for which the constant connection will be maintained, from the management server via communication using the first communication method, The system includes a disconnection means for disconnecting the constant connection after the maintenance time has elapsed since the constant connection was established, The aforementioned management server A registration means for registering the printer in response to a registration request transmitted from the printer by the first communication method, A first determination means for determining the maintenance time according to the elapsed time since the printer was registered in the registration means, The system includes a first transmission means that transmits the aforementioned maintenance time to the printer using the first communication method, The system is characterized in that the first determination means makes the determination to shorten the maintenance time according to the elapsed time. (Configuration 2) The first determination means determines the maintenance time to be a first hour if the elapsed time is shorter than a predetermined time, and determines the maintenance time to be a second hour which is shorter than the first hour if the elapsed time is longer than a predetermined time. The system according to configuration 1, characterized by the features described above. (Composition 3) The first determination means further determines the first instruction indicating whether or not to perform the always-on connection to be an instruction to perform the always-on connection depending on whether the printer is a model compatible with the service, and determines the instruction not to perform the always-on connection depending on whether the printer is a model compatible with the service. The first transmission means further transmits the first instruction to the printer. The acquisition means further acquires the first instruction from the management server, The connection means establishes the constant connection when the first instruction is an instruction to perform the constant connection, and does not perform the constant connection when the first instruction is an instruction not to perform the constant connection. The system according to configuration 1 or 2, characterized by the above. (Composition 4) The aforementioned management server The system includes a first notification means that, upon registration of the printer with the service, sends a first notification to the printer stating that the maintenance time is the second time. The aforementioned printer is The system has a modification means for changing the maintenance time to the second time based on the notification received from the management server, in response to receiving the first notification from the management server. The system according to configuration 2, characterized by the features described above. (Composition 5) The aforementioned printer is The first communication method includes a second transmission means for sending a notification to the management server regarding the use of the printer, The aforementioned management server A second determination means that receives a notification from the printer via the first communication method regarding the use of the printer and determines an extension period to extend the maintenance time, depending on whether the printer is registered with the service, The system includes a third transmission means that transmits a second instruction to the printer via the first communication method, instructing an extension of the maintenance time based on the aforementioned extension time. When the disconnection means receives the second instruction from the management server by the first communication method, it extends the maintenance time based on the second instruction and disconnects the constant connection when the extended maintenance time has elapsed since the constant connection was established. A system according to any one of configurations 1 to 4, characterized by the features described above. (Composition 6) The system according to configuration 5, characterized in that the transmission of notifications resulting from the use of the aforementioned printer includes the transmission of a print log. (Composition 7) The second determination means determines the extension time to be a first extension time if the difference between the number of pages printed by the printer during a predetermined period and the upper limit of the number of pages printed in the service during the predetermined period is greater than a predetermined number, and determines the extension time to be a second extension time which is longer than the first extension time if the difference is less than the predetermined number. The system according to configuration 5 or 6, characterized by the above. (Composition 8) The first determination means, when the printer is registered with another service that requires a constant connection different from the service, determines the maintenance time to a third time during which the disconnection means does not disconnect the connection, regardless of the elapsed time. The aforementioned management server A third determination means that determines the maintenance time to the second time in response to the printer being registered with the other service, and determines the maintenance time to the third time in response to the printer being unregistered from the other service, The system includes a second notification means for notifying the printer of the maintenance time determined by the third determination means, The aforementioned printer is The system has a second modification means that changes the maintenance time based on the notification received from the management server via the second notification means, The system according to configuration 2, characterized by the features described above. (Composition 9) The system according to configuration 8, characterized in that the aforementioned other service is a service for receiving notification of print jobs from the management server via the always-on connection and performing printing. (Composition 10) A printer capable of communicating with a management server that manages contract information for a specified service, A request means for requesting the registration of the printer from the management server via communication using the first communication method, Connection means for establishing a permanent connection with the management server using a second communication method different from the first communication method, An acquisition means for obtaining a maintenance time, which indicates the time for which the constant connection will be maintained, from the management server via communication using the first communication method, A disconnection means for disconnecting the constant connection in accordance with the elapsed time since the constant connection was established, A printer characterized by having the following features. (Composition 11) A management server that manages contract information for a printer's specified services, A registration means for registering the printer in response to a registration request transmitted from the printer by a first communication method, A determination means for determining a maintenance time that instructs the duration for which a continuous connection between the printer and the management server is maintained using a second communication method different from the first communication method, based on the elapsed time since the printer was registered in the registration means. The system includes a transmission means for transmitting the aforementioned maintenance time to the printer by the first communication method, A management server characterized in that, with respect to the printer, the constant connection is disconnected when the maintenance time has elapsed since the constant connection was established. (Method 1) A control method for a system in which a printer and a management server that manages contract information for a predetermined service of the printer can communicate, The printer performs the following: A request step of requesting the management server to register the printer by communication using the first communication method, A maintenance time, which indicates the time for which a continuous connection with the management server is maintained using a second communication method different from the first communication method, is obtained from the management server via communication using the first communication method. The connection process for establishing the aforementioned permanent connection, The system includes a disconnection step, which disconnects the constant connection after the maintenance time has elapsed since the constant connection was established. The following is executed by the aforementioned management server: A registration step in which the printer is registered in response to a registration request transmitted from the printer by the first communication method, A determination step in which the printer determines the maintenance time according to the elapsed time since registration, The process includes a transmission step of transmitting the aforementioned maintenance time to the printer using the first communication method, A system control method characterized in that, in the decision step, the decision is made to shorten the maintenance time according to the elapsed time. (Method 2) A method for controlling a printer that can communicate with a management server that manages contract information for a specified service, A request step of requesting the management server to register the printer by communication using the first communication method, A maintenance time, which indicates the time for which a continuous connection with the management server is maintained using a second communication method different from the first communication method, is obtained from the management server via communication using the first communication method. The connection process for establishing the aforementioned permanent connection, A disconnection step is performed to disconnect the constant connection in accordance with the elapsed time since the constant connection was established, A printer control method characterized by having the following features. (Method 3) A method for controlling a management server that manages contract information for a printer's specified services, A registration step in which the printer is registered in response to a registration request transmitted from the printer by the first communication method, A determination step that determines a maintenance time which instructs the duration for which a continuous connection between the printer and the management server is maintained using a second communication method different from the first communication method, based on the elapsed time since the printer was registered in the registration step, The process includes a transmission step of transmitting the aforementioned maintenance time to the printer using the first communication method, A control method for a management server, characterized in that the constant connection is disconnected in the printer after the maintenance time has elapsed since the constant connection was established. (Program 1) A program that causes a computer to perform the control method described in Method 2. (Program 2) A program to cause a computer to perform the control method described in Method 3.

Claims

1. A system in which a printer and a management server that manages contract information for a predetermined service of the printer can communicate with each other, The aforementioned printer is A request means for requesting the registration of the printer from the management server via communication using the first communication method, Connection means for establishing a permanent connection with the management server using a second communication method different from the first communication method, An acquisition means for obtaining a maintenance time, which indicates the time for which the constant connection will be maintained, from the management server via communication using the first communication method, The system includes a disconnection means for disconnecting the constant connection after the maintenance time has elapsed since the constant connection was established, The aforementioned management server A registration means for registering the printer in response to a registration request transmitted from the printer by the first communication method, A first determination means for determining the maintenance time according to the elapsed time since the printer was registered in the registration means, The system includes a first transmission means for transmitting the aforementioned maintenance time to the printer using the first communication method, The system is characterized in that the first determination means makes the determination to shorten the maintenance time according to the elapsed time.

2. The first determination means determines the maintenance time to be a first hour if the elapsed time is shorter than a predetermined time, and determines the maintenance time to be a second hour which is shorter than the first hour if the elapsed time is longer than a predetermined time. The system according to feature 1.

3. The first determination means further determines the first instruction indicating whether or not to perform the always-on connection to be an instruction to perform the always-on connection depending on whether the printer is a model compatible with the service, and determines the instruction not to perform the always-on connection depending on whether the printer is a model compatible with the service. The first transmission means further transmits the first instruction to the printer. The acquisition means further acquires the first instruction from the management server, The connection means establishes the constant connection when the first instruction is an instruction to perform the constant connection, and does not perform the constant connection when the first instruction is an instruction not to perform the constant connection. The system according to feature 1.

4. The aforementioned management server The printer has a first notification means that, upon registration of the printer with the service, sends a first notification to the printer stating that the maintenance time is the second time. The aforementioned printer is The system has a modification means for changing the maintenance time to a second time based on the notification received from the management server. The system according to feature 2.

5. The aforementioned printer is The first communication method includes a second transmission means for sending a notification to the management server regarding the use of the printer, The aforementioned management server A second determination means that receives a notification from the printer via the first communication method regarding the use of the printer and determines an extension period to extend the maintenance time, depending on whether the printer is registered with the service, The system includes a third transmission means that transmits a second instruction to the printer, based on the aforementioned extension time, to extend the maintenance time, via the first communication method. When the disconnection means receives the second instruction from the management server by the first communication method, it extends the maintenance time based on the second instruction and disconnects the permanent connection when the extended maintenance time has elapsed since the permanent connection was established. The system according to any one of claims 1 to 3.

6. The system according to claim 5, characterized in that the transmission of notifications resulting from the use of the aforementioned printer includes the transmission of a print log.

7. The second determination means determines the extension time to be a first extension time if the difference between the number of pages printed by the printer during a predetermined period and the upper limit of the number of pages printed in the service during the predetermined period is greater than a predetermined number, and determines the extension time to be a second extension time which is longer than the first extension time if the difference is less than the predetermined number. The system according to claim 5, characterized in that it is the same as described in claim 5.

8. The first determination means, when the printer is registered with another service that requires a constant connection different from the service, determines the maintenance time to a third time during which the disconnection means does not disconnect the connection, regardless of the elapsed time. The aforementioned management server A third determination means that determines the maintenance time to the second time in response to the printer being registered with the other service, and determines the maintenance time to the third time in response to the printer being unregistered from the other service, The system includes a second notification means for notifying the printer of the maintenance time determined by the third determination means, The aforementioned printer is The system has a second modification means that changes the maintenance time based on the notification received from the management server by the second notification means, The system according to feature 2.

9. The system according to claim 8, characterized in that the aforementioned other service is a service for receiving notification of a print job from the management server via the always-on connection and performing printing.

10. A printer capable of communicating with a management server that manages contract information for a specified service, A request means for requesting the registration of the printer from the management server via communication using the first communication method, Connection means for establishing a permanent connection with the management server using a second communication method different from the first communication method, An acquisition means for obtaining a maintenance time, which indicates the time for which the constant connection will be maintained, from the management server via communication using the first communication method, A disconnection means for disconnecting the constant connection in accordance with the elapsed time since the constant connection was established, A printer characterized by having the following features.

11. A management server that manages contract information for a printer's specified services, A registration means for registering the printer in response to a registration request transmitted from the printer by a first communication method, A determination means for determining a maintenance time that instructs the duration for which a continuous connection between the printer and the management server is maintained using a second communication method different from the first communication method, based on the elapsed time since the printer was registered in the registration means. The system includes a transmission means for transmitting the aforementioned maintenance time to the printer by the first communication method, A management server characterized in that, with respect to the printer, the constant connection is disconnected when the maintenance time has elapsed since the constant connection was established.

12. A control method for a system in which a printer and a management server that manages contract information for a predetermined service of the printer can communicate, The printer performs the following: A request step of requesting the registration of the printer to the management server by communication using the first communication method, A maintenance time, which indicates the time for which a continuous connection with the management server is maintained using a second communication method different from the first communication method, is obtained from the management server via communication using the first communication method. The connection process for establishing the aforementioned permanent connection, The system includes a disconnection step, which disconnects the constant connection after the maintenance time has elapsed since the constant connection was established. The following is executed by the aforementioned management server: A registration step in which the printer is registered in response to a registration request transmitted from the printer by the first communication method, A determination step in which the printer determines the maintenance time according to the elapsed time since registration, The transmission step includes transmitting the aforementioned maintenance time to the printer using the first communication method, A system control method characterized in that, in the decision step, the decision is made to shorten the maintenance time according to the elapsed time.

13. A method for controlling a printer that can communicate with a management server that manages contract information for a specified service, A request step of requesting the registration of the printer to the management server by communication using the first communication method, A maintenance time, which indicates the time for which a continuous connection with the management server is maintained using a second communication method different from the first communication method, is obtained from the management server via communication using the first communication method. The connection process for establishing the aforementioned permanent connection, A disconnection step is performed to disconnect the constant connection in accordance with the elapsed time since the constant connection was established, A printer control method characterized by having the following features.

14. A method for controlling a management server that manages contract information for a printer's specified services, A registration step in which the printer is registered in response to a registration request transmitted from the printer by a first communication method, A determination step that determines a maintenance time which instructs the duration for which a continuous connection between the printer and the management server is maintained using a second communication method different from the first communication method, based on the elapsed time since the printer was registered in the registration step, The transmission step includes transmitting the aforementioned maintenance time to the printer using the first communication method, A control method for a management server, characterized in that the constant connection is disconnected in the printer after the maintenance time has elapsed since the constant connection was established.

15. A program for causing a computer to execute the control method described in claim 13.

16. A program for causing a computer to execute the control method described in claim 14.

Images