JP2012168610A - Management system, management device, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce wasted time until a power-off and power consumption consumed during the time without resetting a power-off timer provided in a network apparatus.SOLUTION: A management device 101 generates (601) a task with a reboot of a network apparatus 102 according to a setting or the like from a manager 600. When a power-off timer is started, the network apparatus 102 notifies (603) the management device 101 to start a power-off timer. According to the notification to start the power-off timer (S700), the management device 101 sets (604) a task that is generated with the network apparatus 102 performing the notification defined as an object, not to reboot the network apparatus 102 with the execution of the task (S708). Responding to the execution (605) of the task generated according to the notification, by the management device 101, the network apparatus 102 performs a process required by the task without rebooting.

Description

  The present invention relates to control of a management system including a network device and a management device that manages the network device.

  Network devices such as printers and multi-function devices that have a function to transition the network device to a standby state (also called a power-saving state or sleep state) or a power-off state when a predetermined time or a predetermined time elapses There is.

  For example, there is a network device that automatically turns off when a certain time set by the network device administrator elapses from the time when the network device is in a standby state. A timer (hereinafter referred to as “power-off timer” or simply “timer”) is used for power-off due to elapsed time.

  This timer may be reset when the state transitions from the standby state to the normal operation state or when the network device is restarted. The setting of the time for turning off the power and the elapsed time are registered in the network device by the administrator of the network device.

  These network devices are managed by a management device. Some management devices can distribute firmware and other programs to network devices to be managed, and by scheduling program distribution processing, temporary processing and periodic processing can be executed at specified times. There are also things.

  When scheduling a process by an administrator of a network device or management apparatus, the process may be registered after the power-off time set for the network device. In such a case, since the network device is in a power-off state, the network device and the management device cannot execute the scheduled processing.

  Patent Document 1 is cited as a technique for avoiding this problem and for reducing the effort of re-registering the process. Japanese Patent Application Laid-Open No. 2004-228561 automatically reschedules a process when the registered process completion time has passed the power-off time, and completes the process before the power-off.

  Some programs such as firmware to be distributed by the management apparatus request restart of the network device in order to reflect the setting. In addition to the program, there are items such as network settings that require restart of the network device depending on the setting items. In a management apparatus, when distribution of a program that requires restart is scheduled, a method of executing program distribution / setting processing and network device restart at a specified time is generally used.

JP 2010-004335 A

  However, as described above, the management device that manages the network device having the power-off timer and distributes the program that needs to be restarted. The management device also distributes the program before the power-off time by the power-off timer. Processing may be executed.

  In this case, restart occurs due to the program distribution process, and the power-off timer is reset. For this reason, the network device consumes power wastefully only for the time until it again enters the standby state and the time until the power is turned off by the power-off timer.

  The present invention has been made to solve the above problems. An object of the present invention is to reduce wasteful time until power-off and wasteful power consumption consumed during that time without resetting the power-off timer of the network device, and to execute processing appropriately. It is to provide a mechanism that can do.

  The present invention is a management system including a network device and a management device that manages the network device, wherein the management device generates a task that involves restarting the network device, and the generation unit An execution means for executing the task generated in step (b), and a reception means for receiving a notification for specifying a shutdown timing of the network device, wherein the network device sends the network to the management device. Notification means for performing notification for specifying the time of shutdown of the device, and processing means for performing processing required by the task executed in the management device, and the generation means, according to the notification, The network device does not restart when the task generated for the notified network device is executed The processing means performs the processing requested by the task without restarting when the task generated by the generating means is executed by the management device according to the notification. And

  According to the present invention, without resetting the power-off timer of the network device, it is possible to reduce wasteful time until power-off and wasteful power consumption consumed during that time, and execute processing appropriately. Can do.

It is a figure which shows an example of the whole structure of the management system of the network apparatus which shows one Example of this invention. 3 is a block diagram illustrating an example of a hardware configuration of a management apparatus 101 and a client apparatus 103. FIG. 3 is a block diagram illustrating an example of a software configuration of a management apparatus 101. FIG. 2 is a diagram illustrating an example of a hardware configuration of a network device 102. FIG. 2 is a block diagram illustrating an example of a software configuration of a network device 102. FIG. It is a sequence diagram which shows the flow of the main processes in Example 1. FIG. 7 is a flowchart showing details of a task resetting process (604) in FIG. 6 according to the first embodiment. It is a figure which shows an example of the change notification of S709 of FIG. FIG. 10 is a sequence diagram illustrating a main processing flow in the second embodiment. 10 is a flowchart showing a detailed operation of the task management module 303 of the management apparatus 101 at 608 in FIG. 9. 7 is a flowchart showing details of a task resetting process (604) of FIG. 6 in Embodiment 3. It is a figure which shows an example of the change notification of S709 of FIG. 12 is a flowchart showing details of a task rescheduling process (S712) in FIG. 11;

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

FIG. 1 is a diagram showing an example of the overall configuration of a network device management system according to an embodiment of the present invention.
As illustrated in FIG. 1, the management system according to the present exemplary embodiment includes a management device 101, a network device 102, and a client device 103 that are connected to each other via a network 100.

  The management device 101 is a device for managing the network device 102. In addition, the management apparatus 101 and the client apparatus 103 are configured to be included in a general personal computer.

  The network device 102 is connected to the management apparatus 101 via the network 100. The network device 102 is an MFP (Multifunction Peripheral), a printer, a FAX, or the like, and indicates a device that can be managed by the management apparatus 101. In FIG. 1, the network 100 to which the management apparatus 101, the network device 102, and the client apparatus 103 are connected may be the Internet or an intranet. Further, an arbitrary number of management apparatuses 101, network devices 102, and client apparatuses 103 may be connected to the network 100.

Hereinafter, the hardware configuration and the software configuration of each device constituting the management system of the present embodiment will be described with reference to FIGS.
FIG. 2 is a block diagram illustrating an example of a hardware configuration of the management apparatus 101 and the client apparatus 103.
In FIG. 2, a system bus 200 is a common data exchange path between components constituting the computer. A CPU (Central Processing Unit) 201 is a device that controls the entire computer, performs arithmetic processing, and the like. A RAM (Random Access Memory) 202 indicates an area in which a program and data are stored and executed when processing is performed. A ROM (Read Only Memory) 203 is an area in which a program such as a system startup program is stored so as to be readable by a computer.

  A DKC (Disk Controller) 204 controls an external storage device such as an HD (Hard Disk) 205 and an SSD (Solid State Drive). The HD 205 stores programs and data in a computer-readable manner, and can load programs and data into the RAM 202 and the HD 205 as needed. Instead of the HD 205, an SSD or other external storage device may be used.

  A network I / F 206 is connected to the network 100 and performs network communication. The input / output I / F 207 is connected to a keyboard, a mouse, a display, etc. (not shown), and inputs / outputs data.

  The management apparatus 101 and the client apparatus 103 operate in a state where the CPU 201 is executing the basic I / O program and the OS. The basic I / O program is stored in the ROM 203, and the OS is stored in the HD 205. When the computer is turned on, the OS is loaded from the HD 205 to the RAM 202 by the initial program load function in the basic I / O program and executed by the CPU 201 to start the operation of the OS.

FIG. 3 is a block diagram illustrating an example of the software configuration of the management apparatus 101.
As shown in FIG. 3, the software of the management apparatus 101 includes a network module 300, a Web service 301, a device management module 302, a task management module 303, and a database 304. The software configuration in FIG. 3 is stored as a program in the HD 205 of the management apparatus 101, and is realized by the CPU 201 of the management apparatus 101 executing the program. That is, a program for causing a computer having the hardware configuration shown in FIG. 2 to function with the software configuration shown in FIG. 3 is recorded in the HD 205 of the management apparatus 101 so as to be readable by the computer.

  The network module 300 communicates with the network device 102 and the client device 103 connected via the network 100. When the Web service 301 receives a GET request based on HTTP (Hypertext Transfer Protocol) from the Web browser of the client apparatus 103, the Web service 301 provides a service for returning Web page data stored in the HD 205. In addition, although demonstrated by the communication by HTTP here, other communication protocols, such as HTTPS (HTPPS over Secure Socket Layer) and FTP (File Transfer Protocol), may be utilized and it is not limited to HTTP. Further, the request received by the Web service 301 is not limited to the request from the client device 103, and may be a request from an environment where the Web service 301 can be used.

  The device management module 302 is a module that executes processing for managing the network device 102 (hereinafter referred to as a task). For example, there are a task for confirming the operation state of the network device 102 and saving the confirmation result in the database 304, and a task for requesting and executing the network device 102 for restart.

  The task management module 303 is a module capable of rewriting the above-described task generation, task scheduling, and task content. For example, it is possible to schedule whether to execute a task at 0 o'clock every day, or to control whether or not to execute these processes in a task involving restart or power-off. Information regarding task scheduling is stored in the database 304.

  As described above, the device management module 302 and the task management module 303 realize a Web application that manages the network device 102 together with the Web service 301. Note that the application is not limited to a Web application, and may be a native application.

  The database 304 stores information on the network device 102, information acquired by the device management module 302, task information by the task management module 303, and the like. The database 304 may be on a device different from the management apparatus 101 as long as it can be accessed from the device management module 302 or the task management module.

FIG. 4 is a diagram illustrating an example of a hardware configuration of the network device 102, and here, an example of an MFP is illustrated.
As illustrated in FIG. 4, the network device 102 includes a control unit 400, an operation unit 401, a printer 402, and a scanner 403.
The configuration related to the operation unit of the control unit 400 includes a CPU 410, a RAM 411, an operation unit I / F 412, a Network I / F 413, a ROM 414, a DKC 415, an HD 416, an Image Bus I / F 417, and a system bus 418. The printing / scanning configuration of the control unit 400 includes an image bus 419, a scanner image processing unit 420, a printer image processing unit 421, a RIP 422, and a device I / F 423.

  The CPU 410 is a controller for controlling the entire control unit 400. The RAM 411 is an image memory for temporarily storing image data. The operation unit I / F 412 is an interface with the operation unit 401, and outputs image data to be displayed on the operation unit 401 to the operation unit 401. Further, it has a role of transmitting information input by the user through the operation unit 401 to the CPU 410.

  The network I / F 413 is an interface that is connected to the network 100 and exchanges information with an external device via the network 100. The network I / F 413 includes a management information base (MIB) that stores various types of information about the network device 102. The various information possessed by the MIB indicates information such as the IP address, the name of the network device, and the status.

  The ROM 414 is a boot ROM, in which a system boot program is recorded so as to be readable by a computer. The DKC 415 controls an external storage device such as an HD 416 or an SSD. The HD 416 is an external storage device and records system software and image data so that they can be read by a computer. Note that another external storage device such as an SSD may be used instead of the HD 416.

  The Image Bus I / F 417 is a bus bridge that connects the system bus 418 and the image bus 419 and performs data conversion. The system bus 418 is a common data exchange path between components constituting the control unit 400.

  The image bus 419 is configured by a PCI bus or IEEE1394, and is a path for transferring image data at high speed. A scanner image processing unit 420 corrects, processes, and edits an input image. The printer image processing unit 421 performs correction according to the performance of the printer, resolution conversion, and the like on the print output image data.

  A RIP (Raster Image Processor) 422 expands a PDL (Page Description Language) command sent from the network 100 into a bitmap image. The device I / F 423 connects the printer 402 and the scanner 403, which are image input / output devices, and the control unit 400, and converts image data.

  When the network device 102 is turned on, the system software is loaded from the HD 416 to the RAM 411 by the load function in the boot program in the ROM 414 and executed by the CPU 410, and various functions of the network device can be used.

FIG. 5 is a block diagram illustrating an example of a software configuration of the network device 102.
As shown in FIG. 5, the software configuration of the network device 102 includes a network module 500 and a management module 501.
The network module 500 serves as an interface with external devices (management device 101 and client device 103) connected to the network 100. For example, a device information acquisition request for a network device is received from the management apparatus 101 and the request is transmitted to the management module 501. Examples of communication with the management apparatus 101 include communication using SNMP (Simple Network Management Protocol) and communication using SOAP (Simple Object Access Protocol) messages. The network module 500 receives device information from the management module 501 and responds to the management apparatus 101 via the network 100.

  The management module 501 is a module for performing an internal operation of the network device 102, and includes a task execution module 502, an information management module 503, and a state monitoring module 504.

  The task execution module 502 is a module for executing a task set by an administrator of the management apparatus 101 or the network device 102. For example, when a restart request for the network device 102 is received from the management apparatus 101, the task execution module 502 interprets the restart request and executes internal processing necessary for the restart.

  The information management module 503 is a module that manages information (name, IP address, power-off timer setting value, etc.) set in the network device 102. Specifically, the setting information of the network device 102 can be returned in response to a device setting information acquisition request from the management apparatus 101 or the like.

  The state monitoring module 504 is a module that monitors whether the network device 102 is operating normally, whether it is in a standby state (also referred to as a power saving state or a sleep state), or in an error state. is there. For example, when the network device 102 transitions from the normal operation state to the standby state, the state monitoring module 504 can notify the management apparatus 101 that the state has changed. In addition, when the network device 102 transitions from the normal operation state to the standby state, the state monitoring module 504 starts a power-off timer for the network device 102 in the state monitoring module 504. Furthermore, the state monitoring module 504 notifies the management apparatus 101 that the network device 102 has shifted to the sleep state and has started the power-off timer as a notification for specifying the time of power-off (shutdown) of the network device 102. Notice. When the timer time (time set for each network device) is reached, the state monitoring module 504 can make the task execution module 502 request and execute a power-off task.

  Information representative of device information of the network device 102 is stored in the HD 416. Further, the information on the network device 102 may be managed by a database although not shown in FIG. Furthermore, the power-off timer may be a separate module from the state monitoring module 504.

  FIG. 6 is a sequence diagram illustrating a main processing flow in the first embodiment. In FIG. 6, a firmware update task will be described as an example of task processing. The firmware update task refers to a process for updating firmware incorporated in the network device 102 to another firmware. The firmware update task needs to restart the network device 102 in order to reflect the newly incorporated firmware setting. The processing of the management apparatus 101 in FIG. 6 is realized by the CPU 201 of the management apparatus 101 executing a program recorded in the HD 205 so as to be readable by a computer. Further, the processing of the network device 102 in FIG. 6 is realized by the CPU 410 of the network device 102 executing a program recorded in the HD 416 so that it can be read by a computer. Reference numerals 601 to 607 denote steps.

  In FIG. 6, first, the firmware update task is set by the administrator 600 of the management apparatus 101 (601). In the task setting 601, which firmware is to be updated for which network device is set in the management apparatus 101. This task setting function is provided by the Web service 301 and the task management module 303 of the management apparatus 101. The administrator 600 accesses the Web service of the management apparatus 101 from the Web browser of the client apparatus 103, and performs task setting operations on the Web browser of the client apparatus 103. In response to this operation, a task setting request is transmitted from the Web browser of the client apparatus 103 to the Web service 301 of the management apparatus 101 and passed to the task management module 303. The task management module 303 sets a task in response to the task setting request (generates a task and registers it in the database 304). Note that task settings are not limited to settings from an administrator. For example, a configuration in which tasks are set from a server or the like installed at a manufacturer or a sales company via a network such as the Internet may be used.

  When the task setting is completed in the task management module 303, the Web service 301 transmits a task setting completion notification to the Web browser of the client apparatus 103 that has requested the task setting (602). That is, a task setting completion notification is sent to the administrator 600 who set the task.

  After the task setting (601) by the administrator 600 is completed, the power-off timer is started from the state monitoring module 504 of the network device 102 that is the target of the task before the execution time of the task set in 601 When the information is notified to the management apparatus 101 (603), the task management module 303 of the management apparatus 101 performs the task resetting process (FIG. 7) (604).

  The power-off timer is activated by the state monitoring module 504 when the network device 102 enters a standby state. In the task resetting process 604, as shown in detail in FIG. 7, it is determined whether or not the network device is restarted, and the task setting is changed according to the determination result. For example, in the case of resetting the firmware update task, when the power-off timer is activated, the firmware update task is changed to a setting that does not perform the reboot required for the firmware update task.

  When the execution time of the task set in 601 and / or reset in 604 is reached, the task management module 303 requests the device management module 302 of the management apparatus 101 to execute the task ( 605). For example, a task for updating the firmware of the network device 102 is executed. In the case of this task, the device management module 302 of the management apparatus 101 transmits firmware to be updated to the network device 102 and requests firmware update. In response to this request, the task execution module 502 of the network device 102 executes a process (task) for updating the firmware using the firmware received from the management apparatus 101.

  When task execution by the task execution module 502 of the network device 102 is completed, the task execution module 502 notifies the management apparatus 101 of execution completion (606). The task execution module 502 also notifies the administrator 600 of execution completion (607). Note that the execution completion notification in 607 may be notified from the management apparatus 101 that has received the execution completion notification in 606, instead of being notified from the network device 102. Further, the notification of completion of execution to the administrator 600 in 607 may be a pop-up display on the screen of the display device of the client device 103 of the administrator 600, or a mail to the mail address of the administrator 600 registered in advance. Notifications may be used. Moreover, the structure which does not perform execution completion notification of 606,607 may be sufficient.

  FIG. 7 is a flowchart illustrating details of the task resetting process (604) in FIG. 6 according to the first embodiment. This process is mainly performed by the task management module 303 of the management apparatus 101. That is, the processing in FIG. 7 is realized by the CPU 201 of the management apparatus 101 executing a program recorded in the HD 205 so as to be readable by a computer.

  In addition, this process described the reset process about the task which applies firmware (program) to the network apparatus 102 as a task accompanied by restart. However, the present invention is not limited to this, and may be any task that involves an operation that resets the timer. Also, it is assumed that the task processing itself such as the setting change of the network device 102 to be executed does not reset the timer even if the processing is performed.

  When the task management module 303 of the management apparatus 101 receives a notification indicating that the power-off timer has been started in the network device 102 (that is, a notification for specifying the shutdown timing of the network device 102) (S700), S701 Proceed with the process. The notification in S700 corresponds to the above-described 603 and is issued by the network device 102. The notification in S700 is once received by the network module 300, and this notification is transmitted from the network module 300 to the task management module 303.

  In step S <b> 701, the task management module 303 acquires, from the database 304, the power-off timer setting information set in the network device 102 that has received the power-off timer start notification received in step S <b> 701. The power-off timer setting information indicates the time from the start of the timer until the power is turned off. This power-off timer setting information may be obtained directly from the network device 102 using the device management module 302 instead of using the setting information registered in the database 304.

  In S702, the task management module 303 calculates the scheduled power-off time of the network device 102 that has received the power-off timer start notification received in S701. The scheduled power-off time is calculated using the system time when the power-off timer in S700 is received and the power-off timer setting time of the network device 102 acquired in S701.

In step S <b> 703, the task management module 303 stores, from the database 304, a list of tasks that are registered in advance in the management apparatus 101 and are generated for the network device that has received the power-off timer start notification received in step S <b> 701. get.
In step S <b> 704, the task management module 303 checks the setting information of each task in the task list acquired in step S <b> 703 in order from the top.
In step S <b> 705, the task management module 303 determines whether processing has been completed for all tasks.
If the next task can be acquired in S704, the task management module 303 determines that all tasks have not been checked yet (No in S705), and advances the process to S706.

  In step S706, the task management module 303 determines whether the currently referenced task is a task that is executed before the scheduled power-off time calculated in step S702. Note that S706 may be a determination based on the premise that the task to be executed is completed before the power is turned off, or a determination based on the premise that the task is started before the power is turned off. In step S706, it may be determined whether the task to be executed is a task that is executed in a period from a predetermined time before the power-off time to the power-off time. That is, in S706, the execution time specified by the task generated for the network device that has received the power-off timer start notification received in S701 is a predetermined time before the scheduled power-off time calculated in S702. It may be determined whether the task is included in the period.

  If it is determined that the currently referenced task is not a task that is executed before the scheduled power-off time calculated in S702 (No in S706), the task management module 303 checks the next task. , The process proceeds to S704.

  On the other hand, if it is determined that the currently referenced task is a task executed before the scheduled power-off time calculated in S702 (Yes in S706), the task management module 303 shifts the process to S707.

  In step S <b> 707, the task management module 303 determines whether the currently processed task is a task that involves restarting the network device 102. An example of a task involving restart is the firmware update task described above. The firmware update task needs to be restarted in order to reflect the firmware set in the network device 102. Whether or not to restart the network device 102 at the time of task execution may be designated by the user at the time of task creation / registration, or may be automatically determined by the task execution module.

If it is determined that the task does not involve restart (No in S707), the task management module 303 shifts the processing to S704 in order to check the next task.
On the other hand, when it is determined that the task is associated with a restart (Yes in S707), the task management module 303 shifts the process to S708.
In step S <b> 708, the task management module 303 resets (changes) the task so that the restart is not executed when the currently processed task is executed. By performing the processing of S708, it is possible to avoid resetting the power-off timer with the execution of the task. In the task resetting, the old task may be deleted once from the database 304 and registered again in the database 304 as a task that will not be restarted. When one task is set for a plurality of network devices 102, only the network device 102 affected by the power-off timer is deleted from the database 304, and only the newly affected network device 102 is deleted. A task may be created in the database 304.

When the process of S708 is completed, the task management module 303 shifts the process to S704 in order to check the next task.
If the next task cannot be acquired in S704, the task management module 303 regards that all tasks have been checked (Yes in S705), and shifts the processing to S709.

  In S709, the task management module 303 makes a request to the Web service 301, and when the task is reset in S708, the task is not executed due to the notification that the reset has been performed or the influence of the power-off timer. If there is a possibility, a change notification including a notification to that effect is made, and the processing shown in FIG.

FIG. 8 is a diagram illustrating an example of the change notification in S709 of FIG.
In FIG. 8, 800 is a screen provided by the Web service 301 of the management apparatus 101 and displayed on the Web browser of the client apparatus 103, which is a general-purpose computer. 800 is displayed as a part of the management screen of the management apparatus 101, and is displayed when a change is made to the task settings.

Reference numeral 801 denotes device information. The device information 801 indicates setting information (device name and the like) of the network device 102, the state of the network device 102, and the like.
Reference numeral 802 denotes a screen that displays the list of tasks acquired in S703 of FIG. 7 and presents to the user what has been changed in the task settings or has been affected by the power-off timer. For example, “Task01” in FIG. 8 is a firmware update task that accompanies restarting, and the task execution time is specified as 1 o'clock. Since “Task01” has been changed to a task that does not involve restart by the processing of FIG. 7, information is added to the icon and the comment. In addition, since there is a possibility that the task is not executed also in “Task03”, this is added to the icon and the comment. Note that the screen example of FIG. 8 is a display format using a window, but is not limited to this display format.
The change notification may be sent by e-mail to an administrator's e-mail address registered in advance.

As described above, in this embodiment, the task for resetting the power-off timer registered in the management apparatus 101 (for example, a task accompanied by restart) is not reset, and the wasted time until the power is turned off. Can be reduced. In addition, it is possible to appropriately notify the manager of the management apparatus 101 and the network device 102.
Therefore, even if a task such as firmware upgrade is executed from the management apparatus 101 that distributes a program such as a firmware to the network device 102, the network device 102 can be shut down efficiently, and wasteful power consumption can be reduced. .

  In the first embodiment, the method for setting the task before the scheduled power-off time by the power-off timer so as not to restart is described. By performing the setting in the first embodiment so as not to restart, it was possible to reduce the wasted time until the power was turned off by the next power-off timer, but if the power-off by the timer was not performed, the task The setting of is not reflected. Therefore, in this embodiment, a method for appropriately processing tasks after performing the processing in the first embodiment will be described.

  The overall system configuration and the hardware configuration and software configuration of the management apparatus 101, the network device 102, and the client apparatus 103 are the same as those in the first embodiment, and a description thereof is omitted here. Further, the task resetting process (FIG. 7) and the change notification (FIG. 8) in the first embodiment are the same as those in the first embodiment, and thus the description thereof is omitted.

  FIG. 9 is a sequence diagram illustrating a main processing flow in the second embodiment. The processing of the management apparatus 101 in FIG. 9 is realized by the CPU 201 of the management apparatus 101 executing a program recorded in the HD 205 so as to be readable by a computer. Further, the processing of the network device 102 in FIG. 9 is realized by the CPU 410 of the network device 102 executing a program recorded in the HD 416 so that it can be read by a computer. Reference numerals 601 to 615 denote steps. The description of 600 to 607 is the same as FIG.

  Reference numeral 608 denotes a branching process for determining whether or not the power-off timer set (timer start) in the network device 102 is reset (released) due to the user operating the network device 102 or the like. Details will be described below.

When the power-off timer is not released, the processes of 609 to 610 are executed, and when the power-off timer is released, the processes of 611 to 615 are executed.
Reference numerals 609 to 610 denote processing when the power-off timer is not canceled in 608.
When the power-off timer is not canceled, the device status monitoring module of the network device 102 requests the task execution module 502 to turn off the power of the network device 102 when the power-off timer has passed the timer time.

  When the scheduled power-off time calculated in 604 (S702 in FIG. 7) has passed, the task management module 303 of the management apparatus 101 performs alive confirmation to confirm whether the network device 102 has been powered off (610). If there is no response from the network device 102 in the alive confirmation in 610, the task management module 303 of the management apparatus 101 determines that the network device 102 has been powered off by the power-off timer, and the processing shown in FIG. Exit.

Reference numerals 611 to 615 denote processing when the power-off timer is canceled in 608.
If a job for releasing the power-off timer occurs before the power-off timer elapses, the device status monitoring module of the network device 102 releases the power-off timer (611), and the task execution module 502 and the like The job is executed and the job result is output (612). For example, as a process for canceling the power-off timer, execution of printing by the user can be mentioned. Note that the power-off timer cancellation of 611 and 612 is not limited to the operation by the user, and execution of a task whose timer is canceled from the management apparatus 101 may be performed.

  When the scheduled power-off time calculated in 604 (S702 in FIG. 7) has passed, the task management module 303 of the management apparatus 101 performs alive confirmation to confirm whether the network device 102 has been powered off (610). When a response from the network device 102 is received in this alive confirmation of 610 (613), the task management module 303 of the management apparatus 101 determines that the power-off timer of the network device 102 has been released. If it is determined that the power-off timer has been released, the task management module 303 of the management apparatus 101 requests the device management module 302 to reflect the information set by the task execution of 605 above, and re-sends to the network device 102. An activation request is made (614).

  When the network device 102 is requested to restart, the task execution module 502 of the network device 102 restarts, and notifies the management device 101 that the restart has been executed after the restart is completed (615). The response 615 may be notified to the management apparatus 101 immediately before restarting.

  FIG. 10 is a flowchart showing the detailed operation of the task management module 303 of the management apparatus 101 in 608 of FIG. That is, the processing in FIG. 7 is realized by the CPU 201 of the management apparatus 101 executing a program recorded in the HD 205 so as to be readable by a computer.

  When the set task execution time is reached, the task management module 303 requests the device management module 302 to execute the task (S900). S900 corresponds to 605 in FIG. 6, and here, it is assumed that the task changed to the setting that does not request a restart in 604 in FIG. 6 is executed.

  In step S <b> 901, the task management module 303 determines whether a power-off notification has been received from the network device 102. The power-off notification refers to a notification issued from the state monitoring module 504 using multicast or the like immediately before the network device 102 is turned off. Note that the means for notification is not limited to multicast, and the management apparatus 101 only needs to be able to determine when and in which network device 102 the power is turned off.

If it is determined that the power-off notification has been received (S901: Yes), the task management module 303 ends the process shown in FIG.
On the other hand, if it is determined that the reception of the power-off notification has not been confirmed (No in S901), the task management module 303 advances the process to S902.

In S902, the task management module 303 determines whether the scheduled power-off time + α calculated in S702 of FIG. 7 has been reached. In FIG. 10, the scheduled power-off time is widened in consideration of the deviation (α) between the scheduled power-off time and the actual power-off time. α may be set to an arbitrary time by the user.
If it is determined that the scheduled power-off time + α is not yet reached (No in S902), the task management module 303 returns the process to S901.

On the other hand, if it is determined that the scheduled power-off time + α is reached (Yes in S902), the task management module 303 shifts the process to S903.
In step S <b> 903, the task management module 303 performs alive confirmation to confirm whether the network device 102 has been powered off. Note that step S903 corresponds to step 610 in FIG. 6 and is a process for confirming whether the network device 102 has been powered off. An example of alive confirmation is a method of sending a packet such as ping to the network device 102 and confirming whether there is a response.

In step S <b> 904, the task management module 303 receives the result of the alive check in step S <b> 903 and determines whether the network device 102 is powered off.
If there is no response to the confirmation of life and death in S903, the task management module 303 determines that the power of the network device 102 is in a power-off state (device power is cut off) (Yes in S904), and the process illustrated in FIG. Exit.

  On the other hand, if there is a response (613 in FIG. 6) to the confirmation of life and death in S903, the task management module 303 determines that the network device 102 is turned on (No in S904), and proceeds to S905. Shift processing.

  In step S <b> 905, the task management module 303 issues a restart request to the network device 102. Note that the process shown in FIG. 10 is a process of waiting for a power-off notification from the network device 102, but the alive monitoring of the network device 102 may be started immediately after the task is executed.

  As described above, in this embodiment, after the scheduled power-off time elapses, if the network device 102 is not powered off, the restart can be requested so that the task can be appropriately processed, and the waste until the power-off occurs. Time can be reduced.

  In the first and second embodiments, the task re-setting in the time zone before the scheduled power-off scheduled time for the task registered in the management apparatus 101 has been described. In this embodiment, a method for appropriately processing tasks registered in a time zone after the scheduled power-off time will be described.

  The overall system configuration and the hardware configuration and software configuration of the management apparatus 101, the network device 102, and the client apparatus 103 are the same as those in the first embodiment, and a description thereof is omitted here.

  FIG. 11 is a flowchart illustrating details of the task resetting process (604) in FIG. 6 according to the third embodiment. This process is mainly performed by the task management module 303 of the management apparatus 101. That is, the processing in FIG. 11 is realized by the CPU 201 of the management apparatus 101 executing a program recorded in the HD 205 so as to be readable by a computer. In addition, since description of S700-S709 is the same as that of FIG. 7, description is abbreviate | omitted.

  In step S <b> 710, the task management module 303 determines whether the task scheduled after the scheduled power-off time is a task scheduled within the reschedulable range set in the management apparatus 101 and stored in the database 304. The reschedulable range refers to a time range from a scheduled power-off time until a predetermined time (for example, after 2 hours). That is, in S710, it is determined that the task started during the time obtained by adding the time range from the scheduled power supply time can be rescheduled. That is, in S710, the execution time specified by the task generated for the network device that has received the power-off timer start notification received in S701 is a predetermined time after the scheduled power-off time calculated in S702. A task included in the period is determined as a task within a reschedulable range.

  If it is determined that it is not within the reschedulable range (No in S710), the task management module 303 shifts the process to S704 in order to check the next task.

On the other hand, if it is determined that it is within the reschedulable range (Yes in S710), the task management module 303 shifts the process to S711.
In step S <b> 711, the task management module 303 determines whether the currently referenced task is a task that requires a restart (a task that needs to be restarted).
If it is determined that the currently referenced task is not a task that needs to be restarted (No in S711), the task management module 303 shifts the process to S704 in order to check the next task.

On the other hand, when it is determined that the currently referenced task is a task that needs to be restarted (Yes in S711), the task management module 303 shifts the process to S712.
In step S712, the task management module 303 reschedules the currently referenced task. Detailed processing in S712 is shown in FIG.

  Next, in S713, the task management module 303 resets the task so that the restart is not executed when the task rescheduled in S712 is executed. Note that the process of S713 is the same as the process of S708.

  In FIG. 11, if the task is a task that does not need to be restarted in the determination of S711, no processing is performed, but the task may be rescheduled.

FIG. 12 is a diagram illustrating an example of the change notification in S709 of FIG. In addition, since description of 800 and 801 is the same as that of FIG. 8, description is abbreviate | omitted.
In FIG. 12, reference numeral 802 denotes a screen that displays the task list acquired in step S703 of FIG. 11 and presents to the user targets for which tasks have been reset or rescheduled. For example, “Task03” in FIG. 12 is a task that has been reset in FIG. 11 or re-scheduled in FIG. These can be determined from the fact that the change information is added to the icons and comments, and the letters “00:30” indicating Start Time (task start time) are highlighted in bold (bold). ing.

  FIG. 13 is a flowchart showing details of the task rescheduling process (S712) of FIG. This process is mainly performed by the task management module 303 of the management apparatus 101. That is, the processing in FIG. 13 is realized by the CPU 201 of the management apparatus 101 executing a program recorded in the HD 205 so as to be readable by a computer.

  First, in S1000, the task management module 303 obtains a rescheduled advance allowance time (hereinafter referred to as an advance allowance time) from the database 304. The advance allowance time is a time that limits the start time of a task, for example, a time when a process is restricted such that a certain task can only be executed after 22:00. It is assumed that the allowable advance time is registered in the database 304 of the management apparatus 101 in advance.

  In step S <b> 1001, the task management module 303 acquires task processing time from the database 304. The processing time of this task refers to the time from the start to the completion of the task, and the processing time varies depending on the task type. It is assumed that the task processing time is registered in the database 304 of the management apparatus 101 in advance.

  In step S <b> 1002, the task management module 303 temporarily sets the time at which the currently referenced task is to be executed immediately before the scheduled power-off time. The temporarily set time may be set to a time before the time acquired in S1001 from the scheduled power-off time.

  Next, in S1003, the task management module 303 determines whether the task temporarily set in S1002, S1008, and S1010, which will be described later, falls within the allowable time before the scheduled power-off time.

  If it is determined that the temporarily set time is not advanced from the allowable time to the scheduled power-off time (No in S1003), the task management module 303 shifts the process to S1004.

  In step S1004, the task management module 303 notifies the user that the temporarily set task has not been received from the allowable allowable time to the scheduled power-off time and the task cannot be rescheduled. Terminate the process. Note that the notification in S1004 may be a process of notifying the administrator of an email, or may be shown on a screen as shown in FIG.

  On the other hand, when it is determined that the temporarily set time is advanced and within the allowable power-off time and the scheduled power-off time (Yes in S1003), the task management module 303 shifts the process to S1005.

In step S1005, the task management module 303 determines whether another task is already registered at the temporarily set time (that is, the time after the change).
If it is determined that there is no other task registered at the temporarily set time (No in S1005), the task management module 303 determines that there is no duplication of task execution time, and terminates the processing illustrated in FIG. To do.

  On the other hand, if it is determined that there is another task registered at the temporarily set time (Yes in S1005), the task management module 303 considers that the task execution times are duplicated, and shifts the processing to S1006. . Even if it is determined in S1005 that the task is duplicated, if the task can be duplicated, it is determined that rescheduling is possible, and the process illustrated in FIG. 13 may be terminated. .

  In step S <b> 1006, the task management module 303 acquires the priority of each overlapping task (execution task and temporary setting task) from the database 304. It is assumed that task priorities are registered in the database 304 of the management apparatus 101 in advance.

  The temporary setting task shown in S1006 refers to the task whose time is temporarily set in S1002 or S1009 described later (referred to as A), and the execution task overlaps the task whose time is temporarily set. Refers to task (B).

  In step S1007, the task management module 303 compares the priorities of the provisional setting task (A) and the execution task (B). If it is determined that the temporary setting task (A) has a higher priority (A> B) than the execution task (B) (Yes in S1007), the task management module 303 shifts the process to S1008.

  In step S1008, the task management module 303 reschedules the execution task (B) with a low priority because the temporary setting task (A) is a process with a high priority (A> B). In S1008, the execution task is provisionally set before the original time.

  In step S1009, the task management module 303 removes the temporarily set task from the rescheduling target as an execution task, and sets the originally set execution task as a rescheduling target task (temporary setting task). That is, B is replaced with A. As a result, the low priority task can shift the scheduled time forward.

  On the other hand, when it is determined that the priority of the temporary setting task (A) is equal to or lower than the priority of the execution task (B) (A ≦ B) (No in S1007), the task management module 303 shifts the process to S1010. .

In S1010, the task management module 303 is processing when the execution task (B) has a higher priority than the provisional setting task (A) or has the same priority (A ≦ B) in the determination in S1007. The temporary setting task (A) having a low priority is scheduled again.
Then, the task management module 303 performs task rescheduling by repeating the processes of S1003 to S1010. In other words, the task management module 303 reschedules the task so as to specify the time when the task should be executed according to the relative priority with other tasks in S1002 to S1010.

  As described above, in this embodiment, tasks registered in a time zone after the scheduled power-off time can be appropriately processed, and a useless time until power-off can be reduced.

It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.
Although one embodiment has been described above, the present invention can take an embodiment as a system, apparatus, method, program, storage medium, or the like. Specifically, the present invention may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.
Moreover, all the structures which combined said each Example are also contained in this invention.

(Other examples)
The present invention can also be realized by executing the following processing. That is, software (program) for realizing the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, etc.) of the system or apparatus reads the program. It is a process to be executed.

Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device.
The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and these are excluded from the scope of the present invention. is not. That is, the present invention includes all the combinations of the above-described embodiments and modifications thereof.

DESCRIPTION OF SYMBOLS 101 Management apparatus 102 Network equipment 302 Equipment management module 303 Task management module 502 Task execution module 503 Information management module 504 Status monitoring module

Claims (22)

A management system including a network device and a management device that manages the network device,
The management device
Generating means for generating a task with restart of the network device;
Execution means for executing the task generated by the generation means;
Receiving means for specifying a timing for shutting down the network device,
The network device is:
A notification means for performing notification to the management device to specify the shutdown time of the network device;
Processing means for performing processing required by the task executed in the management device,
The generation means, according to the notification, a task generated for the network device that made the notification, a setting that does not restart the network device with execution,
The processing means performs the processing requested by the task without restarting in response to the task generated by the generating means being executed by the management device in accordance with the notification. system. The task involving restart of the network device is a task for applying a program to the network device,
The processing means applies a program required by the task without restarting in response to the task changed by the generation means being executed by the management device in accordance with the notification. The management system according to claim 1. The notification is a notification that the network device shifts to a sleep state,
3. The management system according to claim 1, wherein the network device shutdown time is specified by the notification based on a time from the transition to the sleep state set in the network device to the shutdown. . The generation means generates the task by specifying a time to be executed,
Further, when the time to be executed specified by the task generated for the network device that has performed the notification is earlier than the time of the shutdown, the generation unit is configured so that the network device The management system according to any one of claims 1 to 3, wherein a task set to not restart is generated.   When the generation time specified by the task generated for the network device that has performed the notification is included in a predetermined period before the shutdown time, the generation unit generates a network along with the execution. The management system according to claim 4, wherein the task is set so that the device is not restarted.   The generation means determines the time to be executed when the time to be executed specified by the task generated for the network device that has performed the notification is included in a predetermined period after the time of the shutdown. The management system according to claim 4 or 5, wherein the management system generates a task that is specified before the shutdown time and is set so that the network device is not restarted with execution. The task has a priority;
The management system according to claim 6, wherein the generation unit specifies a time to execute a generated task according to a relative priority with respect to another task. The management device
Confirmation means for confirming whether or not the network device has been shut down after the time of the shutdown;
If it is confirmed by the confirmation means that the network device is not shut down, request means for requesting the network device to restart,
8. The management system according to claim 1, wherein the management system includes: A management device for managing network equipment,
Generating means for generating a task involving restart of the network device by designating a time to be executed;
Execution means for executing the task generated by the generation means;
Receiving means for specifying a timing for shutting down the network device,
When the generation time is before the shutdown time, the generation unit is configured so that the network device does not restart with execution of a task generated for the network device that performed the notification. A management device characterized by:   The management apparatus according to claim 9, wherein the task involving restart of the network device is a task for applying a program to the network device. The notification is a notification that the network device shifts to a sleep state,
The management device according to claim 9 or 10, wherein the notification specifies the time of shutdown of the network device based on the time from the transition to the sleep state set for the network device to the shutdown. .   The generation means, when the time to be executed specified by the task generated for the network device that has made the notification is included in a predetermined time before the shutdown time, The management apparatus according to claim 9, wherein the task is set so as not to restart the device.   The generation means determines a time to be executed when a time to be executed specified by a task generated for the network device that has made the notification is included in a predetermined time after the time of the shutdown. The management apparatus according to any one of claims 9 to 12, wherein the management apparatus generates a task that is specified before the time of the shutdown and is set not to restart the network device with execution. The task has a priority;
14. The management apparatus according to claim 13, wherein the generation unit specifies a time to execute a generated task according to a relative priority with respect to another task. The management device
Confirmation means for confirming whether or not the network device has been shut down after the time of the shutdown;
If it is confirmed by the confirmation means that the network device is not shut down, request means for requesting the network device to restart,
The management apparatus according to claim 9, further comprising: A management device for managing network equipment,
Generation means for generating a task with an operation of resetting a timer for shutting down the network device included in the network device by designating a time to be executed;
Execution means for executing the task generated by the generation means;
Receiving means for receiving a notification indicating that the timer of the network device has been started, for specifying a time when a predetermined time has elapsed since the start of the timer set in the network device as a shutdown time; Have
The generation unit is configured not to reset the timer of the network device when executing the task generated for the network device that has performed the notification when the time to be executed is before the shutdown time. A management device characterized by that.   The management apparatus according to claim 16, wherein the task involving the operation of resetting the timer of the network device is a task involving restart of the network device. A control method in a management system including a network device and a management device that manages the network device,
In the management device,
A generation step for generating a task accompanied by restart of the network device;
An execution step of executing the generated task;
A receiving step of receiving a notification for specifying a timing of shutdown of the network device;
In the network device,
A notification step for notifying the management device for specifying a shutdown timing of the network device;
A processing step for performing processing required by the task executed in the management device,
In the generation step, according to the notification, a task generated for the network device that performed the notification is set so that the network device does not restart with execution,
In the processing step, in response to the task generated in the generation step being executed in the management device according to the notification, the processing requested by the task is performed without restarting. Method. A control method in a management device that manages network devices,
A generation step for generating a task involving restart of the network device by designating a time to be executed;
An execution step of executing the generated task;
Receiving a notification for specifying the time of shutdown of the network device,
In the generation step, when the time to be executed is before the time of the shutdown, the task generated for the network device that has performed the notification is set so that the network device does not restart with execution. A control method characterized by: A control method in a management device that manages network devices,
A generation step of generating a task with an operation of resetting a timer for shutting down the network device included in the network device by designating a time to be executed;
An execution step of executing the generated task;
A reception step of receiving a notification indicating that the timer of the network device has been started, for specifying a time when a predetermined time has elapsed since the start of the timer set in the network device as a time of shutdown; and Have
In the generation step, if the time to be executed is earlier than the time of the shutdown, a task generated for the network device that has performed the notification is set not to reset the timer of the network device upon execution. The control method characterized by these.   The program for functioning a computer as a means of any one of Claim 9 thru | or 15.   The program for functioning a computer as a means of Claim 16 or 17.

Images