Information processing device, method, and program

Abstract

To provide functionality enabling appropriate operation of schedule management for executing various tasks for device management, in a device management application.SOLUTION: An information processing apparatus sets a first schedule determining a timing of transmitting, to a management target device, an instruction to cause the management target device to enter a predetermined power supply state in which a request via a network fails and sets a second schedule determining a timing of transmitting, to the management target device, a request to acquire operation information via the network, and provides, when the second schedule is set, a function of automatically adjusting the second schedule so that a period during which the request via the network fails based on the first schedule does not overlap the timing of transmitting the request based on the second schedule and that the operation information is acquired.SELECTED DRAWING: Figure 10

Description

Technical Field

[0001] The present invention relates to a technology for realizing appropriate device management when there are devices not subject to management in a device management system including one or more network-connected devices.

Background Art

[0002] In recent years, there is a management application (program) that provides a management function for a plurality of network-connected devices in an office. Specifically, there is a device management system that selects from a list of devices discovered from a network and executes tasks such as device security monitoring and device power management (for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As part of device security monitoring, a request for setting a set value according to an appropriate security policy in the device installation environment to a device to be managed may be transmitted via a network using a management application. Also, the management application has a function of automatically transmitting an acquisition request via a network according to a schedule for periodically acquiring operation information of the device to be managed.

[0005] Furthermore, in the operation of offices and other locations where devices are installed, there may be periods when it is required to turn off the power to the devices or to put them in power-saving mode. Management applications need to have the functionality to schedule these periods via commands transmitted over the network.

[0006] Since the schedule for sending these requests will be set individually via separate configuration screens, it will be difficult for administrators and other users to notice if these schedules overlap.

[0007] The present invention aims to provide functionality that ensures proper operation of scheduling for device management. [Means for solving the problem]

[0008] The present invention relates to an information processing device that manages device information of a device to be managed using storage means and executes a management application for managing the managed device via a network, comprising: a first setting means for setting a first schedule that determines the timing for sending an instruction to the managed device to transition to a predetermined power state in which a request via the network fails; a second setting means for setting a second schedule that determines the timing for sending a request to the managed device to acquire operational information via the network; a third setting means for setting a third schedule that determines the timing for sending a request to the managed device to set a security policy via the network; and, with respect to the setting of the third schedule by the third setting means, an execution means that performs processing to ensure that the timing for sending a request based on the third schedule does not overlap with the period in which the request fails due to an instruction sent based on the first schedule. Then, as the processing by the execution means, the period during which the request will fail based on the instructions transmitted according to the first schedule is presented, and display control is performed to allow the user to set the third schedule. It is characterized by the following. [Effects of the Invention]

[0009] According to the present invention, it is possible to provide functionality that ensures proper operation of the schedule management for device management. [Brief explanation of the drawing]

[0010] [Figure 1] A diagram showing an example configuration of the device management system of the present invention. [Figure 2] A block diagram showing an example of the hardware configuration of an information processing device. [Figure 3] A block diagram showing an example of the module configuration of the device management server software. [Figure 4] A block diagram showing an example of the internal configuration of device 2000. [Figure 5] This diagram illustrates a screen related to the device list provided by the device management server. [Figure 6] This diagram illustrates a screen related to the settings menu provided by the device management server. [Figure 7] This diagram illustrates the settings screen for retrieving status information provided by the device management server. [Figure 8] This diagram illustrates the power management settings screen provided by the device management server. [Figure 9] This diagram illustrates the security policy settings screen provided by the device management server. [Figure 10] This is a flowchart illustrating the processing of the device management server according to Embodiment 1. [Figure 11] This figure illustrates a confirmation screen for the security policy according to Embodiment 1. [Figure 12] This figure illustrates a screen for detailed settings related to acquiring operational information according to Embodiment 1. [Figure 13] This is a flowchart illustrating the processing of the device management server according to Embodiment 2. [Figure 14] This figure illustrates a configuration screen for security policies according to Embodiment 2. [Figure 15]It is a diagram exemplifying a screen related to a power management schedule according to Embodiment 2.

Mode for Carrying Out the Invention

[0011] (Example 1) <Explanation of System Configuration> FIG. 1 is a schematic diagram showing the configuration of a device management system showing an embodiment of the present invention.

[0012] FIG. 1 shows that a device management server 1000 and a plurality of devices 2000 are connected. The device 2000 receives print data received via a network and performs printing on actual paper using known printing technologies such as electrophotographic technology and inkjet technology. It also has a function of reading a paper original via a scanner, making copies, or converting it into image data and transmitting it via Email or the like. Of course, a printer without a copy function is also applicable. The device management server 1000 and the device 2000 are connected by a communication line 3000 that constructs a network such as a LAN.

[0013] Here, the device management server 1000 is an information processing device in which a management application (program) that provides functions such as a UI control unit 30, a device control unit 31, a schedule control unit 32, and a function control unit 33 shown in FIG. 3 is executed in order to manage the device 2000.

[0014] <Hardware Configuration of Information Processing Device> FIG. 2 shows an example of the hardware configuration of the information processing device as the device management server 1000.

[0015] The CPU 10 uses the RAM 12 as a work area and executes various programs such as the OS and software (management applications) stored in the ROM 11 and HDD 19. The various components of the device are connected via the system bus 13. The device also includes a disk controller (DKC) 18, a DiskDrive 20 capable of mounting storage media such as CD-ROMs, DVDs, magnetic tapes, and IC memory cards, a video card (VC) 14, and a display device (CRT) 15. Furthermore, the device includes a keyboard controller (KBC) 16, a keyboard (KB) 17, and pointing devices such as a mouse (not shown). The device also communicates data with devices on the communication line 3000 via a network interface board (NIC) 21.

[0016] <Software configuration of the device management server> Figure 3 shows an example of the module configuration of the UI control unit 30, device control unit 31, schedule control unit 32, and function control unit 33 software that operate on the device management server 1000. This example of module configuration is the main component of the processing described later, which is realized by executing the device management software (management application), and is executed by the CPU 10 on the RAM 12, ROM 11, and HDD 19 shown in Figure 2.

[0017] The UI control unit 30 consists of a device display unit 301, a schedule display unit 302, and a function display unit 303. The device control unit 31 consists of a device connection unit 311, a device data management unit 312, and a device data storage unit 313. The schedule control unit 32 consists of a schedule management unit 321 and a schedule storage unit 322. The function control unit 33 consists of a power setting management unit 331, a security policy setting management unit 332, a status setting management unit 333, a counter setting management unit 334, and a setting storage unit 335.

[0018] The UI control unit 30 controls the UI of the device control unit 31, schedule control unit 32, and function control unit 33, respectively, through the device display unit 301, schedule display unit 302, and function display unit 303. It can also be implemented as a web-based application, in which case it can be used via a web browser.

[0019] The device connection unit 311 has functions for device discovery, information collection from devices, and configuration execution. One example of the functions of the device connection unit 311 is the device discovery function for device 2000 using SNMP, IP Broadcast, SLP / Multicast, etc. In this case, the device connection unit 311 searches for device 2000 at any time. The device connection unit 311 also has the function of acquiring / modifying device information, such as MIB (Management Information Base) security policy information, via a communication line 3000 such as a LAN. Device information also manages information acquired from the device as operational information, such as status, counter information, and log information.

[0020] Furthermore, the device connection 311 acquires device identification information such as the device name, product name, and IP address as a result of device discovery, and stores this device information in the storage means by the device data storage unit 313. The device data management unit 312 is responsible for managing data such as device information of managed devices stored in the device data storage unit 313.

[0021] The schedule management unit 321 works in conjunction with the functions of the function control unit 33 to generate and manage schedules entered from the schedule display unit 302 and save them to the schedule storage unit 322.

[0022] The power setting management unit 331, security policy setting management unit 332, status setting management unit 333, and counter setting management unit 334 of the function control unit 33 each generate and manage function information based on input from the function display unit 303 and store it in the setting storage unit 335.

[0023] Here, the device data storage unit 313, the schedule storage unit 322, and the setting storage unit 335 can store data in a database running on the HDD 19 or store data in an external storage service. In addition, table data such as schedule lists, device lists, and function lists are stored in the storage means.

[0024] <Device Software Configuration> Figure 4 shows an example of the software configuration of the information control unit 40 operating on device 2000.

[0025] Device 2000, as a software module, has an information control unit 40 for managing multiple dynamically changing sets of information. The counter information management unit 401 manages the number of printed pages, etc., and stores it in the counter storage unit 402. The MIB information management unit 403 manages MIB information, which is the aforementioned device information, and stores it in the MIB information storage unit 404. The power information management unit 405 manages power-off information and reboot information and stores it in the power information storage unit 406. The status information management unit 407 manages status information such as online, offline, and error, and stores it in the status information storage unit 408. The security policy information management unit 409 manages security policy information such as password setting policies and port restrictions, and stores it in the security policy information storage unit 406. Each piece of data is sent to the device management server 1000 via SNMP or other protocols in accordance with the request of the device management server 1000.

[0026] The device transitions through power states such as power off, power saving, and recovery from power saving in response to input to the main unit or requests via the network. If a device is powered off or in a predetermined power saving state, even if the management server 1000 sends requests via the network to obtain operational information or perform various settings, the corresponding processing will not be executed on the target device, and these requests will fail. In a power saving state other than the predetermined power saving state, the device may be able to automatically recover from the power saving state in response to a request via the network and execute the processing related to that request.

[0027] <Schedule Creation Process> Figures 5 to 8 show example screens of the device management server 1000. Using these, we will explain the process of creating schedules for status, counters, security policies, and power management.

[0028] The device management server 1000 performs a network discovery to identify devices for management. While SNMP and other algorithms can be used for this discovery, the specific method is not restricted. Figure 5 shows an example of the screen after discovery. The discovered device names are displayed along with information about those devices (hostname, IP address, serial number, etc.).

[0029] To create a schedule, first select the target device. You can select a device by checking the checkbox shown in Figure 5. Once a device is selected and you click "Settings," a list of configurable items for that device will appear, as shown in Figure 6. Here, the selectable tasks include Status, Counters, and Security Policy. These configurable tasks are determined by the device type, its capabilities, etc.

[0030] Figure 7 shows an example of the screen for setting the status acquisition schedule, which appears when "Status" is selected in the settings menu shown in Figure 6. You set the "Execution Date and Time" and "Repeat Interval". Multiple schedules can be set, and the currently set schedules are displayed at the bottom. These schedules can be deleted or added as needed. The setting here is to acquire the status every 30 minutes starting from 13:00 on 2021 / 07 / 01, and this setting is saved by pressing "Save". Checking "Execute when server starts" allows you to choose whether to acquire the status when the device management server 1000 is started. Furthermore, if there are detailed settings specific to this item, they can be configured from "Advanced Settings".

[0031] The management application can also provide a "Power Management" settings screen when a device is selected in Figure 5. Figure 8 shows an example of a settings screen where a power management schedule can be set.

[0032] Here, you first set the "Operation Type." You can choose from Sleep, Sweep Wake, Restart, or Power Off. Next, set the "Start Date and Time" and "Repeat." Multiple schedules can be set, and the currently set schedules are displayed at the bottom. These schedules can be deleted or added as needed. The setting here is to power off the device every day starting from 22:00 on 2021 / 07 / 01, and this setting is saved when you press "Save." This series of settings creates schedules for various acquisitions and power management for the selected device, and subsequent actions are performed.

[0033] Figures 10 and 13 are flowcharts illustrating the processes performed by the device management server 1000. S1001 to S1011 and S1301 to S1306 represent the respective steps, each of which is achieved by the CPU 10 loading a management application (program) from the HDD 19, ROM 11, etc., into RAM 12 and executing it.

[0034] <Embodiment 1> The flowchart in Figure 10 will be used to explain the scheduling function processing on the device management server 1000. The explanation of this process will be supplemented using the operational cases shown in Figures 11 and 12. Note that the processing shown in Figure 10 is achieved by the CPU 10 executing the device management software.

[0035] When creating a schedule on the device management server 1000, as explained earlier, the user selects a device from the UI shown in Figure 5, then selects the items to configure from the UI shown in Figure 6, and the schedule configuration begins.

[0036] In S1001, the schedule management unit 321 obtains the execution date and time and repetition interval entered from the schedule display unit 302. In S1002, the schedule display unit 302 determines whether a save instruction has been given. If a save instruction has been given, the process proceeds to S1003. Otherwise, the process returns to the schedule setting operation. In S1003, the schedule management unit 321 determines whether a power management schedule is set from each schedule stored in the schedule storage unit 322. If a power management schedule is set, the process proceeds to S1004. If it is not set, the process proceeds to S1009. In S1004, the schedule management unit 321 determines whether the schedule obtained in S1001 overlaps with the power management schedule confirmed in S1003. If there is an overlap, the process proceeds to S1005. If there is no overlap, the process proceeds to S1009.

[0037] In S1005, the schedule management unit 321 determines whether the schedule obtained in S1001 is a security policy monitoring schedule. If so, proceed to S1010. If a different schedule is set, proceed to S1006.

[0038] In S1006, the schedule management unit 321 determines whether the schedule obtained in S1001 is a status acquisition schedule or a counter acquisition schedule. If it is one of those schedules, the process proceeds to S1007. If it is not one of those schedules, the process proceeds to S1009.

[0039] In S1007, the status setting management unit 333 or the counter setting management unit 333 determines whether automatic adjustment is set for the information set in the setting storage unit 335. If it is set, proceed to S1008. If it is not set, proceed to S1009. In S1008, the schedule management unit 321 adjusts the schedule based on the automatic adjustment period setting set in the setting storage unit 335. Then, determine the schedule and proceed to S1009.

[0040] In S1009, the schedule management unit 321 saves the schedule determined in S1008 to the storage device in the schedule storage unit 322, then returns to the schedule display unit 302 and terminates.

[0041] In S1010, the power setting management unit 331 displays a warning and power setting details via the UI function display unit 303, and proceeds to S1011. In S1011, the power setting management unit 331 displays whether to reset the security policy monitoring schedule via the UI function display unit 303, and determines whether the reset button has been pressed. If reset is selected, the process returns to S1001. If reset is not selected, the process proceeds to S1009.

[0042] Here, we will supplement this explanation using the screen examples shown in Figures 11 and 12.

[0043] First, let's assume that, as shown in Figure 8 of the power management schedule, the power off setting is configured with execution time: 2021 / 07 / 01 22:00 and repetition setting: daily. Then, let's assume that, as shown in the example screens in Figures 5 and 6, we select Device2 and security policy, input the settings for execution time: 2021 / 07 / 01 22:30 and repetition interval: 24 hours, and attempt to save the settings.

[0044] S1001 retrieves the above security policy settings, and S1002 determines that it is a save command. Since a power management schedule has been set in advance, S1003 determines this and proceeds to S1004. In S1004, the power off schedule is set to 22:00, and the security policy monitoring schedule setting is the power off time, so it proceeds to S1005. Since it is a security policy monitoring schedule setting, S1010 issues a warning and displays the power management schedule. An example of this screen is shown in Figure 11. S1011 indicates that if you want to reset, you press the "Cancel" button in Figure 11 to return to the schedule settings in Figure 9. If you want to save as is, you press the "Save" button and it is saved by S1009.

[0045] Furthermore, let's assume, as shown in the example screens in Figures 5 and 6, that you try to set Device2, status selected, execution time: 2021 / 07 / 01 22:30, and repetition interval: 24 hours, and then try to save the settings.

[0046] The screen shown in Figure 12 allows you to configure detailed settings for acquiring operational information (in this case, status information), specifically the setting "Automatically adjust when power management schedules overlap." Here, we assume that the maximum cycle is set to 48 hours and the maximum adjustment time to 1 hour. The maximum cycle is the maximum frequency at which information is acquired from the device. The maximum adjustment time is the maximum amount of time that can be shifted from the input time. If there is a period during which acquisition requests via the network fail due to the power state of the target device following the power management schedule, the schedule (acquisition request timing) will be automatically adjusted according to the settings in Figure 12 so that operational information is acquired outside of that period.

[0047] Steps S1001 to S1004 are the same as in the previous example, but since a status is selected, steps S1005 and S1006 determine this, and the process proceeds to S1007. In S1007, it is determined that an automatic adjustment setting exists, and the adjustment process based on the period setting in S1008 is performed. Here, the maximum period is set to 48 hours and the maximum adjustment time to 1 hour, so the status is acquired every 48 hours at 21:30, when the power is not turned off.

[0048] Furthermore, let's assume that the power-off setting is configured as follows, based on the power management schedule in Figure 8: execution time: 2021 / 07 / 01 22:00, repetition setting: every 2 days. Then, let's assume that, using the example screens shown in Figures 5 and 6, we select Device2 and Counter, input the settings as follows: execution time: 2021 / 07 / 01 22:30, repetition interval: 24 hours, and attempt to save. Let's also assume that automatic adjustment is not enabled in this case.

[0049] Steps S1001 to S1004 are the same as in the previous example, but since the counter is selected, steps S1005 and S1006 determine this, and the process proceeds to S1007. In S1007, it is determined that there is no automatic adjustment setting, and the schedule setting is saved in S1009. Here, no warning is issued and the settings are saved as is, and some of the requests that follow the acquisition schedule succeed (in this case, requests that are executed when the power is not turned off succeed), and the counter is acquired every two days.

[0050] These actions allow for warnings or prompts for reconfiguration if security policy scheduling conflicts with power management scheduling during schedule creation. Furthermore, if status or counter scheduling conflicts with power management scheduling, the settings can be left as is, and the system can save schedules adjusted by periodic settings, depending on whether automatic adjustment is enabled.

[0051] <Embodiment 2> Figure 9 shows an example of the security policy settings screen. It is the same settings screen as Figure 5 mentioned earlier. Here, we will focus on the "Execute at server startup" item. When this setting is enabled, the device management server 1000 can attempt to request information retrieval and other actions when it starts up.

[0052] If information cannot be obtained when the device management server 1000 starts up, and in the case of security policy monitoring, it may be necessary to reconfigure the settings while considering the power management schedule. This process will be explained in detail using Figure 13. Furthermore, this process will be explained in more detail using the screen examples in Figures 14 and 15.

[0053] When the device management server 1000 starts up, schedule settings are retrieved for each function.

[0054] In S1301, the schedule management unit 321 determines whether the startup execution settings previously obtained from the schedule storage unit 322 should be executed. If the settings are to be executed, the process proceeds to S1302; otherwise, the startup schedule processing is terminated. In S1302, the schedule management unit 321 attempts to execute a task by sending a request to the device to acquire information, according to the settings of each management unit of the function control unit 33, and then proceeds to S1303.

[0055] In S1303, the schedule management unit 321 determines whether the information acquisition from the device was successful. If successful, the startup schedule processing is terminated. Otherwise, the process proceeds to S1304. In S1304, the schedule management unit 321 determines whether the schedule setting is for monitoring security policies. If it is for monitoring security policies, the process proceeds to S1305; otherwise, the schedule processing is terminated.

[0056] In S1305, the schedule management unit 321 takes into account the power management schedule obtained from the setting storage unit 335 and schedules the execution process to be performed so as not to overlap with sleep, restart, or power-off times, and then proceeds to S1306.

[0057] In S1306, the schedule management unit 321 saves the schedule determined in S1305 to the schedule storage unit 322, and the schedule processing is terminated.

[0058] Here, we will supplement this explanation using the example screens shown in Figures 14 and 15. Unlike Figure 9, in the example screen shown in Figure 14, we assume that "Run when server starts" was checked when the security policy schedule was set earlier.

[0059] Furthermore, as shown in the example screen in Figure 15, assume that the power management schedule is set as follows: Power off setting: Execution time: 2021 / 07 / 01 22:00, Repeat setting: Daily; Execution time: 2021 / 07 / 03 19:00, Repeat setting: Weekly; Restart setting: Execution time: 2021 / 07 / 05 12:00, Repeat setting: Daily.

[0060] When the device management server 1000 starts up, schedule settings are retrieved for each function. This is also the case when the device management server 1000 restarts. The security policy schedule is retrieved, and S1301 determines that the startup execution settings described above are in place. S1302 checks the security policy monitoring, and here it is determined that information could not be retrieved (S1303). S1304 determines the function, and S1305 resets the execution considering the power management schedule. Here, the settings are made to avoid the times when the power is off or restarting, based on the current date and time. For example, if a restart is needed around 19:00 on 2021 / 07 / 03, the restart will not be performed after 19:00 on that day. Also, if it is around 12:00 on 2021 / 07 / 05, the restart will be performed after 12:30 on that day. The interval between restarts can be set as long as possible, but this is not a requirement here. Subsequently, the data is saved by S1305 and the operation is performed at the set time.

[0061] These actions ensure that the "Execute at server startup" option is checked when configuring the security policy monitoring schedule. If data acquisition fails during the startup of the device management server 1000, the settings can be reconfigured while taking the power management schedule into consideration.

[0062] (Other examples) The present invention also includes apparatuses, systems, and methods configured by appropriately combining the embodiments described above.

[0063] Here, the present invention is a device or system that is the main body for executing one or more software programs that realize the functions of the embodiments described above. Furthermore, a method for realizing the embodiments described above that are executed on the device or system is also part of the present invention. The program is supplied to the system or device via a network or various storage media, and the program is read into one or more memories by one or more computers (CPU, MPU, etc.) of the system or device and executed. In other words, as part of the present invention, the program itself or various storage media that can be read by the computer storing the program are also included. Furthermore, the present invention can also be realized by a circuit (e.g., ASIC) that realizes the functions of the embodiments described above. [Explanation of symbols]

[0064] 1000 Device Management Server 2000 devices

Claims

1. An information processing device that manages device information of devices to be managed using storage means, and runs a management application for managing the managed devices via a network, A first setting means sets a first schedule that determines the timing for sending an instruction to a managed device to transition to a predetermined power state in which the request via the network fails, A second setting means for setting a second schedule that determines the timing for sending a request to a managed device to acquire operational information via the aforementioned network, A third configuration means for setting a third schedule that determines the timing for sending a request to a managed device to configure security policies via the aforementioned network, The setting of the third schedule by the third setting means includes an execution means that performs processing to ensure that the timing of sending a request based on the third schedule does not overlap with the period during which the request fails due to instructions sent based on the first schedule. The information processing apparatus is characterized in that, as the processing by the execution means, it presents a period during which the request will fail based on the instruction transmitted based on the first schedule, and then performs display control to allow the user to set the third schedule.

2. The information processing apparatus according to claim 1, further comprising a means for providing a function to automatically adjust the second schedule so that when setting the second schedule, the timing of sending instructions transmitted based on the first schedule does not overlap, and operational information is acquired outside of the period in which at least some of the requests based on the second schedule fail.

3. The information processing apparatus according to claim 1, characterized in that, with respect to setting the second schedule, it is permissible for some timings of sending requests based on the second schedule to overlap with a period during which the requests fail due to instructions sent based on the first schedule.

4. The information processing apparatus according to any one of claims 1 to 3, characterized in that the device information includes identification information of the device to be managed.

5. The information processing apparatus according to any one of claims 1 to 4, characterized in that the operational information obtained in response to the request to obtain the operational information includes at least one of the status information, counter information, and log information of the managed device, and is stored in the storage means.

6. A method in an information processing device, A management process in which device information of the devices to be managed is managed using a storage means, A first setting step involves setting a first schedule that determines the timing for sending an instruction to a managed device to transition to a predetermined power state in which a request via the network fails, A second setting step involves setting a second schedule that determines the timing for sending a request to a managed device to acquire operational information via the aforementioned network, A third configuration step involves setting a third schedule that determines the timing for sending a request to configure security policies to managed devices via the aforementioned network, The setting of the third schedule includes an execution step of performing processing to ensure that the timing of sending a request based on the third schedule does not overlap with the period during which the request fails due to instructions sent based on the first schedule. The method is characterized in that, as the processing in the execution step, the period during which the request will fail based on the instruction transmitted based on the first schedule is presented, and then display control is performed to allow the user to set the third schedule.

7. On the computer, A management process in which device information of the devices to be managed is managed using a storage means, A first setting step involves setting a first schedule that determines the timing for sending an instruction to a managed device to transition to a predetermined power state in which a request via the network fails, A second setting step involves setting a second schedule that determines the timing for sending a request to a managed device to acquire operational information via the aforementioned network, A third configuration step involves setting a third schedule that determines the timing for sending a request to configure security policies to managed devices via the aforementioned network, The setting of the third schedule is a program for executing an execution step that performs processing to ensure that the timing of sending a request based on the third schedule does not overlap with the period during which the request fails due to instructions sent based on the first schedule, A program that, as the process in the execution step, presents a period during which the request will fail based on instructions sent according to the first schedule, and then performs display control to allow the user to set the third schedule.

Images