JP2019095854A - System and apparatus management method - Google Patents

Abstract

To appropriately manage network apparatuses from the outside of a network by suppressing an increase in a communication load between the network and the outside.SOLUTION: A message management server 111 is configured to, when changing device information common to a plurality of apparatuses in a batch, change common state information, and to transmit a change message 411 to a relay server 112. The relay server 112 is configured to interpret the change message 411, and to update each of the device information of the plurality of apparatuses, and to update state information of each device held by the relay server itself in response to the update device information 441 from each apparatus, and to transmit a change message 451 for reporting such update in a batch to the message management server 111. The message management server 111 is configured to change common state information in response to the change message 451. A monitor server 113 is configured to, when detecting the change of the common state information held by the message management server 111, change the state information of each device corresponding to the changed common state information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a system for managing network devices such as image forming apparatuses and a device management method.

  There is a mechanism of Internet of Things (hereinafter, "IoT") that controls devices by connecting various devices to the Internet and exchanging information with each other. Regarding such an IoT mechanism, a management method has been proposed in which a device management apparatus existing on an external server (hereinafter, "cloud") available via the Internet manages network devices in an intranet. The network devices in the intranet are, for example, printers and multifunction devices used in the office.

  In this management method, information synchronized with the state information of the network device in the intranet is held as the state information of the network device on the cloud. By operating the status information of the network devices managed on the cloud, the status information of the network devices in the intranet can be changed. The status information of the network device is, for example, a property such as “power on or off”, and the function is, for example, a shadow of a device provided by Amazon Web Service.

  There are network devices that can not communicate directly with the outside. In order to manage network devices that can not communicate directly with the outside, there is a management method in which a device management apparatus is provided on a server in an intranet to manage network devices. In such a device management apparatus, the parameter setting (hereinafter referred to as “common setting”) to be commonly set to the managed device is designated, and the device is commonly operated by operating the operation unit provided for each device. There is a technology for applying settings (see Patent Document 1). In this device management apparatus, setting of common parameters in device management is facilitated by acquiring parameters from the device being managed and extracting common setting items from the parameters. According to Patent Document 1, it becomes possible to easily change the common setting, and it is also possible to extract the item of the common setting.

Patent No. 5699612 gazette

  By the way, there are cases where it is desirable to manage network devices that can not communicate directly with the outside with a device management apparatus existing on the cloud. In such a case, it is conceivable to provide a device management apparatus also on the server in the intranet. In such a configuration, it is necessary to exchange information between the device management apparatus in the intranet and the device management apparatus on the cloud.

  However, in this configuration, when the setting of the common parameter is applied to a plurality of network devices, exchange of information occurs between the device management apparatuses by the number of network devices. For this reason, the network load between the intranet and the cloud may be high.

  The present invention has been made to solve the above-mentioned problems. The present invention provides a mechanism capable of suppressing an increase in communication load between the network and the outside and appropriately managing even when managing the network apparatus from the outside of the network where the network apparatus exists. The purpose is

  According to the present invention, a relay device holds setting information of each of a plurality of network devices to be monitored in synchronization with the device main body, and setting information of each network device for each device through the relay device and the device main body And a management system for holding in a synchronized manner, wherein the management system separately sets, for common setting, setting information commonly set among a plurality of devices among the setting information for each of the devices. Holding means for holding as information, changing means for changing setting information for common setting when changing setting information common to a plurality of devices of the device body collectively, and setting information for common setting are changed Request means for transmitting to the relay device a specific update request for collectively updating setting information of device bodies of a plurality of network devices in response to the change; Update means for changing the setting information for the common setting in response to a specific notification from the relay device, and monitoring of the change in the setting information for the common setting, and when the change is detected, the holding means holds Monitoring means for respectively changing setting information for each device corresponding to the changed setting information for common setting, the relay device interprets the specific update request, and the specific update Synchronization means for updating the setting information of the device bodies of the plurality of network devices requested to be changed by the request, and updating the setting information held by itself according to the update information from each of the network devices; Notification means for transmitting to the management system a specific notification for collectively notifying the management system that the setting information of the plurality of network devices has been updated in response to the update request, A, wherein the.

  According to the present invention, even when managing a network device from the outside of the network in which the network device is present, it is possible to suppress an increase in communication load between the network and the outside and appropriately manage it.

A diagram exemplifying a configuration of a system to which a device management system showing the present embodiment can be applied Hardware configuration diagram of the devices included in the system of this embodiment Software configuration diagram of system of this embodiment Software configuration diagram of system of this embodiment Software configuration diagram of system of this embodiment Diagram showing data exchanged via WAN, LAN Diagram showing data exchanged via WAN, LAN Flow chart of change message creation process by client service Flow chart of change message processing by message management server Flow chart of device information update request relay process by relay server Flow chart of update device information transmission process by image forming apparatus Flow chart of status information change message transmission process by relay server Flow chart of monitoring process by monitoring server

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
In the present embodiment, as a device managed by the device management system, an image forming apparatus such as a multifunction peripheral, a printer, or a scanner is described as an example, but any device that can be connected to a network can be used. Good. For example, it may be a network camera or various network home appliances such as a television and an air conditioner.

First, define the terms.
“Device information” indicates status information of devices held by the image forming apparatus. The device status information includes setting information (setting values) of various setting items.
The “state information” is to hold the status information of the device held by the image forming apparatus on the cloud, for example, in the json format, using the function provided by the cloud service vendor.
The “individual state information” is state information which exists in each image forming apparatus, in which device identification information uniquely included in the image forming apparatus is described in the above-mentioned state information.
The “common state information” is state information unique to common settings in which device identification information for common settings of image forming apparatuses grouped in advance is described in the above-mentioned state information.
The “change message” is, for example, information in json format exchanged when changing the above-mentioned state information. When changing state information from a client service described later, information for uniquely identifying a request transmitted from the message management server 111 is added.

FIG. 1 is a diagram showing an example of the configuration of a system to which a device management system according to an embodiment of the present invention can be applied.
As shown in FIG. 1, the message management server 111, the relay server 112, the monitoring server 113, and the client service 114 are communicably connected via a WAN (Wide Area Network) 101 such as the Internet. The relay server 112 and the image forming apparatuses 121, 122, and 123 are communicably connected via a LAN (Local Area Network) 102, an intranet, or the like. The message management server 111 is a device management apparatus that manages network devices 121 to 123 in an internal network such as the LAN 102 from an external network such as the WAN 101.

  The message management server 111, the relay server 112, the monitoring server 113, and the client service 114 may each be configured by one device or may be configured by a plurality of devices. Further, all or a plurality of the message management server 111, the relay server 112, the monitoring server 113, and the client service 114 may be realized by the same device. The message management server 111, the monitoring server 113, and the client service 114 may be configured by a cloud server or the like. For example, the message management server 111, the monitoring server 113, and the client service 114 can be constructed using a public cloud service or the like.

Hereinafter, the hardware configuration of each device constituting the system of the present embodiment will be described using FIG.
FIG. 2A is a diagram showing an example of the hardware configuration of the image forming apparatuses 121, 122, 123. As shown in FIG.
The image forming apparatuses 121, 122, and 123 have the following sections 201 to 213:
First, the document feeding unit 201 automatically sends the document to be read set in the document tray to the image reader 202. The image reader (scanner) 202 reads, for example, a document fed by the document feeding unit 201, and generates image data.

The paper feed unit 204 feeds paper for printing to the image forming unit 203. The image forming unit 203 converts image data generated by the image reader 202 and data received from the outside into a print image, and prints an image on a sheet fed from the sheet feed unit 204.
The Network I / F 205 connects to the Network 101 and exchanges information with the outside.
A sensor 206 detects the state of each part of the apparatus.

The CPU 207 manages each process on the present apparatus. The CPU 207 reads out and executes a program stored in the hard disk 208 or the like to execute various processes to control the entire apparatus.
The hard disk 208 stores programs, data, and the like related to each process of the present apparatus. The non-volatile memory 209 is a memory that can retain data and can be rewritten without supplying power. The volatile memory 210 is a memory that can electrically store and rewrite temporary data related to each process of the present apparatus.

The operation unit 212 receives an instruction input to the apparatus. The display unit 211 displays the operation status of the apparatus and information related to the operation on the operation unit 212.
A system bus 213 links the portions 201 to 212 and exchanges data.

  FIG. 2B is a diagram showing an example of the hardware configuration of the information processing apparatus applicable to the message management server 111, the relay server 112, the monitoring server 113, and the client service 114. As for the message management server 111, the monitoring server 113 and the client service 114, FIG. 2 (b) corresponds to an example of the hardware configuration of each server PC disposed on the data center for realizing them.

The said information processing apparatus has each part of the following 221-227.
First, the display unit 221 displays windows, icons, messages, menus, and other user interface information. The operation unit 222 receives an end user's input using a keyboard and a mouse.

The CPU 223 manages each process on the present apparatus. The CPU 223 executes various processes by reading and executing a program stored in a hard disk 208 or the like to be described later, and generally controls the present apparatus.
The hard disk 224 stores programs, data, and the like related to each process of the present apparatus. The volatile memory 225 is a memory that can electrically store and rewrite temporary data related to each process of the present apparatus.

The Network I / F 226 connects to the WAN 101 and exchanges information with the outside.
A system bus 227 links the portions 221 to 226 and exchanges data.

The software configuration of the system according to the present embodiment will be described below with reference to FIGS. 3A, 3B and 3C.
FIG. 3A (a) shows an example of the software configuration 301 of the message management server 111. As shown in FIG. The software configuration 301 of the message management server 111 is constructed using functions provided by the cloud service vendor. Each part of the software configuration 301 is realized by the CPU 223 of the message management server 111 loading a program stored in the hard disk 224 or the like of the message management server 111 onto the volatile memory 225 and executing it.

The device state information holding unit 311 is a database for holding state information of the image forming apparatuses 121, 122, and 123 transmitted and received by the message management server 111.
Table 1 exemplifies the information held by the device state information holding unit 311 of the message management server 111. As shown in Table 1, the message management server 111 holds status information of each of the image forming apparatuses 121, 122, and 123 for synchronization with the device setting of the apparatus main body via the relay server 112. Further, the message management server 111 separately holds, as common state information, state information which is commonly set among a plurality of devices among the state information of each device.

The control unit 321 controls the operation of each process of the communication unit 322 and the state information operation unit 323.
The communication unit 322 processes status information of the image forming apparatuses 121, 122, and 123 transmitted and received from the relay server 112 and the client service 114.
The state information operation unit 323 performs operation processing on the device state information held by the device state information holding unit 311.

  FIG. 3A (b) shows an example of the software configuration 302 of the relay server 112. As shown in FIG. Each part of the software configuration 302 is realized by the CPU 223 of the relay server 112 loading a program stored in the hard disk 224 or the like of the relay server 112 onto the volatile memory 225 and executing the program.

The request information holding unit 331 holds request information transmitted from the message management server 111.
Table 2 exemplifies the information held by the request information holding unit 331.

The subordinate device information holding unit 332 is a database for holding state information of the image forming apparatuses 121, 122, and 123 connected to the relay server 112 via the LAN.
Table 3 exemplifies the information held by the subordinate device information holding unit 332. As shown in Table 3, the relay server 112 holds the state information of each of the devices of the image forming apparatuses 121, 122, and 123 in synchronization with the device settings of the device body.

The common setting identification information holding unit 333 holds device identification information for common setting of the image forming apparatuses grouped in advance.
Table 4 shows an example of information held in the common setting identification information holding unit 333.

The control unit 341 controls the operation of each process of the communication unit 342, the update request processing unit 343, the update device information processing unit 344, and the change message processing unit 345.
The communication unit 342 transmits and receives messages to and from the message management server 111 via the WAN, and transmits and receives data to and from the image forming apparatuses 121, 122, and 123 via the LAN.

The update request processing unit 343 transmits the request information transmitted from the message management server 111 to the image forming apparatuses 121, 122, and 123.
The update device information processing unit 344 performs processing on update device information transmitted from the image forming apparatuses 121, 122, and 123.
The change message processing unit 345 performs processing on a change message to be transmitted to the message management server 111.

  FIG. 3B (c) shows an example of the software configuration 303 of the monitoring server 113. The software configuration 303 of the monitoring server 113 is constructed using the function provided by the cloud service vendor. Each means of the software configuration 303 is realized by the CPU 223 of the monitoring server 113 loading a program stored in the hard disk 224 or the like of the monitoring server 113 onto the volatile memory 225 and executing it.

The control unit 351 controls the operation of each process of the communication unit 352, the reflection determination processing unit 353, and the change message processing unit 354.
The communication unit 352 performs processing for monitoring the device state information held by the device state information holding unit 311 of the message management server 111 and transmitting a message for changing the device state information.

The reflection determination processing unit 353 performs processing for determining whether or not the device state information held by the device state information holding unit 311 of the message management server 111 can be changed when an update is detected as a target to be monitored by the communication unit 352. Do.
The change message processing unit 354 performs processing on a change message to be transmitted to the message management server 111.

  FIG. 3B (d) is a diagram illustrating an example of the software configuration 304 of the image forming apparatuses 121, 122, and 123. In each part of the software configuration 304, the CPU 207 of the image forming apparatus 121, 122, 123 loads a program stored in the hard disk 208 or the like of the image forming apparatus 121, 122, 123 onto the volatile memory 210 and executes it. Is realized by

The device information holding unit 361 holds state information set in the image forming apparatuses 121, 122, and 123.
Table 5 shows an example of information held by the device information holding unit 361.

The request information holding unit 362 holds request information transmitted from the relay server 112.
The communication unit 371 receives the request information transmitted from the relay server 112, and transmits the updated device information to the relay server 112.
The update request processing unit 372 performs processing on request information transmitted from the relay server 112.
The update processing unit 373 performs processing on updated device information to be transmitted to the relay server 112.

  FIG. 3C (e) shows the software configuration 305 of the client service 114. Each part of the software configuration 305 is realized by the CPU 223 of the client service 114 loading a program stored in the hard disk 224 or the like of the client service 114 onto the volatile memory 225 and executing it.

The communication unit 382 transmits the change message to the message management server 111 via the WAN.
The change message processing unit 381 performs processing on a change message to be transmitted to the message management server 111.

FIG. 4A and FIG. 4B are diagrams showing an example of data exchanged via the WAN 101 and the LAN 102.
FIG. 4A (a) is a diagram showing an example of data of the change message 401 of the individual state information transmitted from the client service 114, the relay server 112 or the monitoring server 113 to the message management server 111. As shown in FIG. The individual state information change message 401 is a message for changing the individual state information held by the device state information holding unit 311 of the message management server 111.

  The device identification information 402 indicates identification information of an image forming apparatus targeted by the individual state information held by the device state information holding unit 311 of the message management server 111. That is, the device identification information 402 is for designating an image forming apparatus to which this message is to be changed.

  The status information 403 is data indicating status information of the image forming apparatus associated with the individual status information held by the device status information holding unit 311 of the message management server 111. That is, the status information 403 indicates the individual status information that this message changes.

  The request identification information 404 is data indicating additional information that can uniquely identify the device information update request to be transmitted when the status information of the corresponding image forming apparatus is updated from the message management server 111.

  FIG. 4A (b) is a diagram showing an example of data of the change message 411 of the common state information transmitted from the client service 114 or the relay server 112 to the message management server 111. As shown in FIG. The common state information change message 411 is a message for changing the common state information held by the device state information holding unit 311 of the message management server 111.

  The common setting identification information 412 is data indicating that the image forming apparatus targeted by the common state information held by the device state information holding unit 311 of the message management server 111 is “all image forming apparatuses”. That is, the device identification information 412 is for designating a group of image forming apparatuses to which this message is to be changed.

  The state information 413 is data indicating common state information to be set, which is associated with the common state information held by the device state information holding unit 311 of the message management server 111. That is, the status information 413 indicates the common status information that this message changes.

  The request identification information 414 is data indicating additional information that can uniquely identify the device information update request transmitted from the message management server 111 when the status information of the corresponding image forming apparatus is updated.

  FIG. 4C is a view showing an example of data of the device information update request 421 transmitted from the message management server 111 to the relay server 112 or from the relay server 112 to the image forming apparatuses 121, 122, and 123. The device information update request 421 is a request (update request) for updating the information of the device information holding unit 361 of one of the image forming apparatuses 121, 122, and 123 from the message management server 111 or the relay server 112.

  The device identification information 422 is data indicating identification information of the image forming apparatus to which the device information update request 421 is to be transmitted. In the example of FIG. 4A (c), “device 0001” is described in the device identification information 422, and an example in which the device information update request 421 is an update request of an individual device is shown. However, in the device information update request 421 transmitted from the message management server 111, the device identification information 422 is described as "divisionALL", "divisionDepartmentA" or "divisionModelA", and the device information update request 421 is updated for common setting. May be a request. Even if the setting items common to a plurality of devices are collectively changed from the message management server 111 by using the update request for common setting, the relay server 112 is set to a plurality of devices in one device information update request. State information to be sent can be sent. Details will be described later.

The status information 423 is data indicating status information to be set in the image forming apparatus to which the device information update request 421 is to be transmitted.
The request identification information 424 is data indicating additional information that can uniquely identify the request when updating the status information of the corresponding image forming apparatus from the message management server 111 in response to the request from the client service 114. That is, the device information update requests 421 having the same request identification information 424 are all transmitted based on the same change message.

  FIG. 4A (d) is a diagram showing an example of data of the updated device information 431 transmitted from the image forming apparatuses 121, 122, 123 to the relay server 112. As shown in FIG. The updated device information 431 is for updating the information of the subordinate device information holding unit 332 of the relay server 112.

The device identification information 432 is data indicating identification information of the image forming apparatus that is the transmission source of the updated device information 431.
The state information 433 is data indicating the state information set in the image forming apparatus of the transmission source of the updated device information 431.

  FIG. 4B (e) is a diagram showing an example of data of the updated device information 441 transmitted from the image forming apparatuses 121, 122, 123 to the relay server 112. The updated device information 441 is updated device information including request identification information for updating the information of the subordinate device information holding unit 332 of the relay server 112.

The device identification information 442 is data indicating identification information of the image forming apparatus that is the transmission source of the updated device information 441 including the request identification information.
The state information 433 is data indicating the state information set in the image forming apparatus of the transmission source of the updated device information 441 including the request identification information.
The request identification information 444 is data indicating additional information that can uniquely identify the request when the status information of the corresponding image forming apparatus is updated from the message management server 111 in response to the request from the client service 114.

  FIG. 4B (f) is a diagram showing an example of data of the common state information change message 451 transmitted from the relay server 112 to the message management server 111. As shown in FIG. The common state information change message 451 is for changing the information of the device state information holding unit 311 of the message management server 111.

The common setting identification information 452 is data for indicating that the image forming apparatus targeted by the common state information held by the device state information holding unit 311 of the message management server 111 is “all image forming apparatuses”. .
State information 453 is omitted because it is data similar to the state information 413.
The reflection exclusion target information 454 is data indicating device identification information which is a target for which the common state information is not reflected on the device state information held by the device state information holding unit 311 of the message management server 111.
The request identification information 455 is omitted because it is the same data as the request identification information 414.

  FIG. 4B (g) is a diagram showing an example of data of the change message 461 of the common state information transmitted from the client service 114 or the relay server 112 to the message management server 111. The common state information change message 461 is for changing the information in the device state information holding unit 311 of the message management server 111.

  The common setting identification information 462 is data for indicating that the image forming apparatus targeted by the common state information held by the device state information holding unit 311 of the message management server 111 is “department-specific image forming apparatus”. is there. The information on the image forming apparatuses belonging to the department is held by the common setting identification information holding unit 333 of the relay server 112.

State information 463 is omitted because it is data similar to the state information 413.
The request identification information 464 is omitted because it is the same data as the request identification information 414.

  FIG. 4B (h) is a diagram showing an example of data of the change message 471 of the common state information transmitted from the client service 114 or the relay server 112 to the message management server 111. The common state information change message 471 is for changing the information of the device state information holding unit 311 of the message management server 111.

  The common setting identification information 472 is the “image type of image forming apparatus of the model type” targeted by the common state information held by the device state information holding unit 311 of the message management server 111 targeted by this message. It is data to show that. The information of the image forming apparatus belonging to the model is held by the common setting identification information holding unit 333 of the relay server 112.

State information 473 is omitted because it is data similar to the state information 413.
The request identification information 474 is omitted because it is the same data as the request identification information 414.

  FIG. 5 is a flowchart showing an example of processing executed when the client service 114 creates a change message for changing the information held by the device state information holding unit 311 of the message management server 111. That is, the process of FIG. 5 is realized by the CPU 223 of the client service 114 loading a program stored in the hard disk 224 or the like of the client service 114 onto the volatile memory 225 and executing the program. The client service 114 starts the process illustrated in the flowchart of FIG. 5 in response to a change request of the state information held by the device state information holding unit 311 of the message management server 111 from, for example, a Web browser or another application.

  In S501, the change message processing unit 381 specifies whether the target of the change message to be created is for individual status information or common status information. The change message processing unit 381 changes the status information common to a plurality of image forming apparatuses grouped in advance into, for example, all image forming apparatuses, by department, by machine type, etc. to “common state information”. Specifies the change message for

If a change message for the individual state information is specified in S501 (YES in S501), the change message processing unit 381 advances the process to S502.
In S502, the change message processing unit 381 creates a change message 401 of the individual state information describing the device identification information 402 to which the change message is to be applied. Note that request identification information 404 that can uniquely identify a request corresponding to the change message is added to the change message 401 of the individual state information.

If a change message for the common state information is specified (NO at S501), the change message processing unit 381 advances the process to S503.
In S503, the change message processing unit 381 creates a change message 411 of the common state information in which the common setting identification information 412 to which the change message is applied is described. Note that request identification information 414 that can uniquely identify the request corresponding to the change message is added to the change message 411 of the common state information.

  When the change message is generated in S502 or S503, the communication unit 382 transmits the change message generated in S502 or S503 to the message management server 111 in S504, and ends the processing of this flowchart. .

  As described above, according to the process in FIG. 5, the client service 114 can create one change message for collectively changing common setting items of a plurality of devices.

  FIG. 6 is a flowchart showing an example of processing executed by the control unit 321 when the message management server 111 receives a change message from the client service 114. That is, the process of FIG. 6 is realized by the CPU 223 of the message management server 111 loading a program stored in the hard disk 224 or the like of the message management server 111 onto the volatile memory 225 and executing the program.

In step S601, when the communication unit 322 receives a change message (for example, 401 or 411) from the client service 114, the process transitions to step S602.
In step S602, the state information operation unit 323 determines whether the target of the change message received in step S601 is a change message of the individual state information or a change message of the common state information. In this determination process, it is checked whether the device identification information described in the change message designates the identification information of the individual device or the identification information of the common state information.

  If it is determined in S602 that the received change message designates identification information of an individual device (YES in S602), the state information operation unit 323 advances the process to S603.

  In S603, the state information operation unit 323 acquires the device identification information 402 described in the change message 401 of the individual state information received in S601. Based on the acquired device identification information 402, the state information operation unit 323 specifies the state information held by the device state information holding unit 311 of the message management server 111 as shown in Table 1, and the change acquired in S601 above Update individual status information using messages. Thereafter, the state information operation unit 323 advances the process to S605.

  On the other hand, when it is determined in S602 that the received change message designates identification information for common setting (NO in S602), the state information operation unit 323 advances the process to S604.

  In S604, the state information operation unit 323 acquires the common setting identification information 412 described in the change message 411 of the common state information received in S601. Based on the acquired device identification information 412, the state information operation unit 323 specifies the common state information held by the device state information holding unit 311 of the message management server 111, and uses the change message acquired in S601 above. Update common state information. Thereafter, the state information operation unit 323 advances the process to S605.

  In step S605, the state information operation unit 323 determines the transmission source of the change message. In this determination process, it is checked whether the change message contains request identification information.

  If the change message includes request identification information, the state information operation unit 323 determines that the transmission source of the change message is the client service 114 (YES in S605), and the process proceeds to S606. In this case, the process proceeds to the process of transmitting information for changing the state information of the image forming apparatus.

In step S606, the status information operation unit 323 acquires device status information and device status information history information as shown in Table 1 linked with the device identification information acquired in the above-described S603 or S604, and detects a change difference.
Next, in step S607, the state information operation unit 323 uses the change difference information of the state information detected in step S606 and the device identification information acquired in step S603 or S604 to update the device information update request 421 including request identification information. create.
Next, in step S608, the communication unit 322 transmits the device information update request 421 created in step S607 to the relay server 112, and ends the processing of this flowchart.

  On the other hand, when the change message does not include the request identification information in S605, the state information operation unit 323 determines that the transmission source of the change message is the relay server (NO in S605). In this case, the status information operation unit 323 determines that reflection of status information on the image forming apparatus with respect to the device status information holding unit 311 of the message management server 111 is completed, and ends the processing of this flowchart.

  As described above, according to the process of FIG. 6, when changing common setting items of a plurality of devices from the message management server 111 at one time, the relay server 112 should be set to a plurality of devices in one device information update request. Status information can be sent.

  FIG. 7 is a flowchart showing an example of processing executed by the control unit 341 when the relay server 112 receives the device information update request 421 transmitted from the message management server 111. That is, the process of FIG. 7 is realized by the CPU 223 of the relay server 112 loading a program stored in the hard disk 224 or the like of the relay server 112 onto the volatile memory 225 and executing the program.

In S701, when the communication unit 342 receives the device information update request 421 from the message management server 111, the communication unit 342 holds the request in the request information holding unit 331.
Next, in S702, the update request processing unit 343 checks the device identification information 422 included in the device information update request 421 received in S701, and determines a device to be updated. In the determination process, it is checked whether the device identification information 422 included in the device information update request 421 designates identification information of an individual device or designation of identification information for common setting.

When the update request processing unit 343 determines that the identification information of the individual device is specified in the above-described S702 (in the case of YES in S702), the process transitions to S703.
In step S703, the communication unit 342 transmits the device information update request 421 to the image forming apparatus of the device identification information 422 included in the device information update request 421 confirmed in step S702, and ends the processing of this flowchart.

On the other hand, if the update request processing unit 343 determines in step S702 that identification information for common setting is designated (in the case of NO in step S702), the process transitions to step S704.
In step S704, the communication unit 342 transmits the device information update request 421 to all the image forming apparatuses corresponding to the identification information for common setting described above, in which the relay server 112 transmits and receives data via the LAN. Do. The target for transmitting the device information update request 421 refers to the identification information for common setting as shown in Table 4 to specify the target image forming apparatus.

  Next, in step S705, the communication unit 342 does not receive the device information update request 421 transmitted from the relay server 112 in step S704, and determines whether there is an image forming apparatus that failed in communication. If the communication unit 342 determines that there is an image forming apparatus that has failed in communication (YES in step S705), the process advances to step S706.

  In step S706, the update request processing unit 343 registers the device identification information of the image forming apparatus confirmed in step S705 in the reflection exclusion target illustrated in Table 2. At the time of registration, the request identification information 424 included in the device information update request 421 received in S701 is associated with the request identification information 424 and registered. After the process of S706, the update request processing unit 343 ends the process of this flowchart.

  On the other hand, when the communication unit 342 determines that there is no image forming apparatus that has failed in communication (in the case of NO in S705), the processing of this flowchart ends.

  As described above, according to the process in FIG. 7, when collectively changing setting items common to a plurality of devices from the message management server 111, it becomes an object based on one device information update request received from the message management server 111. Device information of each device can be updated.

  FIG. 8 is a flowchart illustrating an example of processing executed when the device information update request 421 transmitted from the relay server 112 is received by the image forming apparatuses 121, 122, and 123. That is, the CPU 207 of the image forming apparatus 121, 122, 123 loads the program stored in the hard disk 208 or the like of the image forming apparatus 121, 122, 123 onto the volatile memory 210 and executes the processing of FIG. It is realized by doing.

In S801, when the communication unit 371 receives the device information update request 421 transmitted from the relay server 112, the process transitions to S802.
In S802, the update request processing unit 372 updates the information in the device information holding unit 361 as shown in Table 5 using the status information 423 of the device information update request 421 received in S801.

Next, in S803, the update processing unit 373 confirms the updated information of the device information holding unit 361.
In S804, the update processing unit 373 determines whether the update information confirmed in S803 is the information updated by the device information update request 421. In this determination process, the update information confirmed in S <b> 803 is compared with the state information 423 included in the device information update request 421 stored in the request information storage unit 362. Then, if the comparison results match, it is determined that the information is updated by the device information update request 421. If the comparison results do not match, the information is not updated by the device information update request 421. judge.

  If it is determined in S804 that the update information confirmed in S803 is the information updated by the device information update request 421 (YES in S804), the update processing unit 373 advances the process to S805.

  In step S805, the update processing unit 373 creates the updated device information 441 including the request identification information, using the update information confirmed in step S803 and the request identification information 424 included in the device information update request 421. After creation, the communication unit 371 transmits the updated device information 441 including the request identification information to the relay server 112, and ends the processing of this flowchart.

  On the other hand, if it is determined in S804 that the update information confirmed in S803 is not the information updated by the device information update request 421 (NO in S804), the update processing unit 373 advances the process to S806.

  In S806, the update processing unit 373 creates the updated device information 431 using the update information confirmed in S803. After creation, the communication unit 371 transmits the updated device information 431 to the relay server 112, and ends the processing of this flowchart.

  As described above, according to the process of FIG. 8, when the device information is updated based on the device information update request received from the relay server 112, the updated device information including the identification information of the request is transmitted to the relay server 112. Can.

  FIG. 9 is a flowchart illustrating an example of processing executed by the control unit 341 when the relay server 112 receives updated device information transmitted from the image forming apparatuses 121, 122, and 123. That is, the processing of FIG. 9 is realized by the CPU 223 of the relay server 112 loading a program stored in the hard disk 224 or the like of the relay server 112 onto the volatile memory 225 and executing the program.

  In S901, when the communication unit 342 receives the updated device information transmitted from the image forming apparatus 121, 122, 123, the updated device information processing unit 344 updates the information of the subordinate device information holding unit 332 as shown in Table 3. Do. That is, the update device information processing unit 344 updates the setting information held by itself according to the update device information from the image forming apparatus.

  Next, in step S902, the update device information processing unit 344 determines whether the update device information received in step S901 includes request identification information. If it is determined that the updated device information includes request identification information (YES in step S902), the process advances to step S903.

  In S903, the update device information processing unit 344 updates the information held by the request information holding unit 331 as shown in Table 2 using the update device information received in S901. For example, among the device identification information described in the update waiting device information linked to the request identification information, only the device identification information included in the update device information received in S901 is deleted and updated.

  Next, in S904, the update device information processing unit 344 confirms the presence or absence of update waiting device information associated with the request identification information confirmed in S902, which is held in the request information holding unit 331 as shown in Table 2. If it is determined that there is a device that has not been updated among the devices targeted by the device status update request (in the case of NO in S904), the updated device information processing unit 344 ends the processing of this flowchart.

  On the other hand, if it is determined in S904 that all devices targeted by the device state update request have been updated (YES in S904), the updated device information processing unit 344 advances the process to S905.

  In step S905, the updated device information processing unit 344 determines whether the request identification information confirmed in step S902 designates identification information for common setting. If it is determined that identification information for common setting is designated (in the case of YES in S905), the updated device information processing unit 344 advances the process to S906.

  In S906, the change message processing unit 345 creates the change message 411 or 451 of the common state information describing the common setting identification information 412 to which the change message is to be applied, using the update device information received in S901. . At the time of creation, the reflection exclusion target columns of the request information holding unit 331 as shown in Table 2 attached to the request identification information of the updated device information received in S901 are confirmed. When the device identification information is described in the reflection exclusion target column, it is additionally written as the reflection exclusion target information 454 in the change message of the common state information. After creation, the communication unit 342 transmits the common state information change message 451 including the common state information change message 411 or the reflection exclusion target information 454 to the message management server 111, and ends the processing of this flowchart. The common status information change message 451 transmitted in S906 is notified collectively to the message management server 111 that the status information of the plurality of devices has been updated according to the device information update request received in S701 of FIG. 7. It is to do.

On the other hand, when it is determined in S905 that identification information of the individual device is designated (in the case of NO in S905), the update device information processing unit 344 advances the process to S907.
In S 907, the change message processing unit 345 creates a change message 401 of the individual state information describing the device identification information 402 to which the change message is to be applied, using the updated device information received in S 901. After creation, the communication unit 342 transmits the change message 401 of the individual state information to the message management server 111, and ends the processing of this flowchart.

  If it is determined in S902 that the updated device information received in S901 does not include request identification information (NO in S902), the updated device information processing unit 344 advances the process to S908.

  In step S908, the update device information processing unit 344 determines whether there is a device information update request waiting for update, which is associated with the device identification information included in the update device information received in step S901. In this determination process, it is checked whether the device identification information included in the updated device information received in S901 is described in the update waiting device information column of the request information holding unit 331 as shown in Table 2. If it is described, it is determined that there is a device information update request waiting for update attached to the device identification information included in the updated device information (YES in S908). On the other hand, if not described, it is determined that there is no device information update request waiting for update attached to the device identification information included in the updated device information (NO in S908).

In the case of YES at S908, the update device information processing unit 344 makes a transition to S909 and implements a response because there is a conflict between the change request from the client service and the change from the device.
In step S909, the update device information processing unit 344 writes and updates the device identification information included in the update device information received in step S901 in the same reflection exclusion target column in the update waiting device information column detected in step S908. Proceed with the process.

  If it is determined in S908 that there is no device information update request waiting for updating associated with the device identification information included in the updated device information received in S901 (if NO in S908), the updated device information processing unit 344 The processing proceeds to step S910.

In S910, the change message processing unit 345 creates a change message 401 of the individual state information describing the device identification information 402 to which the change message is to be applied, using the updated device information received in S901. After creation, the communication unit 342 transmits the change message 401 of the individual state information to the message management server 111, and ends the processing of this flowchart.
Note that the processing of the message management server 111 that processes the transmitted change message is the same as the processing of S601 to S608, and thus is omitted.

  As described above, according to the process of FIG. 9, when the state information of each device is updated based on the change message for collectively changing the common setting items of the devices to be managed, the state information of each device is It is possible to transmit, to the message management server 111, one change message for collectively returning the update to the information held by the message management server 111.

  FIG. 10 is a flowchart showing an example of processing executed when the relay server 112 changes the common state information held in the device state information holding unit 311 of the message management server 111 in the monitoring server 113. . That is, the process of FIG. 10 is realized by the CPU 223 of the monitoring server 113 loading a program stored in the hard disk 224 or the like of the monitoring server 113 onto the volatile memory 225 and executing the program.

In S1001, the communication unit 352 monitors the common state information held by the device state information holding unit 311 of the message management server 111.
Next, in step S1002, the communication unit 352 determines whether the relay server 112 has changed the common state information monitored in step S1001. In this determination process, the state is periodically monitored using a means such as polling for the monitoring target. Then, when the changer is the relay server 112 and the change date and time and the version have been updated since the previous polling, it is determined that the change has been made.

  If the communication unit 352 determines in step S1002 that the common state information to be monitored is not changed by the relay server 112 (in the case of NO in step S1002), the processing of this flowchart ends.

  On the other hand, if the communication unit 352 determines in step S1002 that the common state information to be monitored has been changed by the relay server 112 (YES in step S1002), the process transitions to step S1003.

  In S1003, the reflection determination processing unit 353 determines whether the reflection exclusion target information is described in the device state information of the common state information monitored in S1001. If the reflection determination processing unit 353 determines that the reflection exclusion target information is described in the device state information of the monitoring target common state information (in the case of YES in S1003), the processing transitions to S1004.

  In S1004, the change message processing unit 354 excludes all the device identification information described in the reflection exclusion target information confirmed in S1003 and the device identification information of the common state information, and corresponds to the device identification information of the common state information. Send a message to change the individual status information of. The information to be transmitted refers to the device state information of the common state information, and creates a change message 401 for each individual state information. After transmitting the change message 401 of the individual state information, the change message processing unit 354 ends the process of this flowchart.

  When the reflection determination processing unit 353 determines that the reflection exclusion target information is not described in the device state information of the monitoring target common state information in S1003 (in the case of NO in S1003), the processing transitions to S1005.

  In S1005, the change message processing unit 354 transmits a message for changing all the individual status information corresponding to the device identification information of the common status information except the device identification information of the common status information. The information to be transmitted refers to the device state information of the common state information, and creates a change message 401 for each individual state information. After transmitting the change message 401 of the individual state information, the change message processing unit 354 ends the process of this flowchart.

  As described above, according to the process of FIG. 10, it is possible to detect a change from the relay server 112 of the common state information held by the message management server 111 and reflect the change in the individual state information of each device held by the message management server 111. .

  As described above, in the present embodiment, the management system (such as the message management server 111) on the cloud and the management apparatus (the relay server 112) in the intranet cooperate with each other to provide network devices (such as the image forming apparatuses 121 to 123). It can manage state information. When common settings are applied to a plurality of devices, only the common parameter information is exchanged between the management system and the relay server, and the relay server 112 interprets the information, and the state of the plurality of devices held in the intranet Apply to information. Also when reflecting that the state information has been changed in the management system on the cloud, it applies to a plurality of devices held on the cloud in the same way. And, with such a configuration, it is possible to appropriately manage the network devices in the internal network such as the intranet with a management system existing outside on the cloud etc. while suppressing the communication load between the external and the internal network. . For example, also when setting common parameters (common state information) for a plurality of network devices, communication between the management apparatus and the internal network is performed collectively. This makes it possible to change common parameters and reflect them on the management device while suppressing an increase in network load between the network where the network device is present and the outside. That is, even when managing the network device from the outside of the network where the network device exists, it is possible to suppress the increase in the communication load between the network and the outside and appropriately manage it.

In the above-described embodiment, the message management server 111, the monitoring server 113, and the client service 114 communicate with each other via the WAN, but they exist under the same network and communicate via the LAN. It is also good.
Further, in the above-described embodiment, the message management server 111 and the relay server 112 have a one-to-one configuration. However, even when the message management server 111 and the relay server 112 have a one-to-many configuration, the device management system can be realized by the same method.

  Furthermore, in the above-described embodiment, information for specifying all the image forming apparatuses is set in the identification information for common setting. However, as shown in FIG. 4B (g) and FIG. 4B (h), even if a group unit such as a department or a model is specified, the device management system can be realized by the same method.

In addition, the structure of the various data mentioned above and its content are not limited to this, According to a use or the objective, you may be comprised by various structure or content.
Although the embodiment has been described above, the present invention can be embodied as, for example, a system, an apparatus, a method, a program, or a storage medium. Specifically, the present invention may be applied to a system constituted by a plurality of devices, or may be applied to an apparatus comprising a single device.
Further, all the configurations obtained by combining the above-described embodiments are also included in the present invention.

(Other embodiments)
The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or storage medium, and one or more processors in a computer of the system or apparatus read and execute the program. Can also be realized. It can also be implemented by a circuit (eg, an ASIC) that implements one or more functions.
Further, the present invention may be applied to a system constituted by a plurality of devices or to an apparatus comprising a single device.
The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the respective embodiments) are possible based on the spirit of the present invention, which are excluded from the scope of the present invention is not. That is, the configuration in which each of the above-described embodiments and their modifications are combined is also included in the present invention.

Claims (8)

Relay device that holds setting information of each of a plurality of network devices to be monitored in synchronization with the device body, and setting information of each of the network devices can be held in synchronization with the device body via the relay device A management system, and
The management system separately holds, as setting information for common setting, setting information commonly set among a plurality of apparatuses among setting information for each of the apparatuses,
A changing unit that changes the setting information for the common setting when collectively changing setting information common to a plurality of devices of the device body;
Request means for transmitting, to the relay apparatus, a specific update request for collectively updating setting information of device bodies of a plurality of network devices in response to the change when the setting information for the common setting is changed; ,
Updating means for changing the setting information for the common setting according to a specific notification from the relay device;
The change of the setting information for common setting is monitored, and when the change is detected, the setting information for each device corresponding to the changed setting information for common setting held in the holding unit is changed. Means, and
The relay device is
It interprets the specific update request, updates the setting information of the device main bodies of the plurality of network devices requested to be changed by the specific update request, and holds it by itself according to the update information from each of the network devices Synchronization means for updating the setting information
And notification means for transmitting to the management system a specific notification for collectively notifying the management system that the setting information of the plurality of network devices has been updated in response to the specific update request.
A system characterized by   The system according to claim 1, wherein the relay device and the plurality of network devices to be monitored are provided in the same network, and the management system is provided outside the network. The relay device excludes, as a device targeted for exclusion of the specific update request, among the network devices for which the synchronization unit updates the setting information of the device body in response to the specific update request, the device for which the update has failed. Have a means,
The notification means includes, in the specific notification, information indicating the device to be excluded.
The monitoring unit excludes the exclusion target device included in the specific notification that is the basis of the change in the detected common setting setting information, and corresponds to each device corresponding to the changed common setting setting information. The system according to claim 1 or 2, wherein the setting information of is changed.   When the network device for which the synchronization means is to update the setting information of the device body is included in the network device to be updated by a specific update request waiting for update, the exclusion means performs the specific update of the network device. The system according to claim 3, characterized in that the device is a request exclusion target.   The system according to any one of claims 1 to 4, wherein the setting information for common setting is setting information that is commonly set to all network devices monitored by the relay apparatus.   The system according to any one of claims 1 to 4, wherein the setting information for common setting is setting information commonly set among a plurality of network devices grouped in advance.   The system according to claim 6, wherein the grouping includes at least a type of network device or a division by section linked to the network device. Relay device that holds setting information of each of a plurality of network devices to be monitored in synchronization with the device body, and setting information of each of the network devices can be held in synchronization with the device body via the relay device A device management method in a system having a management system,
The management system further includes holding means for separately holding, as setting information for common setting, setting information commonly set among a plurality of devices among setting information for each of the devices.
Executed by the management system
When collectively changing setting information common to a plurality of devices in the device body, a changing step of changing the setting information for the common setting;
A request step of transmitting, to the relay apparatus, a specific update request for collectively updating setting information of device bodies of a plurality of network devices in response to the change when the setting information for common setting is changed; , And, and
Executed by the relay device
It interprets the specific update request, updates the setting information of the device main bodies of the plurality of network devices requested to be changed by the specific update request, and holds it by itself according to the update information from each of the network devices Synchronization step of updating the setting information
And transmitting, to the management system, a specific notification for collectively notifying the management system that the setting information of the plurality of network devices has been updated in response to the specific update request.
Furthermore, executed by the management system
An updating step of changing the setting information for the common setting according to a specific notification from the relay device;
The change of the setting information for common setting is monitored, and when the change is detected, the setting information for each device corresponding to the changed setting information for common setting held in the holding unit is changed. Step and
A device management method comprising:

Images