Repeater with proxy server function, control method therefor, and program

Abstract

To provide a repeater which switches a device registration to a device management service in accordance with a self-monitoring function of a device.SOLUTION: A monitoring apparatus 105 which is a repeater with a proxy server function for repeating a communication between a device management service and a device comprises: a determination section 512 for determining whether or not a device receiving provision of the device management service without utilizing the proxy server function of the repeater includes a self-monitoring function for the device management service; a proxy setting section 511 for performing proxy setting using proxy information of the proxy server function of the repeater to the device in a case where the device includes the self-monitoring function; and a registration section 513 which instructs a registration to the device, to which the proxy setting is performed, for re-registration as a device including the self-monitoring function to the device management service.SELECTED DRAWING: Figure 18

Description

[Technical field]

[0001] The present invention relates to a relay device having a proxy server function, and a control method and program thereof. [Background technology]

[0002] In recent years, various devices are connected to servers and cloud services through a network. There is a mechanism called Internet of Things (IoT) that provides high-value-added services to devices connected to cloud services, etc. through a network. There are two major systems in IoT. The first is a device management system that includes a device management service that manages connected devices, a storage service that manages collected device information, and an authentication and authorization service that has an authentication and authorization function for securely connecting devices to cloud services. The second is a contract service providing system that cooperates with the device management system to provide various services such as device maintenance services and reporting services. Patent Document 1 discloses a system in which a certain device substitutes for another device in the same network and registers the device as a client in an authentication and authorization server.

[0003] As in Patent Document 1, there are several cases where one device controls the registration process on behalf of another device. For example, a monitoring device that centrally manages multiple devices with self-monitoring functions via its own proxy function issues registration instructions to devices with self-monitoring functions under the monitoring device. There are also cases where a monitoring device performs registration on behalf of multiple devices that do not have self-monitoring functions. [Prior art documents] [Patent documents]

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

[0005] However, since the functions that a cloud service can provide to a device with a self-monitoring function are different from those to a device without a self-monitoring function, the cloud service may have different methods of managing and registering each device. In addition, the functions that can be remotely monitored from a monitoring device are generally limited. Therefore, since a device with a self-monitoring function can receive more services, it is preferable for the device to use the self-monitoring function preferentially. In a case where a device without a self-monitoring function becomes a device with a self-monitoring function through a firmware update, when the self-monitoring function is enabled, the cloud service must switch (re-register) the registration of the device.

[0006] An object of the present invention is to provide a relay device that switches device registration to a device management service depending on the self-monitoring function of the device. [Means for solving the problem]

[0007] In order to solve the above problems, the relay device of the present invention is a relay device equipped with a proxy server function that relays communication between a device management service and a device, and has a determination unit that determines whether a device receiving a device management service without using the proxy server function of the relay device has a self-monitoring function for the device management service, a setting unit that, if the device has the self-monitoring function, performs proxy settings in the device using proxy information of the proxy server function of the relay device, and a registration unit that issues a registration instruction to the device for which the proxy settings have been set, causing it to be re-registered in the device management service as a device having a self-monitoring function. Effect of the Invention

[0008] According to the present invention, device registration to a device management service can be switched depending on the self-monitoring function of the device. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an overall configuration of a system that performs device management. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of an image forming apparatus. [Diagram 3] FIG. 2 illustrates an example of a hardware configuration of a monitoring device and a management server. [Figure 4] FIG. 2 illustrates an example of a software configuration of an image forming apparatus. [Diagram 5] FIG. 2 illustrates an example of a software configuration of a monitoring device. [Figure 6] FIG. 11 is a sequence diagram illustrating an example of a registration determination process of the image forming apparatus. [Figure 7] FIG. 11 is a sequence diagram showing an example of a registration process of an image forming apparatus that does not have a self-monitoring function. [Figure 8] 4 is a diagram illustrating an example of a device management information table managed by the monitoring apparatus. [Figure 9] 4A and 4B are diagrams illustrating an example of a device management table and an agent management table managed by a device management server. [Figure 10] 13 is a diagram illustrating an example of a client management table managed by the authentication and authorization server; [Figure 11] 11 is a diagram illustrating an example of a device registration key management table managed by the authentication and authorization server; [Figure 12] 11 is a diagram illustrating an example of an activation code management table managed by the authentication and authorization server. FIG. [Figure 13] 11 is a diagram illustrating an example of a credential management table managed by the authentication and authorization server; [Figure 14] FIG. 11 is a sequence diagram showing an example of a registration process of an image forming apparatus having a self-monitoring function. [Figure 15] 10 is a flowchart illustrating an example of a device registration status confirmation process of the monitoring device. [Figure 16]10 is a flowchart illustrating an example of a re-registration determination process for an image forming apparatus. [Figure 17] 10 is a flowchart illustrating an example of a re-registration determination process for an image forming apparatus. [Figure 18] 10 is a flowchart illustrating an example of a re-registration process of an image forming apparatus. [Figure 19] 13 is a flowchart illustrating an example of a re-registration determination process of an image forming apparatus according to a third embodiment. [Figure 20] FIG. 11 illustrates an example of a monitoring mode management table. [Figure 21] FIG. 13 is a diagram illustrating an example of a monitoring mode setting screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Example 1 1 is a diagram for explaining the overall configuration of a device management system that manages devices. In this embodiment, an example will be described in which a device management service manages an image forming apparatus 106 that is a network device. The device management system includes the image forming apparatus 106 that is the object of management, a monitoring apparatus 105 that is a relay apparatus, and a group of servers that provide device management services to the image forming apparatus 106 via a network. There may be multiple image forming apparatuses 106. These are connected via the network.

[0011] The image forming device 106 is a network device that receives various services from a group of servers in the system. The image forming device 106 is, for example, an MFP (Multifunction Peripheral) having a printing function and a scanning function. The image forming device 106 receives print data received via a network using the printing function, and prints the data on actual paper or the like using known printing technology such as electrophotography technology or inkjet technology. The image forming device 106 reads a paper document via a scanner and converts it into image data using the scanning function. Note that the network device may be any device capable of communication, and may be, for example, a single-function printer having only a printing function, a scanner, a 3D printer, a notebook computer, a smartphone, a smart home appliance, or the like.

[0012] The monitoring device 105 monitors the image forming device 106, which is a network device, via the network. The monitoring device 105 is connected between the server group and the image forming device 106. The monitoring device 105 collects data from the image forming device 106 and transmits it to the server. The monitoring device 105 of this embodiment also has a proxy server function and functions as a relay device that relays communication between the image forming device 106 and the server group. Note that some of the image forming devices 106 that are targets of management of the device management service may function as the monitoring device 105.

[0013] The server group manages data collected by the monitoring device 105 and the image forming device 106 and monitoring device 105 that are targets of management, and provides a device management service. The server group in this embodiment includes, for example, a device management server 101, an authentication and authorization server 102, a resource server 103, and a service providing server 104. The device management server 101 is an information processing device that manages information on the image forming device 106 and monitoring device 105 that are targets of various services.

[0014] The authentication and authorization server 102 is an information processing device that provides an authentication and authorization function for securely connecting the image forming device 106 and the monitoring device 105 to various servers. The authentication and authorization server 102 performs authentication and authorization using, for example, a general OAuth mechanism. The authentication and authorization server 102 registers each device (the image forming device 106, the monitoring device 105) as a client linked to a specific tenant, and issues a token to the client. By using the issued token, each device (the image forming device 106, the monitoring device 105) accesses various servers.

[0015] The resource server 103 is an information processing device that manages information collected from the image forming device 106 that is mainly required to provide services. The service providing server 104 provides various services such as maintenance services and reporting services based on various information of the image forming device 106 managed by the resource server 103. Note that the functions of the server group may be realized by one or more information processing devices, a virtual machine (cloud service) that uses resources provided by a data center including the information processing devices, or a combination of these.

[0016] The server group (device management server 101, authentication and authorization server 102, resource server 103, and service providing server 104) is connected to a LAN (Local Area Network) 109. The image forming apparatus 106 and the monitoring apparatus 105 are connected to a LAN 108. The LAN 109 and the LAN 108 are connected to a WAN (Wide Area Network) 107. In this manner, the server group, the monitoring apparatus 105, and the image forming apparatus 106 are connected via a network. Note that the network may be configured to transmit and receive data, and any communication method may be used. For example, the network may be configured as a LAN, a WAN, a cellular network such as LTE or 5G, a wireless network, a telephone line, a dedicated digital line, or a combination of these.

[0017] 2 is a diagram showing an example of a hardware configuration of the image forming apparatus 106. The image forming apparatus 106 includes an overall control unit 211, a reader unit 212, a printer unit 213, an operation unit 214, and a switch unit 215. The overall control unit 211 includes a CPU 201, a ROM 202, a RAM 203, a HDC 204, a HDD 205, a reader I / F 207, a printer I / F 208, an operation unit I / F 209, a switch I / F 210, and an NWI / F 216. The CPU 201, the ROM 202, the RAM 203, the HDC 204, the reader I / F 207, the printer I / F 208, the operation unit I / F 209, the switch I / F 210, and the NWI / F 216 are connected via a system bus 206.

[0018] A CPU (Central Processing Unit) 201 performs overall control of the entire image forming apparatus 106. The CPU 201 performs overall control of each device connected to a system bus 206 by executing software for controlling the image forming apparatus 106 stored in a ROM 202 or a HDD 205. A ROM (Read Only Memory) 202 is a memory dedicated to reading data, and stores, for example, a basic control program for the image forming apparatus 106. A RAM (Random Access Memory) 203 is a memory from which data can be read and written. The RAM 203 functions, for example, as a work area for the CPU 201.

[0019] A hard disk controller (HDC) 204 controls a hard disk drive (HDD) 205. The hard disk drive (HDD) 205 is an example of a storage device, and stores various programs, data, etc. Note that, although an example in which the image forming apparatus 106 includes the HDD 205 as a storage device will be described in this embodiment, this is not limiting, and other storage devices such as an SSD or a disk drive that loads an external medium may be used.

[0020] The reader I / F 207 is an interface that connects the reader unit 212 and the system bus 206, and controls the reader unit 212. The reader unit 212 reads an original as an image and generates image data. The generated image data is used for various processes such as outputting the image data to the printer unit 213, storing the image data in the HDD 205, and transmitting the image data to a host computer connected to a network 217 via a network I / F 216, in response to an instruction from a user.

[0021] The printer I / F 208 is an interface that connects the printer unit 213 and the system bus 206, and controls the printer unit 213. The printer unit 213 prints the document read by the reader unit 212 and image data stored in the HDD 205 onto a recording medium (e.g., onto paper). The printer unit 213 also receives a print job from a host computer connected to a network 217 via a network I / F unit 216, and prints the image data based on the print job.

[0022] The operation unit I / F 209 is an interface that connects the operation unit 214 and the system bus 206, and controls the operation unit 214. The operation unit I / F 209 controls display on the operation unit 214 and user input from the operation unit 214. The operation unit 214 displays to the user and accepts operations from the user. The operation unit 214 may be configured, for example, with a display and buttons for operation, or may be configured with a touch panel. By associating input coordinates and display coordinates on the touch panel, it is possible to configure a GUI that makes it appear as if the user can directly operate a screen displayed on the touch panel.

[0023] The switch I / F 210 is an interface that connects the switch unit 215 and the system bus 206, and controls the switch unit 215. The switch unit 215 has a switch for controlling the power ON / OFF state of the image forming apparatus 106, etc. The NW (Network) I / F 216 is a communication interface that connects the image forming apparatus 106 and a network (for example, LAN 108). The CPU 201 communicates with other information devices on the network via the NWI / F 216 and the network.

[0024] 3 is a diagram showing an example of the hardware configuration of the monitoring device 105. In addition, the server group (the device management server 101, the authentication and authorization server 102, the resource server 103, and the service providing server 104) also have the same hardware configuration as the monitoring device 105. The monitoring device 105 has the same hardware configuration as a general information processing device, and includes a CPU 303, a memory 304, a storage device 302, an operation I / F 305, and a communication I / F 301.

[0025] The CPU 303 of the monitoring device 105 controls the entire monitoring device 105. The CPU 303 loads a program from the storage device 302 into the memory 304 and executes it to realize various controls. The storage device 302 stores an operating system (OS), programs, management data, data collected from external systems and devices, etc. The memory 304 functions as a work area for the CPU 303. The operation I / F 305 outputs various data and execution results of programs to a connected output device such as a display, and receives input from a connected input device. The communication I / F 301 is a network interface for communicating with external systems and devices. The communication I / F 301 of the monitoring device 105 is connected to, for example, the WAN 107 and the LAN 108.

[0026] 4 is a diagram showing an example of the software configuration of the image forming apparatus 106. The image forming apparatus 106 has a communication unit 401 and a data management unit 402. The communication unit 401 communicates with external devices such as the monitoring device 105. The data management unit 402 manages basic information of the device, various types of operation information, and the like. The basic information of the device includes, for example, the device name, serial number, and product name. The various types of operation information include, for example, the number of printed sheets, the remaining amount of ink, and error information.

[0027] The image forming apparatus 106 having a self-monitoring function has a self-monitoring unit 406. The self-monitoring function is a function of monitoring the apparatus itself, collecting operation information required for a device management service within the apparatus itself, and transmitting the information to various servers that provide the device management service. The self-monitoring unit 406 has an authentication unit 403, a monitoring unit 404, and a data transmission unit 405. The authentication unit 403 communicates with the authentication and authorization server 102, and performs registration processing as a client, and token acquisition and management. The authentication unit 403 also communicates with the monitoring apparatus 105 regarding settings required for monitoring, including a registration instruction to the authentication and authorization server 102. The monitoring unit 404 performs data collection required for self-monitoring. The data transmission unit 405 transmits data collected by the monitoring unit 404 to the resource server 103.

[0028] 5 is a diagram showing an example of the software configuration of the monitoring device 105. The monitoring device 105 includes a proxy server 501, a data management unit 502, a device management unit 503, a task management unit 504, and a data transmission unit 505. The proxy server 501 collects communications from the image forming device 106 having a self-monitoring function and relays communications between the image forming device 106 and a device management service. The data management unit 502 manages device information required for device monitoring. For example, the data management unit 502 manages status information indicating whether a device is a device under its own management. The data management unit 502 also manages monitoring data and the like acquired from the image forming device 106 not having a self-monitoring function.

[0029] The mechanisms by which the server group obtains device data include a method in which the monitoring device 105 collects data from the image forming device 106 by regular polling and sends it to the server group, and a method in which the monitoring device 105 serves as a proxy server and collects data from the image forming device 106. The monitoring device 105 has a proxy mode and a polling mode as monitoring modes. In the polling mode, the monitoring device obtains data from the image forming device 106 by regular polling and transmits the obtained information to a server in the server group to manage the device. In the proxy mode, the monitoring device 105 functions as a proxy server that relays communication between the image forming device 106, which has a self-monitoring function, and the server group.

[0030] The device management unit 503 sets the proxy server information held by itself, instructs registration, etc., for the image forming apparatus 106 having the self-monitoring function. In addition, the device management unit 503 registers the image forming apparatus 106 to the device management service (for example, the authentication and authorization server 102) instead of the image forming apparatus 106 not having the self-monitoring function. The device management unit 503 has a proxy setting unit 511, a determination unit 512, and a registration unit 513. The proxy setting unit 511 performs proxy setting using the proxy information of the proxy server function for the device that uses the proxy server 501. The proxy setting unit 511 of this embodiment performs proxy setting for the image forming apparatus 106 having the self-monitoring function. The determination unit 512 determines whether or not to execute re-registration processing of the image forming apparatus 106 to the device management service. The determination unit 512 determines whether or not the image forming apparatus 106 is a target for re-registration processing based on whether or not the image forming apparatus 106 has the self-monitoring function for the device management service. A task management unit 504 manages various tasks of the monitoring device 105, such as monitoring and registration of the image forming device 106. A data transmission unit 505 transmits, to the resource server 103, monitoring data and the like acquired from the image forming device 106 that does not have a self-monitoring function and that is held in the data management unit 502.

[0031] The process of registering the image forming apparatus 106 in the device management service will be described with reference to Figs. 15 to 17. In the registration process, each process executed by the image forming apparatus 106 is realized by the CPU 201 of the image forming apparatus 106 executing a program stored in memory (ROM 202 or HDD 205). Each process executed by the monitoring apparatus 105 is realized by the CPU 303 of the monitoring apparatus 105 executing a program stored in memory 304. Each process executed by the device management server 101 is realized by the CPU 303 of the device management server 101 executing a program stored in memory 304. Each process executed by the authentication and authorization server 102 is realized by the CPU 303 of the authentication and authorization server 102 executing a program stored in memory 304.

[0032] In this embodiment, the registration process to the device management service and the monitoring mode of the monitoring device 105 differ depending on whether the image forming device 106 has a self-management function. Therefore, in the registration process of the image forming device 106 to the device management service, first, a capability determination is made as to whether the image forming device 106 has a self-management function. Fig. 6 is a sequence diagram showing the capability determination process of the image forming device 106. Here, it is assumed that the device to be managed by the monitoring device 105 is managed in advance by the device management server 101.

[0033] In S601, the device management unit 503 of the monitoring device 105 requests the device management server 101 to acquire a list of managed devices of the monitoring device 105. The device management server 101 has in advance a managed device list that lists devices to be managed by the monitoring device 105. In S602, the device management server 101 transmits the managed device list of the monitoring device 105 to the monitoring device 105 in response to the request to acquire the managed device list. As a result, the device management unit 503 of the monitoring device 105 acquires the managed device list of the monitoring device 105 from the device management server 101.

[0034] In S603, the device management unit 503 of the monitoring device 105 requests the devices in the managed device list to determine the capabilities of the devices. In this embodiment, the device management unit 503 of the monitoring device 105 requests the communication unit 401 of the image forming device 106 to determine the capabilities of the image forming device 106. In the capability determination, it is determined whether or not the image forming device 106 has a self-monitoring function, and if the image forming device 106 does not have a self-monitoring function, whether or not the monitored data can be acquired.

[0035] In S604, the data management unit 402 of the image forming apparatus 106 transmits information used in device capability determination to the device management unit 503 of the monitoring apparatus 105 via the communication unit 401. Examples of information used in device capability determination include the presence or absence of a specific service or module, firmware version information, and the like. In S605, the determination unit 512 of the monitoring apparatus 105 performs device capability determination based on information acquired from the device. The determination unit 512 first determines whether the image forming apparatus 106 has a self-monitoring function. For example, the determination unit 512 determines whether the image forming apparatus 106 is a device having a self-monitoring function depending on whether a service having a self-monitoring function exists. In this case, if a service having a self-monitoring function exists, the determination unit 512 determines that the device has a self-monitoring function. If the device does not have a self-monitoring function, the determination unit 512 determines whether the monitoring apparatus 105 is a monitorable device. For example, the determination unit 512 determines whether the device is a monitorable device depending on whether the device can collect monitoring target data and transmit it to the monitoring apparatus 105. The method of determining the capabilities of a device is not limited to this, and other methods may be used. Alternatively, the device may determine whether or not it has a self-monitoring function, and respond to the monitoring device 105 with the determination result.

[0036] The monitoring device 105 issues instructions for registration processing according to the determination result. In the case of a device with a self-monitoring function, the monitoring device 105 executes registration processing for a device with a self-monitoring function in S607. In the case of a device that does not have a self-monitoring function but can be monitored, the monitoring device 105 executes registration processing for a device without a self-monitoring function in S606. Note that in the case of a device that does not have a self-monitoring function and cannot be monitored, the device is not registered in the monitoring device 105 and this processing ends.

[0037] Next, the registration process of an image forming device that does not have a self-monitoring function, which is S606, will be described. Fig. 7 is a sequence diagram showing the registration process of an image forming device that does not have a self-monitoring function. In this embodiment, a device registration key is used to register the image forming device 106 to be managed in the authentication and authorization server 102. The device registration key is information required when registering the image forming device 106 to be managed in the authentication and authorization server 102 of the device management service.

[0038] In S701, the device management unit 503 of the monitoring apparatus 105 requests the device management server 101 to acquire a device registration key. The request to acquire the device registration key includes device identification information of the device to be registered and a token of the monitoring apparatus 105. In this embodiment, information by which the device management server 101 uniquely identifies the image forming apparatus 106 (hereinafter, referred to as a device management service device ID) is added to the request to acquire the device registration key as the device identification information. The device management service device ID is managed by the data management unit 502 as a part of the device management information.

[0039] An example of device management information managed by the data management unit 502 of the monitoring device 105 will now be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of a device management information table. The device management information includes, for example, a device ID 801, a serial number 802, an IP address 803, a management status 804, a registration status 805, a monitoring type 806, a re-registration flag 807, and a device management service device ID 808.

[0040] The device ID 801 is information that uniquely identifies the device within the system. The serial number 802 is information that uniquely identifies the device, which is set at the time of shipping the device. The IP address 803 is information that indicates the IP address of the device. The management status 804 is information that indicates whether the device is a target for management by the device management system. Here, the image forming apparatus 106 included in the managed device list acquired from the device management server 101 in S602 is determined to be a managed device. The registration status 805 is information that indicates whether the managed image forming apparatus 106 has been registered in the device management service.

[0041] The monitoring type 806 is information indicating the type of monitoring to be performed. For example, if the image forming device 106 has a self-monitoring function, monitoring is performed via a proxy of the monitoring device 105. Therefore, "Proxy" is stored in the monitoring type 806 of the image forming device 106 having the self-monitoring function. Also, if the image forming device 106 does not have a self-monitoring function, monitoring is performed by collecting monitoring data from the monitoring device 105 by regular polling. Therefore, "Polling" is stored in the monitoring type 806 of the image forming device 106 without a self-monitoring function. Then, in the case of a device that does not have monitorable capability information or for which capability determination has not been performed, information indicating this (e.g., "Unknown") is stored in the monitoring type 806.

[0042] The re-registration flag 807 is information indicating whether or not a device registered as a device without a self-monitoring function is to be re-registered as a device with a self-monitoring function. For example, the re-registration flag 807 stores "1" when a device without a self-monitoring function is to be re-registered as a device with a self-monitoring function, and stores "0" otherwise. The device management service device ID 808 is information with which the device management server 101 uniquely identifies the image forming apparatus 106. Note that the device management information is not limited to this and may include other information.

[0043] Returning to the description of Fig. 7, in S702, the device management server 101 verifies the token of the monitoring device 105 included in the received request to acquire a device registration key and the device identification information of the device to be registered, and then issues a device registration key issue request to the authentication and authorization server 102. The device registration key issue request includes a device management service device ID. Specifically, the device management server 101 first verifies the token of the monitoring device 105 included in the request to acquire a device registration key. After verifying the token, the device management server 101 checks whether the image forming device 106 is a device managed on the device management server 101 based on the device management service device ID.

[0044] Here, the information managed by the device management server 101 will be described with reference to Fig. 9. Fig. 9(A) is a diagram showing an example of a device management table managed by the device management server 101. In the device management table, information on devices that are the targets of services provided by the device management server 101 is managed. The device management table includes, for example, a device ID 901, a serial number 902, a tenant ID 903, an agent ID 904, and a status 905.

[0045] The device ID 901 is a device management service device ID. The device ID 901 is the same information as the client ID in a client management table managed by the authentication and authorization server 102, which will be described later. The serial number 902 is information that uniquely identifies the device. The tenant ID 903 is information that identifies the tenant to which the device belongs. The agent ID 904 is information that identifies the agent to which the device is linked. The status 905 is information that indicates the enabled / disabled state of the device.

[0046] 9(B) is a diagram showing an example of an agent management table managed by the device management server 101. The agent management table manages information about agents who have contracted for services provided by the device management server 101. The agent management table includes, for example, an agent ID 906, a tenant ID 907, a client ID 908, and a status 909.

[0047] The agent ID 906 is information that allows the device management server 101 to uniquely identify the monitoring device 105. The tenant ID 907 is information that identifies the tenant to which the agent belongs. The client ID 908 is a client ID in a client management table managed by the authentication and authorization server 102. The status 909 is information that indicates the enabled / disabled state of the agent.

[0048] The timing at which information is registered in the device management table or agent management table of the device management server 101 is, for example, the timing at which a target device to which a service is to be provided is specified by the service providing server 104. The target device may be specified, for example, from a Web UI possessed by the service providing server 104, or a Web API may be used.

[0049] Returning to the explanation of Fig. 7, the device management server 101 confirms that the device corresponding to the device management service device ID is managed in the device management table, and then sends a device registration key issuance request to the authentication and authorization server 102 (S702). In S703, the authentication and authorization server 102 confirms whether the device to be registered is managed on the authentication and authorization server 102, and issues a device registration key. First, the authentication and authorization server 102 confirms whether the device is managed in the client management table, based on the device management service ID included in the device registration key issuance request.

[0050] Here, the information managed by the authentication and authorization server 102 will be described. FIG. 10 is a diagram showing an example of a client management table managed by the authentication and authorization server 102. The client management table includes, for example, a client ID 1001, a serial number 1002, a tenant ID 1003, and a status 1004. The client ID 1001 is information that allows the authentication and authorization server 102 to uniquely identify a device. The client ID 1001 is the same information as the device ID that the device management server 101 manages in the device management table, and is different information from the client ID 908 that the device management server 101 manages in the agent management table. The serial number 1002 is information that uniquely identifies a device. The tenant ID 1003 is information that identifies the tenant to which the device belongs. The status 1004 is information that indicates the valid / invalid state of the client.

[0051] The authentication and authorization server 102 issues a device registration key after confirming that the device is managed in the client management table based on the device management service ID included in the device registration key issuance request. Then, the authentication and authorization server 102 issues and stores the device registration key in the device registration key management table. Here, the device registration key management table that manages the issued device registration key will be described. FIG. 11 is a diagram showing an example of the device registration key management table managed by the authentication and authorization server 102. The device registration key management table includes, for example, a device registration key 1101, a tenant ID 1102, and an expiration date 1103.

[0052] The device registration key 1101 is information that uniquely identifies the device registration key. The tenant ID 1102 is information that uniquely identifies the tenant, and a device registration key is issued for each tenant. Note that multiple device registration keys can be issued for the same tenant, and if one tenant has multiple devices, a device registration key can be issued for each device. The expiration date 1103 is information that indicates expiration date information for the device registration key.

[0053] Returning to the description of Fig. 7, the device registration key issued in S703 is transmitted to the monitoring device 105, which is the source of the request to obtain the device registration key, via the device management server 101. In S704, the authentication and authorization server 102 transmits the device registration key issued in S703 to the device management server 101. In S705, the device management server 101 transmits the device registration key received from the authentication and authorization server 102 to the monitoring device 105.

[0054] In S706, the device management unit 503 of the monitoring device 105 makes an activation code acquisition request to the authentication and authorization server 102. The activation code acquisition request includes the acquired device registration key and the serial number of the device. In S707, the authentication and authorization server 102 issues an activation code in response to the activation code acquisition request. First, the authentication and authorization server 102 checks the validity of the device registration key using the client management table and the device registration key management table based on the serial number and device registration key included in the activation code acquisition request. If the device registration key is valid, the authentication and authorization server 102 issues an activation code and stores it in the activation code management table.

[0055] Here, an activation code management table for managing activation codes will be described. Fig. 12 is an example of an activation code management table managed by the authentication authorization server 102. The activation code management table includes, for example, an activation code 1201, a serial number 1202, a device registration key 1203, and an expiration date 1204. The activation code 1201 is a code issued for each device required for client activation. The serial number 1202 is information for uniquely identifying the device. The device registration key 1203 is information for uniquely identifying the device registration key. The expiration date 1204 is information indicating expiration date information of the activation code.

[0056] Returning to the description of Fig. 7, in S708, the authentication and authorization server 102 transmits the activation code issued in S707 to the monitoring device 105 which is the request source of the activation code acquisition request. In S709, the device management unit 503 of the monitoring device 105 makes an activation request to the authentication and authorization server 102. The activation request includes the device registration key, the activation code, and the serial number of the device.

[0057] In S710, the authentication and authorization server 102 issues credentials in response to the activation request. The authentication and authorization server 102 first checks the validity of the activation code. The authentication and authorization server 102 checks the validity of the activation code based on the serial number, device registration key, and activation code included in the activation request, as well as the client management table and activation code management table. If it is confirmed that the activation code is valid, the authentication and authorization server 102 issues credentials and stores them in the credential management table. After storing the credentials, the authentication and authorization server 102 updates the status information managed in the client management table to valid and stores it.

[0058] Here, a credential management table for managing credentials will be described. Fig. 13 is a diagram showing an example of the credential management table managed by the authentication and authorization server 102. The credential management table includes, for example, a client ID 1301 and credentials 1302. The client ID 1301 is information for uniquely identifying a client (device). The client ID 1301 is the same information as the client ID 1001 and the device ID 901 managed by the device management server 101, and is different information from the client ID 908 managed by the device management server 101 in the agent management table. The credentials 1302 are secret key information required when acquiring a token.

[0059] 7. In S711, the authentication and authorization server 102 transmits the credentials issued in S710 to the monitoring device 105 that is the source of the activation request. This enables the client of the image forming device 106, which is the device to be registered, and enables the monitoring device 105 to collect monitoring data of the image forming device 106 and transmit it to the resource server 103.

[0060] Next, the registration process of an image forming apparatus having a self-monitoring function will be described. Fig. 14 is a sequence diagram showing an example of the registration process of an image forming apparatus having a self-monitoring function. In S1401, the device management unit 503 of the monitoring apparatus 105 requests the device management server 101 to acquire a device registration key. The request to acquire the device registration key includes device identification information of the image forming apparatus 106 to be registered. The device identification information is a device management service device ID included in a list of devices to be managed. The device management service device ID is managed as a part of device management information in the data management unit 502. The device registration key is information required when registering the image forming apparatus 106 in the authentication and authorization server 102 of the device management service.

[0061] In S1402, the device management server 101 verifies the token of the monitoring device 105 included in the received request to acquire a device registration key and the device identification information of the device to be registered, and then requests the authentication and authorization server 102 to issue a device registration key. The request to issue a device registration key includes a device management service device ID. Specifically, the device management server 101 first verifies the token of the monitoring device 105 included in the request to acquire a device registration key. After verifying the token, the device management server 101 checks whether the image forming device 106 is a device managed on the device management server 101 based on the device management service device ID. The device management server 101 checks that the image forming device 106 is managed in a device management table, and then requests the authentication and authorization server 102 to issue a device registration key.

[0062] In S1403, the authentication and authorization server 102 checks whether the image forming device 106 is managed on the authentication and authorization server 102, and issues a device registration key. The authentication and authorization server 102 first checks whether the image forming device 106 is managed in the client management table, based on the device management service ID included in the device registration key issuance request. After checking that the image forming device 106 is managed in the client management table, the authentication and authorization server 102 issues a device registration key.

[0063] The device registration key issued in S1403 is transmitted to the monitoring device 105, which is the source of the request to obtain the device registration key, via the device management server 101. In S1404, the authentication and authorization server 102 transmits the device registration key issued in S1403 to the device management server 101. In S1405, the device management server 101 transmits the device registration key received from the authentication and authorization server 102 to the monitoring device 105.

[0064] In S1406, the proxy setting unit 511 of the device management unit 503 of the monitoring apparatus 105 transmits proxy information of the proxy server 501 of the monitoring apparatus 105 to the authentication unit 403 of the image forming apparatus 106. The proxy information is access information for a proxy function for allowing the image forming apparatus 106 to use the proxy server 501. In S1407, the data management unit 402 of the image forming apparatus 106 sets and saves the proxy information of the proxy server 501 acquired in S1404. In S1408, the image forming apparatus 106 transmits a completion of setting the proxy information to the monitoring apparatus 105.

[0065] In S1408, the device management unit 503 of the monitoring apparatus 105 requests the authentication unit 403 of the image forming apparatus 106 to obtain the proxy information set in S1407. In S1409, the image forming apparatus 106 transmits the requested proxy information to the monitoring apparatus 105. Then, the monitoring apparatus 105, which has newly obtained the proxy information set in S1407 from the image forming apparatus 106, stores the obtained proxy information in the data management unit 502. Note that, although an example in which the proxy setting is performed after obtaining the device registration key has been described in this embodiment, this order does not matter. The proxy setting (S1406 to S1410) may be performed first, and the device registration key obtaining process (S1401 to S1405) may be performed later.

[0066] In S1411, the device management unit 503 of the monitoring apparatus 105 issues a device registration instruction to the authentication unit 403 of the image forming apparatus 106. The device registration instruction includes the device registration key acquired in S1401. In S1412, the authentication unit 403 of the image forming apparatus 106 issues an activation code acquisition request to the authentication and authorization server 102. The activation code acquisition request includes the device registration key acquired in S1411 and the serial number of the image forming apparatus 106.

[0067] In S1413, the authentication and authorization server 102 issues an activation code in response to the activation code acquisition request. First, the authentication and authorization server 102 checks the validity of the device registration key using the client management table and the device registration key management table based on the serial number and device registration key included in the activation code acquisition request. If the device registration key is valid, the authentication and authorization server 102 issues an activation code and stores it in the activation code management table.

[0068] In S1414, the authentication and authorization server 102 transmits the activation code issued in S708 to the image forming apparatus 106 that is the request source of the activation code acquisition request. In S709, the authentication unit 403 of the image forming apparatus 106 sends an activation request to the authentication and authorization server 102. The activation request includes the device registration key, the activation code, and the serial number of the image forming apparatus 106.

[0069] In S1416, the authentication and authorization server 102 issues a credential in response to the activation request. The authentication and authorization server 102 first checks the validity of the activation code. The authentication and authorization server 102 checks the validity of the activation code based on the serial number, device registration key, and activation code included in the activation request, the client management table, and the activation code management table. If the activation code is confirmed to be valid, the authentication and authorization server 102 issues a credential and stores it in the credential management table. After storing the credential, the authentication and authorization server 102 updates the status information managed in the client management table to valid and stores it. In S1417, the authentication and authorization server 102 transmits the credential issued in S710 to the image forming apparatus 106 that is the source of the activation request.

[0070] After issuing the device registration instruction in S1411, the monitoring apparatus 105 then performs device registration status confirmation processing in S1418. In S1418, the device management unit 503 of the monitoring apparatus 105 performs device registration status confirmation with the authentication unit 403 of the image forming apparatus 106. The device registration status confirmation processing will be described with reference to FIG. 15. FIG. 15 is a flowchart showing the device registration status confirmation processing in the monitoring apparatus 105. In S1501, the device management unit 503 of the monitoring apparatus 105 initializes a count of the number of times the device registration status has been obtained. Specifically, the device management unit 503 initializes a variable i to 0. The variable i is a value for counting the number of times the device registration status has been obtained.

[0071] In S1502, the device management unit 503 of the monitoring apparatus 105 requests the authentication unit 403 of the image forming apparatus 106 to acquire the device registration status from the device management service, and acquires the device registration status as a response. In S1503, the device management unit 503 of the monitoring apparatus 105 checks whether the device registration status acquired in S1502 is "registered". If "registered", the device management unit 503 performs processing of S1504. On the other hand, if "not registered", the device management unit 503 performs processing of S1505.

[0072] In S1504, the device management unit 503 of the monitoring apparatus 105 changes the value of the registration status 805 in the device management information table managed by the data management unit 502 to "registered". In S1505, the device management unit 503 of the monitoring apparatus 105 checks whether the number of times the device registration status has been acquired has reached the upper limit. Specifically, if the variable i is smaller than the threshold N, the device management unit 503 determines that the upper limit has not been reached. The threshold N is a value of the upper limit number of times the device registration status has been acquired, which is determined in advance. If the variable i is not smaller than the threshold N, it determines that the upper limit has been reached, and ends this processing. On the other hand, if the variable i is smaller than the threshold N, it determines that the upper limit has not been reached, and the device management unit 503 performs processing of S1506. In S1506, the device management unit 503 of the monitoring apparatus 105 increments the value of the variable i by one, and returns the processing to S1502.

[0073] Next, the re-registration determination process of the image forming device 106 will be described. Fig. 16 and Fig. 17 are flow charts showing the re-registration determination process of the image forming device. In the re-registration determination process, it is determined whether a device registered as a device without a self-monitoring function should be re-registered as a device with a self-monitoring function. A device without a self-monitoring function can also become a device with a self-monitoring function compatible with a device management service by updating the firmware. Each process executed by the monitoring device 105 in the re-registration determination process is realized by the CPU 303 of the monitoring device 105 executing a program stored in the memory 304.

[0074] In S1601, the task management unit 504 checks whether it is time to execute a capabilities determination task for determining capabilities of devices managed by the monitoring apparatus 105. The capabilities determination process is performed on image forming apparatuses for which capabilities determination has not been performed, i.e., image forming apparatuses for which the monitoring type 806 is "Unknown". If it is time to execute the capabilities determination process, the task management unit 504 performs processing in S1602. On the other hand, if it is not time to execute the capabilities determination process, the task management unit 504 returns the process to S1601.

[0075] In S1602 to S1607, the monitoring device 105 performs a capability determination task for each of all devices managed within the monitoring device 105. When the capability determination process for all devices is completed, the capability determination task is completed. The task management unit 504 selects one of all devices managed within the monitoring device 105 and executes the processes of S1602 to S1607, and repeats this process until it is completed for all devices managed within the monitoring device 105.

[0076] First, in S1602, the task management unit 504 determines whether the selected device is a target device for executing the capabilities determination process. The task management unit 504 determines whether the selected device is a target device for executing the capabilities determination process based on the device management information held by the data management unit 502. Specifically, if the monitoring type 806 in the device management information table (FIG. 8) is "Unknown", the task management unit 504 determines that the device is a target device for executing the capabilities determination process and performs the process of S1603. On the other hand, if the monitoring type 806 is "Proxy" or "Polling", the task management unit 504 determines that the device is not a target device for executing the capabilities determination process and performs the process of S1604.

[0077] In S1603, the monitoring device 105 performs a capability determination process for the device. In the capability determination process, the monitoring device 105 determines the capability of the device based on, for example, information on whether the device is a management target and whether the device has a self-monitoring function. The monitoring device 105 determines whether the device is a management target based on the management status 804 in the device management information table. If the management status 804 is a management target, the monitoring device 105 acquires, for example, information on whether a service having a self-monitoring function exists from the device as information on whether the device has a self-monitoring function. In addition, information on whether a self-monitoring module corresponding to the self-monitoring unit 406 is installed in the device may be acquired. If a service having a self-monitoring function exists, the monitoring device 105 determines that the device has the self-monitoring function. On the other hand, if a service having a self-monitoring function does not exist, the monitoring device 105 determines that the device does not have the self-monitoring function.

[0078] In S1604, the task management unit 504 judges whether the selected device is a device to be executed for the self-monitoring function judgment process based on the device management information held by the data management unit 502. The self-monitoring function judgment process is a process for judging whether the firmware of the image forming apparatus 106, which has already been registered in the authentication and authorization server 102 and is monitored by collecting monitoring data by regular polling, has been updated to a device having a self-monitoring function. Therefore, the device to be the target of the self-monitoring function judgment process is a device that is managed, registered, and monitored by polling. The task management unit 504 judges whether the device is the target of the self-monitoring function judgment process based on the management status 804, the registration status 805, and the monitoring type 806 in the device management information table. If it is judged that the device is the target of the self-monitoring function judgment process, the task management unit 504 performs the process of S1605. On the other hand, if it is judged that the device is not the target of the self-monitoring function judgment process, the task management unit 504 ends the process of the capability judgment task and performs the process of S1608.

[0079] In S1605, the determination unit 512 of the device management unit 503 performs a self-monitoring function determination process. In the self-monitoring function determination process, the device management unit 503 determines whether the target device has a self-monitoring function. The determination of whether the target device has a self-monitoring function is made, for example, based on whether a predetermined service having a self-monitoring function exists in the device. Alternatively, the device may be determined to have a self-monitoring function by checking whether the device has been upgraded to a predetermined firmware version. Alternatively, the device may be determined to have a self-monitoring function by checking information on whether a self-monitoring module corresponding to the self-monitoring unit 406 is installed in the device.

[0080] In S1606, the judgment unit 512 of the device management unit 503 judges the result of the self-monitoring function judgment process in S1605. If it is judged that the device has the self-monitoring function, the device management unit 503 performs the process of S1607. On the other hand, if it is judged that the device does not have the self-monitoring function, the device management unit 503 ends the processing of the capability judgment task and performs the process of S1608. In S1607, the judgment unit 512 of the device management unit 503 sets a re-registration flag in the device management information table managed by the data management unit 502. In setting the re-registration flag, the device management unit 503 updates the value of the device management information table re-registration flag 807 to "1".

[0081] In S1608, the task management unit 504 starts executing the device registration task. In the processes of S1609 to S1614, the monitoring apparatus 105 processes the device registration task for all devices managed within the monitoring apparatus 105, one by one. When the process is completed for all devices, the device registration task is completed. The task management unit 504 selects one of all devices managed within the monitoring apparatus 105 and repeats the process of S1609 to S1614 until the process is completed for all devices managed within the monitoring apparatus 105.

[0082] In S1609, the task management unit 504 judges whether the selected device is a device to be subjected to the re-registration process based on the management information of the device held in the data management unit 502. The re-registration process is a process for re-registering a device that has already been monitored by periodic polling in order to monitor the device through a proxy of the monitoring apparatus 105. The device to be subjected to the re-registration process is a device that does not have a self-monitoring function and whose monitoring data was collected by periodic polling, but has been firmware updated to a device with a self-monitoring function. Therefore, the device to be subjected to the re-registration process is a device for which a re-registration flag is set in the device management information table. If the value of the re-registration flag 807 is "1" and it is determined that the device is a target for the re-registration process, the task management unit 504 performs the process of S1610. If the value of the re-registration flag 807 is "0" and it is determined that the device is not a target for the re-registration process, the task management unit 504 performs the process of S1611. In S1610, the task management unit 504 performs the device re-registration process. Details of the device re-registration process will be described later with reference to FIG. 18.

[0083] In S1611, the task management unit 504 judges whether the selected device is a device to be registered based on the management information of the device management held in the data management unit 502. The registration process is a process for registering the image forming apparatus 106 that is a managed object and is not registered in the authentication and authorization server 102. Therefore, the device to be registered is the image forming apparatus 106 that is a managed object and is not registered. The task management unit 504 judges whether the device is a target of the registration process based on the management status 804 and the registration status 805 in the device management information table. If the management status 804 is "managed object" and the registration status 805 is "not registered", the task management unit 504 judges that the device is a target of the registration process. If it is judged that the device is a target of the registration process, the task management unit 504 performs the process of S1612. On the other hand, if it is judged that the device is not a target of the registration process, the task management unit 504 performs the process of S1613. In S1612, the monitoring apparatus 105 performs the device registration process. In the device registration process, if the device does not have a self-monitoring function, the process of S606 (FIG. 7) is performed, and if the device has a self-monitoring function, the process of S607 (FIG. 14) is performed.

[0084] In S1613, the task management unit 504 judges whether the selected device is a device to be subjected to the release process based on the management information of the device held in the data management unit 502. The release process is a process for canceling the registration of a device that is not managed and registered in the authentication and authorization server 102. Therefore, the device to be subjected to the release process is a device that is not managed and registered. If the management status 804 is "not managed" and the registration status 805 is "registered" in the device management information table, it is judged that the device is a device to be subjected to the release process, and the task management unit 504 performs the process of S1614. On the other hand, if the management status 804 is "not managed" and the registration status 805 is not "registered", it is judged that the device is not a device to be subjected to the release process, and the task management unit 504 ends this process. In S1614, the task management unit 504 executes the release process of the device. Note that the release process is not directly related to the present invention, so a description thereof will be omitted.

[0085] Next, details of the device re-registration process in S1610 will be described with reference to Fig. 18. Fig. 18 is a flowchart illustrating the re-registration process of the image forming apparatus 106. The device that is the target of the re-registration process in S1610 is a device that does not have a self-monitoring function and has collected monitoring data by regular polling, but has acquired the self-monitoring function through a firmware update or the like. Monitoring using the proxy mode of the monitoring device 105 makes it possible to provide more services to the device than the polling mode. For this reason, the device with the self-monitoring function deactivates its registration as a device without the self-monitoring function and performs registration processing as a device with the self-monitoring function so that it can use the monitoring device 105 in proxy mode.

[0086] In S1701, the device management unit 503 performs a deactivation process for the target device. In the deactivation process, a request to deactivate the target device is made to the authentication and authorization server 102. The deactivation request includes information on the device management service device ID 808 of the device to be deactivated. The authentication and authorization server 102 that has received a request for deactivation process from the monitoring device 105 changes the status 1004 of the target device managed in the client management table (FIG. 10) to invalid based on the device management service device ID 808. Then, the authentication and authorization server 102 transmits the result of the deactivation process to the monitoring device 105 that is the source of the deactivation request.

[0087] In S1702, the device management unit 503 determines whether the deactivation of the target device has been successful based on the response from the authentication and authorization server 102 to the deactivation request. If the deactivation has been successful, the monitoring apparatus 105 performs the process of S1703. On the other hand, if the deactivation has failed, this process ends. In S1703, the device management unit 503 changes the registration status 805 in the device management information table (FIG. 8) held by the data management unit 502 from "registered" to "unregistered" and the monitoring type 806 from "Polling" to "Proxy". As a result, the monitoring type of the target device in the monitoring apparatus 105 is updated from polling mode to proxy mode.

[0088] In S1704, the registration unit 513 of the device management unit 503 performs a process of registering the target device as a device having a self-monitoring function. The process of registering the target device as a device having a self-monitoring function executed in S1704 is the same as the process of registering an image forming device having a self-monitoring function shown in Fig. 14. Through this process, the monitoring device 105 sets proxy information of the proxy server 501 in the target device, so that the target device can use the proxy server 501 of the monitoring device 105 (S1406 to S1410). In addition, a device registration instruction using a device registration key is issued to the target device (S1411), and the target device communicates with the authentication and authorization server 102 to register the device (S1412 to S1417).

[0089] In S1705, the device management unit 503 judges whether the activation has been successful. Whether the activation has been successful is judged based on the response to the activation request acquired from the authentication and authorization server 102 in S1417. If the activation has been successful, the device management unit 503 performs the process of S1706. On the other hand, if the activation has failed, the device management unit 503 ends this process. In S1706, the device management unit 503 updates the management information of the device held in the data management unit 502. The device management unit 503 deletes the re-registration flag in the management information of the device. Specifically, the device management unit 503 updates the value of the re-registration flag 807 in the device management information table from "1" to "0". This completes the process of re-registering a device that has become equipped with a self-monitoring function by a firmware update or the like so that the device can use the proxy server 501. Furthermore, the device management unit 503 updates the registration status 805 in the device management information table, which was updated to "unregistered" in S1703, from "unregistered" to "registered."

[0090] As described above, according to this embodiment, the capability information of a monitored device that does not have a self-monitoring function is periodically checked, and when the device becomes a device with a self-monitoring function, a re-registration process can be performed as a device with a self-monitoring function. The re-registration process makes it possible to switch the monitoring method of the device by the monitoring device from polling mode to proxy mode without the user's effort. This allows the device registration status on the cloud service side to be dynamically switched according to the device's capability status, and device monitoring can be appropriately managed without the effort of the service provider.

[0091] Example 2 In the first embodiment, the monitoring method is switched by periodically checking the capability information of the device and re-registering the device as a device having a self-monitoring function. However, when switching the monitoring method, if there is unsent data to the cloud service acquired by periodic polling, the monitoring data will be lost. Therefore, before the device deactivation process (S1701) for device re-registration, if there is unsent monitoring data held in the data management unit 502, the data transmission unit 505 may transmit the data to the resource server 103. By transmitting the unsent monitoring data to the resource server 103 before executing the device deactivation process, it becomes possible to manage continuous monitoring data without data loss even when the monitoring method is switched.

[0092] Example 3 The monitoring device 105 has a setting means for switching the monitoring mode (polling mode or proxy mode). When the monitoring mode is the polling mode, the monitoring type of even devices having a self-monitoring function is the polling mode, and the proxy server of the monitoring device cannot be used. When the monitoring mode is the proxy mode, the monitoring type of devices not having a self-monitoring function is the polling mode, but it is desired to have devices having a self-monitoring function use the proxy server of the monitoring device and switch the monitoring type to the proxy mode.

[0093] In the first embodiment, a case has been described in which a device that does not have a self-monitoring function becomes a device with a self-monitoring function by a firmware update while a device is being monitored through a monitoring device. However, the monitoring device can switch and set the monitoring mode, and when the monitoring device is in a polling mode, even a device with a self-monitoring function cannot use the proxy server of the monitoring device. In this way, even if a device originally has a self-monitoring function, there are cases in which the monitoring mode of the monitoring device is not a proxy mode that uses the proxy server function but a polling mode. When the monitoring mode of the monitoring device is switched from the polling mode to the proxy mode, in order for a device with a self-monitoring function to receive a device management service using the proxy server of the monitoring device, the device needs to be re-registered in the device management service. Therefore, in this embodiment, when the monitoring mode of the monitoring device is switched to the proxy mode, the monitoring method of the device with the self-monitoring function is switched, and an instruction is given to register the device in the device management service as a device with a self-monitoring function. In the following, only the differences from the first embodiment are described, and the same configurations and processes as those in the first embodiment are given the same reference numerals and their description is omitted.

[0094] A re-registration determination process of the image forming device 106, which is a network device to be managed in this embodiment, will be described. FIG. 19 and FIG. 17 are flow chart diagrams showing the re-registration determination process of the image forming device in the third embodiment. In the re-registration determination process of this embodiment, it is determined whether to re-register the device as a device having a self-monitoring function according to the monitoring mode of the monitoring device 105. Specifically, when the monitoring mode of the monitoring device 105 is the proxy mode, a process is performed to determine whether to re-register the device as a device having a self-monitoring function. Each process performed by the monitoring device 105 in the re-registration determination process is realized by the CPU 303 of the monitoring device 105 executing a program stored in the memory 304. The process shown in FIG. 19 is performed, for example, when the setting of the monitoring mode of the monitoring device 105 is changed.

[0095] S1601 is the same process as in the first embodiment. In S1602, the task management unit 504 determines whether the selected device is a device for which the capabilities determination process is to be executed. The task management unit 504 determines whether the selected device is a device for which the capabilities determination process is to be executed based on the device management information held by the data management unit 502. Specifically, when the monitoring type 806 in the device management information table (FIG. 8) is "Unknown", the task management unit 504 determines that the device is a device for which the capabilities determination process is to be executed, and performs the process of S1603. On the other hand, when the monitoring type 806 is "Proxy" or "Polling", the task management unit 504 determines that the device is not a device for which the capabilities determination process is to be executed, and performs the process of S1901.

[0096] In S1901, the task management unit 504 determines whether the monitoring mode of the monitoring device 105 is a proxy mode. The monitoring mode of the monitoring device 105 is information indicating how to manage the image forming device 106. The management device 105 of this embodiment has a proxy mode and a polling mode as the monitoring mode, and either the proxy mode or the polling mode is set as the monitoring mode. For example, in the "polling mode", the monitoring device 105 monitors all devices by polling regardless of the functions that the devices have. In the "proxy mode", the monitoring device 105 manages devices that have a self-monitoring function by making the proxy server 501 of the monitoring device 105 use the device to manage devices that do not have a self-monitoring function, and monitors devices that do not have a self-monitoring function by polling.

[0097] The task management unit 504 determines whether the monitoring mode of the monitoring device 105 is the proxy mode based on the information of the monitoring mode management table held in the data management unit 502. FIG. 20 is a diagram showing an example of a monitoring mode management table. The monitoring mode management table 2000 is a table in which the monitoring mode settings of the monitoring device 105 are stored. The monitoring mode management table 2000 is saved in the data management unit 502. The monitoring mode management table 2000 has setting items (Key) and setting values ​​(Value). In the example shown in FIG. 20, "Mode" indicating the monitoring mode is stored in the setting item (Key), and "Proxy" indicating the proxy mode is stored in the setting value (Value). When the monitoring mode is the polling mode, "Polling" is stored in the setting value (Value).

[0098] The monitoring mode is set by the user from a monitoring mode setting screen that the monitoring device has in advance. FIG. 21 is a diagram showing an example of the monitoring mode setting screen. The monitoring mode setting screen displays a monitoring mode setting area 2100 for setting the monitoring mode and an OK button 2103. The proxy mode and the polling mode are displayed in the monitoring mode setting area 2100, and the user selects one of the modes. In the example shown in FIG. 21, a radio button 2101 for selecting the proxy mode and a radio button 2102 for selecting the polling mode are displayed, and the user selects one of the radio buttons to select the monitoring mode of the monitoring device 105. By pressing the OK button 2103 after selecting the monitoring mode, the selected monitoring mode is set as the monitoring mode of the monitoring device 105. Information on the set monitoring mode is managed in a monitoring mode management table (FIG. 20) held by the data management unit 502. Note that the radio buttons are merely an example, and it is sufficient that the monitoring mode of the monitoring device 105 can be set on the monitoring mode setting screen.

[0099] In S1901, the task management unit 504 determines whether the monitoring mode of the monitoring device 105 is the proxy mode based on the monitoring mode setting managed in the monitoring mode management table (FIG. 20). If the setting value (Value) in the monitoring mode management table is "Proxy", the task management unit 504 determines that the monitoring mode of the monitoring device 105 is the proxy mode, and performs the process of S1604. If the monitoring mode of the monitoring device 105 is the proxy mode, the monitoring device 105 can cause a device having a self-monitoring function to use the proxy server 501 of the monitoring device 105. For this reason, a series of processes (S1604 to S1607) are performed to check whether the device has the self-monitoring function. That is, when the monitoring mode of the device by the monitoring device 105 is switched to the proxy mode that causes the device to use the proxy server function of the monitoring device 105, the determination unit 512 determines whether the device has the self-monitoring function for the device management service. On the other hand, if the setting value (Value) in the monitoring mode management table is "Polling", the task management unit 504 determines that the monitoring mode of the monitoring device 105 is the polling mode and not the proxy mode, and performs the process of S1608 (FIG. 17). If the monitoring mode of the monitoring device 105 is the polling mode, the device cannot be made to use the proxy server 501 of the monitoring device 105, and there is no need to re-register the device having the self-monitoring function. Therefore, if the monitoring mode of the monitoring device 105 is the polling mode, a series of processes (S1604 to S1607) for checking whether the device has the self-monitoring function is not executed. The processes from S1604 onwards are the same as those in the first embodiment.

[0100] For the device for which the re-registration flag was set in S1607, the monitoring device 105 changes the registration status 805 in the device management information table (FIG. 8) from "registered" to "unregistered" and the monitoring type 806 from "polling" to "proxy" in S1703. This updates the monitoring type of the target device in the monitoring device 105 from polling mode to proxy mode. Then, in S1704, the monitoring device 105 instructs the device management service to perform a registration process (FIG. 14) for registering the target device as a device having a self-monitoring function. By the above process, when the monitoring mode of the monitoring device is switched from polling mode to proxy mode, it is possible to determine whether the device has a self-monitoring function, and if the device has the self-monitoring function, to re-register the device as a device having the self-monitoring function. By performing the registration process as a device having a self-monitoring function, the device can use the proxy server 501 of the monitoring device 105 in proxy mode and can receive more services than in polling mode.

[0101] As described above, according to this embodiment, even when the monitoring mode in the monitoring device is switched from the polling mode to the proxy mode, it is possible to switch the monitoring type of the device from the polling mode to the proxy mode and issue a re-registration instruction.

[0102] The disclosure of this embodiment includes the following configuration of a relay device. (Configuration 1) A relay device having a proxy server function for relaying communication between a device management service and a device, a determination unit that determines whether a device that is provided with a device management service without using a proxy server function of the relay device has a self-monitoring function for the device management service; a setting unit that performs proxy setting in the device using proxy information of the proxy server function of the relay device when the device has a self-monitoring function; a registration unit that issues a registration instruction to the device for which the proxy setting has been performed, to cause the device to be re-registered in the device management service as a device having a self-monitoring function. (Configuration 2) 2. The relay device according to claim 1, wherein, when a device has a self-monitoring function, the relay device requests the device management service to deactivate the device, and performs the proxy setting after the deactivation is completed. (Configuration 3) The device management unit further includes a device management unit for managing device information. The relay device according to configuration 2, characterized in that when the deactivation of the device is completed, the device management unit updates the registration status information of the device from information indicating registered to information indicating unregistered, and when the activation request by the device that received the registration instruction to the device management service is successful, the device management unit updates the registration status information of the device from information indicating unregistered to information indicating registered. (Configuration 4) The relay device according to configuration 3, characterized in that when the deactivation of the device is completed, the device management unit updates a monitoring type for the device from a polling mode in which device information is collected by periodic polling to a proxy mode in which the device uses the proxy server function. (Configuration 5) The relay device according to any one of configurations 2 to 4, characterized in that when it is determined that a device has a self-monitoring function, if there is data collected from the device but not yet transmitted to the device management service, the relay device transmits the data to the device management service before requesting the device management service to deactivate the device. (Configuration 6) The relay device according to any one of configurations 1 to 5, characterized in that when a monitoring mode of the device by the relay device is switched to a mode that causes the device to use a proxy server function of the relay device, the determination unit determines whether the device has a self-monitoring function for the device management service. (Configuration 7) the device is an image forming apparatus, 7. The relay device according to any one of configurations 1 to 6, wherein an image forming device that does not have a self-monitoring function for the device management service is updated to an image forming device that has the self-monitoring function by updating firmware.

[0103] (Other Examples) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-mentioned embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0104] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

Claims

1. A relay device having a proxy server function for relaying communication between a device management service and a device, a determination unit that determines whether a device that is provided with a device management service without using a proxy server function of the relay device has a self-monitoring function for the device management service; a setting unit that performs proxy setting in the device using proxy information of the proxy server function of the relay device when the device has a self-monitoring function; a registration unit that issues a registration instruction to the device for which the proxy setting has been performed to cause the device to be re-registered in the device management service as a device having a self-monitoring function.

2. 2. The relay device according to claim 1, wherein, when a device has a self-monitoring function, the relay device requests the device management service to deactivate the device, and performs the proxy setting after the deactivation is completed.

3. The device management unit further includes a device management unit for managing device information. The relay device according to claim 2, characterized in that when the deactivation of the device is completed, the device management unit updates the registration status information of the device from information indicating registered to information indicating unregistered, and when the activation request by the device that received the registration instruction to the device management service is successful, the device management unit updates the registration status information of the device from information indicating unregistered to information indicating registered.

4. The relay device according to claim 3, characterized in that, when the deactivation of the device is completed, the device management unit updates a monitoring type for the device from a polling mode in which device information is collected by periodic polling to a proxy mode in which the device uses the proxy server function.

5. The relay device according to claim 2, characterized in that when it is determined that a device has a self-monitoring function, if there is data collected from the device and not yet sent to the device management service, the relay device transmits the data to the device management service before requesting the device management service to deactivate the device.

6. The relay device according to claim 1, characterized in that, when a monitoring mode of the device by the relay device is switched to a mode in which the device uses a proxy server function of the relay device, the determination unit determines whether the device has a self-monitoring function for the device management service.

7. the device is an image forming apparatus, 2. The relay device according to claim 1, wherein the image forming device that does not have a self-monitoring function for the device management service is updated to an image forming device that has the self-monitoring function by updating firmware.

8. A method for controlling a relay device having a proxy server function for relaying communication between a device management service and a device, comprising the steps of: determining whether a device that is provided with a device management service without using a proxy server function of the relay device has a self-monitoring function for the device management service; When the device has a self-monitoring function, a step of performing a proxy setting in the device using proxy information of the proxy server function of the relay device; and issuing a registration instruction to the device for which the proxy setting has been performed to cause the device to be re-registered in the device management service as a device having a self-monitoring function.

9. A program for causing a computer of a relay device to execute each step according to claim 8.

Images