Information processing device, control method and program for information processing device

Abstract

To provide a device management function meeting the needs of a device manager even when a specific device is set to be an object not to be managed.SOLUTION: A device management server manages, with a device information storage unit 313, device information on a plurality of devices to be managed, and the device management server has: a device information management unit 312 that manages device information in the device information storage unit 313 as an object to be managed or an object not to be managed; and a device display unit 301 that, when allowing a user to select a target device with a first function, controls not to take devices corresponding to the device information managed as the object not to be managed as selection candidates and take devices corresponding to the device information managed as the object to be managed as the selection candidates, and when allowing the user to select a target device with a second function, controls to take devices corresponding to the device information managed as the object to be managed and the object not to be managed as the selection candidates.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present invention relates to an information processing apparatus for managing devices, a control method for the information processing apparatus, and a program. [Background technology]

[0002] Device management systems and management servers that collect and manage data such as operational information for devices such as printers and multifunction devices are well known. Due to the increasing number of devices to be managed and the need to reduce management server costs and maintain them, the number of devices that can be managed by a single management device is expanding. Device management systems typically periodically collect information such as power, status, and counters to continuously manage devices. Power management also includes powering down and rebooting devices.

[0003] Furthermore, device management systems add devices to be managed by searching, but can also exclude some devices from management by specifying their IP addresses. In this case, a device management system has been devised that can perform appropriate data analysis even when device information and association information no longer exists due to a device being excluded from management. Patent Document 1 discloses a device management system that records information about a device that has been excluded from management along with an expiration date indicating until when it will remain a managed device, and continues to aggregate data until the expiration date. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-190001 Summary of the Invention [Problem to be solved by the invention]

[0005] However, if a specific device is excluded from management in a device management system as in Patent Document 1, important items such as security policies and power management cannot be managed.

[0006] An object of the present invention is to provide a device management function that meets the needs of a device administrator even when a specific device is set as an unmanaged device. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, the information processing apparatus of the present invention is an information processing apparatus that manages device information of a plurality of devices to be managed by a storage means, each of the plurality of devices included in a control measure to manage the information as managed or unmanaged; a function control means for controlling the execution of a first function that can be targeted only at devices managed as managed devices, and a second function that is a specific function different from the first function and can be targeted at devices managed as managed devices and devices not managed as managed devices; When selecting the target device for the first function, it will be managed as unmanaged. It was The device is not selected as a candidate but is managed as a managed device. It was Select the device as a candidate, The aforementioned When selecting the target device for the second function, it will be managed as managed or unmanaged. It was and a control means for controlling the device to be a selection candidate. [Effects of the Invention]

[0008] According to the present invention, even when a specific device is set as an unmanaged device, it is possible to provide a device management function that meets the needs of a device administrator. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates a configuration of a device management system. [Figure 2] FIG. 2 illustrates a hardware configuration of a device management server. [Figure 3] FIG. 2 is a diagram illustrating a software configuration of a device management server. [Figure 4] FIG. 2 is a diagram illustrating a software configuration of a device. [Figure 5] FIG. 10 is a diagram illustrating an example of a device search screen. [Figure 6] FIG. 10 is a diagram illustrating an example of a device search setting screen. [Figure 7] FIG. 10 is a diagram illustrating an example of a schedule setting screen. [Figure 8] FIG. 10 is a diagram illustrating an example of a device selection screen. [Figure 9] FIG. 10 is a diagram illustrating an example of a power management schedule setting screen. [Figure 10] 10 is a flowchart showing a device search process. [Figure 11] 10 is a flowchart showing a display process for device selection candidates. [Figure 12] FIG. 10 is a diagram illustrating an example of a screen for setting a target display. [Figure 13] FIG. 10 is a diagram illustrating an example in which devices not subject to management are displayed as selection candidates. [Figure 14] 10 is a flowchart showing a process when a schedule is executed. [Figure 15] 10 is a flowchart showing a process for displaying a schedule setting screen. DETAILED DESCRIPTION OF THE INVENTION

[0010] (First embodiment) 1 is a diagram showing the configuration of a device management system. The device management system has a device management server 1000 that manages devices and a device group 2000 that is the object of management. The device group 2000 includes multiple devices 2001 to 2003. The device management server 1000 is connected to each of the devices 2001 to 2003 via a network 3000, and is capable of communicating with each other.

[0011] The devices 2001 to 2003 are information processing devices capable of communicating with the device management server 1000. In this embodiment, the devices 2001 to 2003 are described as an example of information processing devices, each of which is an MFP (Multi Function Peripheral) equipped with multiple functions such as a printing function and a scanning function. In printing, print data received from an external device is printed on actual paper using known printing technology such as electrophotography or inkjet technology. In scanning, a paper document is read via a scanner to generate image data, which is then copied or converted into image data and sent by email or the like. The devices 2001 to 2003 may be any information processing device capable of communication, such as an image forming device such as a printer, an image processing device such as a scanner, a 3D printer, a laptop computer, a smartphone, or a smart home appliance.

[0012] The device management server 1000 is an information processing device that executes device management software to provide a device management service. The device management server 1000 manages a plurality of devices in a device group 2000 via a network 3000. The device management server 1000 may be realized by one or more information processing devices, a virtual machine (cloud service) that uses resources provided by a data center that includes information processing devices, or a combination of these.

[0013] The network 3000 is a communication network such as a LAN. The network 3000 may be configured as any one of a communication network such as a LAN or a WAN, a cellular network (e.g., LTE or 5G), a wireless network, a telephone line, a dedicated digital line, etc., or a combination of these. In other words, the network 3000 may employ any communication method as long as it is configured to enable data transmission and reception.

[0014] <Device management server hardware configuration> 2 is a diagram showing the hardware configuration of the device management server 1000. The device management server 1000 includes a CPU 10, a ROM 11, a RAM 12, a display I / F 14, a display device 15, an input I / F 16, an input device 17, a storage device I / F 18, an HDD 19, a disk drive 20, and a communication I / F 21. The CPU 10, ROM 11, RAM 12, the display I / F 14, the input I / F 16, the storage device I / F 18, and the communication I / F 21 are connected via a system bus 13.

[0015] A CPU (Central Processing Unit) 10 performs overall control of the device management server 1000. The CPU 10 uses RAM 12 as a work area to execute various programs, such as device management software, stored in ROM 11 or HDD 19 or supplied by a storage medium mountable on a disk drive 20.

[0016] The ROM (Read Only Memory) 11 is a memory dedicated to reading data, and stores, for example, the basic control program of the device management server 1000. The RAM (Random Access Memory) 12 is a memory from which data can be read and written. The RAM 12 is used, for example, as a working memory for the CPU 10.

[0017] The display device 15 is, for example, a liquid crystal display, and displays various information to the user. The CPU 10 displays a user interface and various screens on the display device 15 via the display I / F 14. The input device 17 has a pointing device (for example, a mouse, touchpad, touch panel, trackball, etc.), a keyboard, etc., and accepts operations from the user. The CPU 10 accepts input instructions for the user interface from the input device 17 via the input I / F 16. The display device 15 and the touch panel of the input device 17 may be integrated into one device such as a touch panel. By associating input coordinates on the touch panel with display coordinates, it is possible to configure a GUI that makes it appear as if the user can directly operate the screen displayed on the touch panel.

[0018] The HDD (Hard Disk Drive) 19 is an example of a storage device that stores various programs, data, etc. The Disk Drive 20 is an example of a storage device that can read and write data by loading external media such as floppy disks, CD-ROMs, DVDs, and IC memory cards. The CPU 10 accesses the HDD 19 and the Disk Drive 20 via the storage device I / F 18 to read and write data. The HDD 19 may also be used in place of the RAM 13 or the ROM 12. The CPU 10 connects to a network 3000 via a communication I / F 21, enabling data communication with a device 2001 on the network 3000.

[0019] <Device management server software configuration> 3 is a diagram showing the modular configuration of software related to device management in the device management server 1000. Each software module is implemented by the CPU 10 loading a device management program stored in the ROM 11, HDD 19, or the like into the RAM 12 and executing it. The device management server 1000 has a UI control unit 30, a device control unit 31, a schedule control unit 32, and a function control unit 33.

[0020] The UI control unit 30 has a device display unit 301, a schedule display unit 302, and a function display unit 303. The device display unit 301 controls the UI display of the device control unit 31. The schedule display unit 302 controls the UI display of the schedule control unit 32. The function display unit 303 controls the UI display of the function control unit 33. Each UI may be displayed on the display device 15 of the device management server 1000, or may be provided on a web browser via the network 3000.

[0021] The device control unit 31 includes a search setting reception unit 310, a device search unit 311, a device information management unit 312, and a device information storage unit 313. The search setting reception unit 310 receives a search range for finding devices to be managed, specified by the user on the search setting screen 600, and search exclusions. The search range and exclusions are specified by, for example, IP addresses. In this embodiment, devices with IP addresses specified as exclusions are managed as exclusions. Therefore, in this embodiment, the exclusions are treated as information for identifying devices to be excluded from management. The device search unit 311 searches for devices on the network according to the settings received by the search setting reception unit 310. Device search is performed using, for example, SNMP, IP Broadcast, SLP / Multicast, etc. The device search unit 311 acquires device information such as device names, product names, and IP addresses from the discovered devices. The device search unit 311 also has a function for acquiring / changing device information such as MIB (Management Information Base) security policy information. The device information management unit 312 manages the device information stored in the device information storage unit 313. The device information storage unit 313 is a storage unit that stores device information.

[0022] The schedule control unit 32 has a schedule setting reception unit 320, a schedule management unit 321, and a schedule storage unit 322. The schedule setting reception unit 320 receives user input on a schedule setting screen. The schedule management unit 321 generates a schedule for each function (task) in response to the user input, and also manages the schedules stored in the schedule storage unit 322. The schedule storage unit 322 stores the set schedule.

[0023] The function control unit 33 has 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. The power setting management unit 331 manages the power of the device in accordance with a power management schedule. The security policy setting management unit 332 manages the security of the device in accordance with a security schedule. The status setting management unit 333 collects status information from the device and manages the device status. The counter setting management unit 334 collects counter information from the device and manages the device status and consumables. The setting storage unit 335 stores the information collected from the device. In addition, the function control unit 33 communicates with the device 2000 on the network 3000 in order to manage the device using the power setting management unit 331, the security policy setting management unit 332, the status setting management unit 333, and the counter setting management unit 334. Here, the device information storage unit 313, schedule storage unit 322, and setting storage unit 335 are data recording media such as databases that run on the HDD 19, and store table data such as schedule lists, device lists, and function lists.

[0024] <Device software configuration> 4 is a diagram showing the software configuration on device 2000. Device 2000 has an information control unit 40. Information control unit 40 has multiple information management units for managing multiple dynamically changing information groups, and multiple information storage units for storing the information managed by each management unit. As the multiple information management units, information control unit 40 has a counter information management unit 401, an MIB information management unit 403, a power information management unit 405, a status information management unit 407, and a security policy information management unit 409. Furthermore, as information storage units corresponding to each information management unit, information control unit 40 has a counter storage unit 402, an MIB information storage unit 404, a power information storage unit 406, and a security policy information storage unit 410.

[0025] The counter information management unit 401 manages the number of printed pages and other information, and stores it in the counter storage unit 402. The MIB information management unit 403 manages MIB information, which is 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 410. The information control unit 40 also communicates with external devices such as the device management server 1000. The information control unit 40 receives requests from the device management server 1000 and transmits stored data to the device management server 1000 using SNMP or other protocols in response to the received request.

[0026] 5 to 9 show an example of the UI of the device management server 1000. The flow of creating a schedule for status, counter, security policy, and power management will be explained using FIGS. 5 to 9. First, the process of searching for devices to be managed on the network will be explained. The device management server 1000 searches for devices to be managed.

[0027] FIG. 5 is a diagram showing an example of a device discovery screen. When a device 501 is selected in the management UI 500 and the displayed discovery button 505 is further selected, the device management server 1000 displays a discovery setting screen 600. FIG. 6 is a diagram showing an example of the device discovery setting screen. The discovery setting screen 600 displays setting items: a discovery method 601, a search range 602, and an exclusion setting 603. The discovery method 601 is a setting item for specifying a device discovery method. An example of a device discovery algorithm is SNMP, but any method is acceptable. The search range 602 is a setting item for specifying a range for device discovery. For example, the search range is specified by IP address. In the example of FIG. 6, "192.168.10.90-192.168.10.120" is specified as the IP address for the search range. The exclusion setting 603 is an item for setting devices to be excluded from discovery. For example, the IP addresses of the excluded devices are set. Devices to be excluded from discovery are devices that are not to be managed by the device management server 1000. In the example of Fig. 6, "192.168.10.110" is set as the IP address to be excluded. Note that in order to exclude a certain range of devices, a range of IP addresses of the device group to be excluded may be specified. When the OK button 604 is selected, the device management server 1000 searches for devices on the network 3000 in accordance with the settings on the search settings screen 600. Note that during a search in this embodiment, IP addresses set in the exclusion settings 603 are excluded from the search targets.

[0028] An example of the UI after the search is shown in FIG. 5. The device search screen 506 displays device information as a device list 507. The device information includes, for example, the device name, host name, IP address, and serial number. The device information displayed in the device list 507 includes device information about devices acquired in the current search and device information acquired in previous searches and stored in the device information storage unit 313. Therefore, even if a device with an IP address has been excluded from the search targets in the current search by the exclusion setting 603, it will be displayed in the device list 507 if it has been searched in a previous search and its device information exists in the device information storage unit 313. In the examples of FIGS. 5 and 6, "192.168.10.110" has been excluded from the search targets, but Device3 corresponding to this IP address is displayed in the device list 507. In this embodiment, devices excluded from the search targets, such as Device3, are managed as devices not to be managed.

[0029] Next, the schedule settings for each device management function will be described. In this embodiment, the management settings for general functions and specific functions differ in the range of devices that they target. The general function is, for example, a function for acquiring information from a device. The specific function is, for example, a function related to power management and a function related to security settings.

[0030] First, the settings related to general functions will be described. To configure the settings related to general functions, the user selects Settings 502 in the management UI 500 to display a general function settings screen. Then, on the general function settings screen, the user configures the information to be acquired, the schedule for acquiring the information, and the devices to which the general functions will be applied. In this embodiment, the devices that are the targets of general functions such as information acquisition are managed devices. Therefore, devices that are managed as non-managed devices are not targets of the general functions. In a device list (not shown) that is displayed when configuring the devices to which the general functions will be applied, non-managed devices are not displayed, and only managed devices are displayed as selection candidates, and the user selects a device to which the general functions will be applied from the managed devices. The information to be acquired is, for example, information collected by the device, such as counter information such as the amount of ink remaining and the number of printed pages, and status information indicating the status of the device, such as an error.

[0031] FIG. 7 is a diagram showing an example of a schedule setting screen for an information acquisition function, which is a general function. On the schedule setting screen 701, an execution date and time 703 and a repetition interval 704 for acquiring information from a device are set. Multiple schedules can be set, and a list 707 of currently set schedules is displayed at the bottom. In the example shown in FIG. 7, a schedule is set to acquire status every 30 minutes starting at 1:00 PM on July 1, 2021. Also, by checking Execute at server startup 702, it is possible to set the device management server 1000 to acquire information from the device when it is started. Furthermore, if there are item-specific detailed settings, they can be set in the detailed settings 705. The schedule settings are saved by pressing Save 706. Schedules can be deleted or added as needed.

[0032] Next, settings related to specific functions will be described. Here, an example will be described in which power management 503 is selected as the specific function. Note that the process of selecting a device to apply and setting a schedule is the same when security policy 504 is selected. When power management 503 is selected, a device selection screen 801 for selecting a device to be subject to power management is displayed. FIG. 8 is a diagram showing an example of the device selection screen. A device list 802 displayed on the device selection screen 801 displays a list of selection candidates for devices to be managed by functions related to power management. The user selects a device for which power management settings are to be made in the device list 802. In this embodiment, devices that are subject to specific important functions such as power management include managed devices and unmanaged devices. This is to reduce the possibility of devices whose power is not managed or devices that may become security holes. Therefore, the device list 802 displays managed devices (e.g., Device 1 and Device 2) and unmanaged devices (e.g., Device 3) as selection candidates. The device list 802 displays, for example, device names, device information, and selection check boxes. When a device is selected and the Next button 803 is selected, the screen transitions to a schedule setting screen 901 for setting a power management schedule.

[0033] The device selection screen 801 may also display a target display 804 that limits the display depending on whether the devices displayed as selection candidates are managed or not. The target display 804 is a pull-down menu for selecting the target devices to be displayed in the device list 802, and "All," "Managed," and "Not Managed" can be selected. When "All" is selected, managed devices and not managed devices are displayed as selection candidates in the device list 802. When "Managed," devices that are managed as managed devices are displayed in the device list 802. When "Not Managed," devices that are managed as not managed devices are displayed in the device list 802.

[0034] FIG. 9 is a diagram showing an example of a power management schedule setting screen. The power management schedule setting screen 901 allows the user to set schedules such as turning off the device's power and restarting the device. The operation type 902 allows the user to select the type of power management process to be performed by the device, such as sleep, sweep release, restart, or power off. The execution start date and time 903 sets the date and time at which the process selected in the operation type will be executed. The repetition 904 allows the user to set the interval at which the process selected in the operation type will be repeated. Multiple schedules can be set. In the example shown in FIG. 9, a schedule is set to turn off the device's power every day at 22:00 starting from 22:00 on 2021 / 07 / 01. The schedule settings are saved by pressing Save 706.

[0035] The power management schedule setting screen 901 also displays the currently set schedule for power management. The currently set schedule for power management is displayed in an existing schedule list 906 for each management category (type) of device specified by the user. Display target type 905 is a pull-down menu for selecting the management type of devices to be displayed in the existing schedule list 906. In the display target type 905, "all," "managed," and "unmanaged" can be selected. Through the series of settings described using FIGS. 5 to 9, various information acquisition, power management, and security policy schedules are created for the selected device, and subsequent operations are performed.

[0036] The schedule setting process in the device management server 1000 will be described using the flowcharts shown in Figures 10 and 11. Note that each step in Figures 10 and 11 is implemented by the CPU 10 of the device management server 1000 loading a device management program from the HDD 19, ROM 11, etc. into the RAM 12 and executing it.

[0037] First, the device search process will be described. Fig. 10 is a flowchart showing the device search process. When managing devices, the device management server 1000 first searches for devices, as explained above. Device search can be performed each time, or can be performed periodically by setting a schedule.

[0038] In S1001, the search setting receiving unit 310 receives settings for searching for devices on the network. Specifically, the device search settings input to the search setting screen 600 displayed by the device display unit 301 are acquired. The device search settings include, for example, a search algorithm, a search range (first specification) for finding devices to be managed, and information for identifying devices not to be managed (second specification). The information for identifying devices not to be managed is, for example, IP addresses to be excluded. In the example shown in FIG. 6, SNMPv1 specified in the search method 601 is acquired as the search algorithm, the search range specified in the search range 602 is acquired as the first specification, and the IP addresses specified in the exclusion setting 603 are acquired as the second specification.

[0039] In S1002, the device search unit 311 determines whether the search settings acquired in S1001 include information for identifying devices to be excluded from management. That is, it determines whether there is an IP address exclusion setting 603. If there is an IP address exclusion setting, it determines that the information for identifying devices to be excluded from management is included, and proceeds to S1003. On the other hand, if there is no IP address exclusion setting, it determines that the information for identifying devices to be excluded from management is not included, and proceeds to S1004.

[0040] In S1003, the device search unit 311 performs a search process according to information for identifying devices to be excluded from management. Specifically, the device search unit 311 performs a search process in the search range (first designation) specified in S1001, excluding the IP addresses set to be excluded (second designation). In other words, the device search unit 311 does not perform a search for IP addresses specified for exclusion. In the example of FIG. 6, the device search unit 311 performs a device search in the search range "192.168.10.90-192.168.10.120" specified by IP addresses, excluding the IP address "192.168.10.110". In S1004, the device search unit 311 performs a normal search process in the search range (first designation) specified in S1001. The device search unit 311 searches for devices in the search range specified in S1001.

[0041] In S1005, the device information management unit 312 stores the device information newly acquired by the search process in the device information storage unit 313. Specifically, based on the search results of the search process in S1003 or S1004, the device search unit 311 performs a process of adding the device information to the device list managed by the device information storage unit 313. The device information includes, for example, the device name, host name, IP address, serial number, etc.

[0042] In S1006, the device information management unit 312 determines whether a device to be excluded from management, i.e., a device specified to be excluded from device discovery, is in the device list. Specifically, the device information management unit 312 determines whether a device corresponding to an IP address set to be excluded in the exclusion setting 603 on the discovery setting screen 600 is in the device list. The process of S1006 is performed because a device specified to be excluded from the current discovery may exist in the device list due to a previous discovery. In the example shown in FIG. 5, the device corresponding to "192.168.10.110," which is the IP address specified in the exclusion setting 603, is listed in the device list as Device3. If a device to be excluded from management is in the device list, the process proceeds to S1007. On the other hand, if a device to be excluded from management is not in the device list, the process ends.

[0043] In S1007, the device information management unit 312 registers devices that are not to be managed based on information for identifying devices that are not to be managed. The device information management unit 312 stores the device information of the devices that are not to be managed as information on devices that are not to be managed in the device information storage unit 313. In the example of Fig. 5, the device information management unit 312 stores and manages the device information of Device3, which has an IP address of "192.168.10.110", in the device information storage unit 313 as a device that is not to be managed. This ends the device search process.

[0044] Next, we will explain how to control the selection candidates for devices displayed on the setting screen for setting the target devices when setting a function. When creating a schedule in the device management server 1000, the item of the function to be set (e.g., setting 502, power management 503, security policy 504) is selected, and schedule setting begins on a device selection screen (e.g., device selection screen 801). The device selection screen displays selection candidates for devices to be managed by the function to be set.

[0045] In this embodiment, the first function for acquiring information such as status information and counter information from devices targets only managed devices. On the other hand, the devices targeted by important specific second functions, such as functions related to security settings and power management, also include devices designated as unmanaged devices. That is, when configuring the first function, only managed devices are selected as candidates, and devices corresponding to device information managed as unmanaged devices are not selected as selection candidates. On the other hand, when configuring the second function, both managed devices and devices selected as unmanaged devices can be selected as selection candidates. Details of the process in which the device display unit 301 of the UI control unit 30 controls the display of selection candidates for devices that provide this function in accordance with the function selected as the setting target are described with reference to FIG. 11 . Note that in this embodiment, an example is described in which a power management function and a security function are set as specific second functions for which management can be selected. However, the functions targeted by the second function are not limited to these.

[0046] 11 is a flowchart showing a process for displaying device selection candidates. In S1101, the device display unit 301 of the UI control unit 30 determines whether the function selected as the setting target is a function that can select an unmanaged device as a selection candidate. That is, it determines whether the function selected as the setting target is a second function that is a specific function. If the function selected as the setting target is the second function that is a specific function, it is determined that the function can select an unmanaged device as a selection candidate, and the process proceeds to S1102. On the other hand, if the function selected as the setting target is not the second function that is a specific function, it is determined that the function cannot select an unmanaged device as a selection candidate, and the process proceeds to S1105. That is, if the function is the first function, the process proceeds to S1105.

[0047] In S1102 to S1110, the device display unit 301 controls the selection candidates to be displayed in the device list 802 in accordance with the user's selection in the target display 804. In S1102, the device display unit 301 acquires the target display setting set on the UI of the device selection screen. The target display setting displays the type of devices that are selection candidates, and "All," "Managed," and "Not Managed" can be selected. "All" is an option that displays both managed devices and non-managed devices as selection candidates. The target display setting is selected by the user in the target display 804 on the device selection screen 801. FIG. 12 is a diagram showing an example of a screen for setting the target display. When the pull-down menu of the target display 804 on the device selection screen 801 is selected, the target display settings of "All," "Managed," and "Not Managed" are displayed. The device display unit 301 acquires the result of the user's selection in the target display 804.

[0048] In S1103, the device display unit 301 determines whether the target display setting acquired in S1102 is "managed device." That is, it determines whether the setting for displaying selection candidates for the device selected by the user in the target display 804 is a setting for displaying only managed devices. If the target display setting is "managed device," the process proceeds to S1104. On the other hand, if the target display setting is not "managed device," the process proceeds to S1106.

[0049] In S1104, the device display unit 301 determines whether there are any devices to be managed. Specifically, the device display unit 301 determines whether information about devices to be managed is stored in the device information storage unit 313. If there are any devices to be managed, the process proceeds to S1105. On the other hand, if there are no devices to be managed, the device display is not performed and the process returns to S1102. Note that if there are no devices to be managed, an error notification may be issued to the effect that there are no devices to be selected.

[0050] In S1105, the device display unit 301 displays the management target devices as selection candidates in the device list 802. The device display unit 301 acquires the device information of the management target devices stored in the device information storage unit 313 via the device information management unit 312, and displays the management target devices. After displaying the management target devices as selection candidates in the device list 802, the process returns to S1102.

[0051] In S1106, the device display unit 301 determines whether the target display setting acquired in S1102 is "unmanaged device." That is, it determines whether the setting for displaying selection candidates for the device selected by the user in the target display 804 is a setting for displaying only unmanaged devices. If the target display setting is "unmanaged device," the process proceeds to S1107. On the other hand, if the target display setting is not "unmanaged device," the process proceeds to S1109.

[0052] In S1107, the device display unit 301 determines whether there are any devices not to be managed. Specifically, the device display unit 301 determines whether information about devices managed as not to be managed is stored in the device information storage unit 313. If there are any devices not to be managed, the process proceeds to S1108. If there are no devices not to be managed, the process returns to S1102 without displaying the devices. Note that if there are no devices not to be managed, an error notification may be issued to the effect that there are no devices to be selected.

[0053] In S1108, the device display unit 301 displays the unmanaged devices as selection candidates in the device list 802. The device display unit 301 acquires device information of the unmanaged devices stored in the device information storage unit 313 via the device information management unit 312, and displays the unmanaged devices. After displaying the unmanaged devices as selection candidates in the device list 802, the process returns to S1102.

[0054] 13 will be used to explain an example of the display of the device list 802 when "Not Managed" is selected in the target display 804 in the case where there is an unmanaged Device3 with an IP address of "192.168.10.110" as shown in FIGS. 6 and 5. In S1107, the device display unit 301 determines that there is a device 3 with "192.168.10.110" as an unmanaged device, and the process proceeds to S1008. The device display unit 301 then lists Device3, which is an unmanaged device, as a selection candidate for the unmanaged device and displays it in the device list 802. FIG. 13 is a diagram showing an example in which an unmanaged device is displayed as a selection candidate. In this way, by performing control to display Device3 as an unmanaged device in device selection for power management schedule setting, the unmanaged device can be selected as a target for power management.

[0055] S1109 is a process performed when the target display setting acquired in S1102 is neither "managed devices" nor "unmanaged devices," i.e., "all." In S1109, the device display unit 301 determines whether there are any managed and unmanaged devices in order to display all devices. Specifically, the device display unit 301 determines whether information about devices managed as managed devices and information about devices managed as unmanaged devices is stored in the device information storage unit 313. If there are any managed and unmanaged devices, proceed to S1110. On the other hand, if there are no managed and unmanaged devices, no devices are displayed and return to S1102. Note that if there are no managed devices, an error notification may be sent to the effect that there are no devices to be selected.

[0056] In S1110, the device display unit 301 displays all devices, i.e., managed devices and unmanaged devices, in the device list 802 as selection candidates. The device display unit 301 acquires device information for all devices stored in the device information storage unit 313 via the device information management unit 312, and displays all devices. After displaying all devices as selection candidates in the device list 802, the process returns to S1102. The process in FIG. 11 is repeated until a device is selected in the device list 802 and the Next button 803 is selected.

[0057] According to this embodiment, devices excluded from a search during a search can be managed as unmanaged devices. Unmanaged devices are generally not subject to management, but it is possible to include unmanaged devices in specific functions such as power management and security management. Therefore, even if a specific device is set as unmanaged, it is possible to manage specific functions, providing detailed device management functions that meet the needs of device administrators.

[0058] (Second embodiment) In the first embodiment, the device information corresponding to the IP addresses excluded during the search is managed as device information not to be managed by the device information management unit 312, is continuously held in the device information storage unit 313, and is made the target of specific functions such as power management. In the present embodiment, an example will be described in which the device is also excluded from the target of specific functions such as power management and security policies.

[0059] When the user wishes to end management of a device by the device management server 1000, the user selects the device that the user does not want to manage from a list of all device information stored in the device information storage unit 313, and instructs the device information storage unit 312 to delete the corresponding device information. Upon receiving the deletion instruction via the UI, the device information management unit 312 deletes the specified device information from the device information storage unit 313. When executing a schedule for a specific item such as power management or security policy, the device management server 1000 controls the device whose device information has been deleted from the device information storage unit 313 so that it does not operate even if there is an execution schedule for the device. This control will be described using FIG. 14.

[0060] Fig. 14 is a flowchart showing the process when a schedule is executed. The process shown in Fig. 14 is realized by the CPU 10 executing the device management software. This process starts when a pre-set execution schedule starts operating at the set date and time.

[0061] In S1401, the schedule management unit 321 reads the device to be operated from the schedule storage unit 322, and proceeds to S1402. In S1402, the schedule management unit 321 determines whether the device to be operated is a device outside the scope of management. If there are multiple devices to be operated, the schedule management unit 321 determines each one one by one. If the device is outside the scope of management, proceed to S1403, and if not, proceed to S1404.

[0062] In S1403, the device information management unit 312 determines whether device information for the device determined in S1402 to be a device not subject to management exists in the device information storage unit 313. If the device information exists in the device information storage unit 313, the process proceeds to S1404. On the other hand, if the device information does not exist in the device information storage unit 313, the process proceeds to S1405. In S1404, the schedule management unit 321 cooperates with each management unit in the function control unit 33 to execute the processing of the scheduled function on the target device. Thereafter, the process proceeds to S1405.

[0063] In S1405, the schedule management unit 321 determines whether the device to be processed is the last device among the execution target devices read in S1401. If it is the last device, the process ends. If not, the process proceeds to S1406. In S1406, the schedule management unit 321 advances the previously read execution target device to the next target device, and the process returns to S1402.

[0064] Through this series of operations, when a schedule for a specific item such as power management or security policy is executed, if a device that is not managed is deleted from the device list, the execution process will not be performed even if there is an execution schedule for that device. By deleting the device information of a device that is not managed by the device management server 1000 from the device information storage unit 313, the user can exclude that device from the schedules of all functions, including specific functions such as power management and security policy.

[0065] In the present embodiment, an example has been described in which devices corresponding to device information deleted from the device information storage unit 313 are excluded from the target when a schedule is executed, but this is not limited to when a schedule is executed. For example, a device corresponding to device information deleted from the device information storage unit 313 is also excluded from selection candidates when setting a schedule. In this way, when device information corresponding to a device that is not subject to management is deleted, the device is excluded from management by the device management server 1000, including power management and security management.

[0066] (Third embodiment) When setting schedules for security policies or power management, it may be possible to display the currently set schedule. In this embodiment, a form will be described in which the currently set schedule is displayed in the existing schedule list 906 on the schedule setting screen 901 according to a display target type selected from "All," "Managed," and "Not Managed." Control of the display process for the currently set schedule will be described with reference to FIG. 15.

[0067] When creating each schedule in the device management server 1000, as explained above, the function items to be set are selected in the UI shown in Fig. 5, and schedule setting is started from the respective device selection screens as shown in Fig. 8. After the device is selected, the schedule setting screen shown in Fig. 9 is displayed. Fig. 15 is a flowchart showing the display processing of the schedule setting screen. The processing shown in Fig. 15 is realized by the CPU 10 executing the device management software.

[0068] In S1501, the schedule display unit 302 displays setting items such as execution date and time, repetition setting, etc. required for schedule setting. As a result, the operation type 902, execution start date and time 903, and repetition 904 shown in FIG. 9 are displayed. In S1502, the schedule display unit 302 determines whether the selected function is a function that can select an unmanaged device. In other words, it determines whether the function selected as the setting target is a second function, which is a specific function. This processing is the same as that of S1101. If it is a function that can select an unmanaged device, proceed to S1503. If it is a function that cannot select an unmanaged device, proceed to S1506.

[0069] In S1503, the schedule setting reception unit 320 performs processing to read the device type of the display target set on the schedule setting screen 901. Specifically, the selection of the display target type 905 on the schedule setting screen 901 is read. In the display target type 905, "all," "managed," and "unmanaged" can be selected, and the user selects the device type of the schedule set as the destination that they wish to display.

[0070] In S1504, the schedule display unit 302 determines whether the display type selected in the display target type 905 is a managed device. If it is a managed device, the process proceeds to S1505. If it is not a managed device, the process proceeds to S1507. In S1505, the schedule display unit 302 determines whether there is a schedule for the managed device. Specifically, the schedule display unit 302 checks with the schedule management unit 321 whether a schedule for the managed device is stored in the schedule storage unit 322. If there is a schedule for the managed device, the process proceeds to S1506. If there is no schedule for the managed device, the process ends without displaying the schedule, and waits for the next user instruction. In S1506, the schedule display unit 302 performs schedule display processing for the managed device. The schedule display unit 302 displays the schedule for the managed device set via the schedule management unit 321 in the existing schedule list 906, based on the data stored in the schedule storage unit 322.

[0071] In S1507, the schedule display unit 302 determines whether the display type selected in the display target type 905 is an unmanaged device. If it is an unmanaged device, the process proceeds to S1508. If it is not an unmanaged device, the process proceeds to S1510. In S1508, the schedule display unit 302 determines whether there is a schedule for the unmanaged device. Specifically, the schedule display unit 302 checks with the schedule management unit 321 whether a schedule for the unmanaged device is stored in the schedule storage unit 322. If there is a schedule for the unmanaged device, the process proceeds to S1509. If there is no schedule for the unmanaged device, the process ends without displaying the schedule, and waits for the next user instruction. In S1509, the schedule display unit 302 performs processing to display the schedule for the unmanaged device. The schedule display unit 302 displays the schedule for the unmanaged device set via the schedule management unit 321 in the existing schedule list 906, based on the data stored in the schedule storage unit 322. In the example shown in Figure 9, the existing schedule for unmanaged devices is displayed as "Type: Power Off", "Execution Time: 2021 / 0801 23:00", and "Repeat: Daily" for Device3.

[0072] In S1510, the schedule display unit 302 determines whether there are schedules for managed and unmanaged devices in order to display the schedules of all devices. Specifically, the schedule display unit 302 checks with the schedule management unit 321 whether the schedules for managed devices and unmanaged devices are stored in the schedule storage unit 322. If there are schedules, the process proceeds to S1511. If there are no schedules, the process ends without displaying the schedules, and the process waits for the next user instruction. In S1511, the schedule display unit 302 performs a process of displaying schedules for all devices, including managed and unmanaged devices. Based on the data stored in the schedule storage unit 322, the schedule display unit 302 displays the schedules of all devices set via the schedule management unit 321 in the existing schedule list 906.

[0073] According to this embodiment, the function for selecting the display of non-managed devices allows the user to select between displaying managed, non-managed, or all schedules. This allows the display of non-managed schedules that have already been set, and enables the device administrator to recognize and manage the currently set schedules.

[0074] (Other embodiments) The present invention may be applied to a system consisting of multiple devices (e.g., a host computer, an interface device, a reader, a printer, etc.), or to an apparatus consisting of a single device (e.g., a copier, a facsimile machine, etc.). The object of the present invention can also be achieved by supplying a recording medium on which program code that realizes the functions of the above-described embodiments is recorded to a system or apparatus, and having a computer in the system or apparatus read and execute the program code stored in the recording medium. In this case, the program code itself read from the recording medium realizes the functions of the above-described embodiments, and the program code itself and the recording medium on which the program code is stored constitute the present invention.

[0075] The present invention also includes cases where an operating system (OS) running on a computer performs some or all of the actual processing based on the instructions of the program code, thereby realizing the functions of the above-mentioned embodiments. Furthermore, the present invention also applies to cases where program code read from a storage medium is written to memory in a function expansion card inserted into a computer or in a function expansion unit connected to a computer. In such cases, a CPU or the like in the function expansion card or function expansion unit performs some or all of the actual processing based on the instructions of the written program code, thereby realizing the functions of the above-mentioned embodiments.

[0076] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program.The present invention can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.

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

Claims

1. An information processing apparatus that manages device information of a plurality of devices to be managed in a storage means, a management unit that manages each of the plurality of devices included in the device information in the storage unit as a managed device or a non-managed device; a function control means for controlling the execution of a first function that can be used only for devices managed as managed devices, and a second function that is a specific function different from the first function and can be used for devices managed as managed devices and devices not managed as managed devices; an information processing device characterized by having a control means that, when a target device for the first function is to be selected, devices managed as managed objects are selected as selection candidates, and devices managed as unmanaged objects are not selected as selection candidates, and when a target device for the second function is to be selected, devices managed as managed objects and devices managed as unmanaged objects are selected as selection candidates.

2. The device further comprises a receiving means for receiving settings including a first specification of a search range for finding devices to be managed and a second specification of information for identifying devices not to be managed when setting up a search for devices on a network, 2. The information processing apparatus according to claim 1, wherein when device information of a device corresponding to the second specification included in the accepted setting is stored in the storage means, the device information is managed as device information not to be managed.

3. 3. The information processing apparatus according to claim 1, wherein the first function is a function for acquiring status information or counter information from a device via a network.

4. 4. The information processing apparatus according to claim 1, wherein the second function is a function relating to security settings for a device via a network or a function relating to power management.

5. 5. The information processing apparatus according to claim 1, wherein a device corresponding to the device information managed as an unmanaged device and deleted from the storage means is excluded from the targets of the second function.

6. 6. The information processing apparatus according to claim 1, wherein the information processing apparatus can display a schedule of the second function for a device corresponding to device information managed as an unmanaged device.

7. 7. The information processing apparatus according to claim 6, wherein an existing schedule of the second function for a device corresponding to device information managed as an unmanaged device is displayed on the setting screen of the schedule of the second function.

8. A control method for an information processing apparatus that manages device information of a plurality of devices to be managed in a storage means, comprising: a step of managing each of the plurality of devices included in the device information in the storage means as a managed device or a non-managed device; controlling the execution of a first function that can only target managed devices as managed devices and a second function that is a specific function different from the first function and can target managed and unmanaged devices; a step of controlling the information processing device so that when a target device for the first function is to be selected, devices managed as managed objects are selected as selection candidates, and devices managed as unmanaged objects are not selected as selection candidates, and when a target device for the second function is to be selected, devices managed as managed objects and devices managed as unmanaged objects are selected as selection candidates.

9. A program for causing a computer to function as each of the means of the information processing apparatus according to any one of claims 1 to 7.

Images