JP2000235547A - Resource management system and method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To always manage that which resource is included and which change is caused in each device in a computer network. SOLUTION: In the computer network 1, a managing device 10 inquires software resources and hardware resources (device resources) installed in each device 20 to be managed through a communication network 30. Each device 20 checks which device resources are included by retrieving an execution file (*exe) or the like in a file system in accordance with an inquiry and transmits resource data showing a current state to the device 10. The device 10 stores and manages the resource data, detects the number of device resources or the existence of a specific device resource or the like in each managed device 20 and executes management for informing a system manager of the detected result or the like.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a resource management system and a resource management system for managing hardware resources and software resources of devices such as computers connected to each other via a network or any one of them (device resources). The present invention relates to a device, a managed device, and a method thereof.

[0002]

2. Description of the Related Art A computer network system is used in which a plurality of computers are connected via a network to process and transfer data. In such a computer network, in order to prohibit unauthorized use of each computer and ensure proper operation of the system, what kind of hardware resources and software resources (device resources) must be assigned to each computer in the system.
Needs to be managed at all times.

For example, JP-A-63-114337, JP-A-4-79446, and JP-B-1-1606.
No. 6 and Japanese Patent Publication No. 7-44541 (References 1 to 4).
4) discloses an electronic mail system and a data transfer system using such a network system. However, each of the methods disclosed in these documents only discloses a method of determining a transfer destination and a route of mail (data) in association with a user's organization and name, and the like. It does not disclose a method that can always accurately grasp device resources.

[0004]

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems of the prior art, and in a network system in which a plurality of computers and other devices are connected via a network device, each device is A resource management system, a resource management device, and a resource management device capable of constantly managing what hardware resources and software resources (device resources) are possessed, and what kind of change has occurred in each device resource. It is an object to provide a management device and these methods.

The present invention also provides a resource management system and a resource management system which can display resource information of each device constituting a network system, facilitate system management tasks, and reduce user's labor required for system management tasks. It is an object to provide a management device, a managed device, and a method thereof.

[0006]

[Resource management system] In order to achieve the above object, a resource management system according to the present invention includes a resource management device and one or more managed devices. A resource management system that manages device resources of the managed device, wherein each of the managed devices generates resource data indicating device resources of the managed device, and Resource data transmitting means for transmitting the generated resource data, wherein the resource management device receives the resource data from each of the managed devices; and the received managed device. Resource data management means for managing each of the resource data.

[0007] Preferably, the resource management device responds to at least a device resource change notification from the managed device.
A resource data transmission requesting unit for requesting each of the managed devices to transmit the resource data, wherein in each of the managed devices, the resource data generating unit responds at least to the request for transmitting the resource data. Generating the resource data indicating the device resources of each of the managed devices, wherein the resource data transmitting unit converts the generated resource data into at least the resource data in response to a request for transmission of the resource data. Sent to the management device,
Alternatively, when the device resource is changed, a notification of the change of the device resource is transmitted to the resource management device.

[0008] Preferably, in the resource management device, the resource data management means includes standard data storage means for storing standard data indicating device resources which each of the managed devices has as a standard, and receives from the managed device. Generating difference data indicating a difference between the received resource data and the standard data corresponding to the received resource data, the resource data received from each of the managed devices, First resource management means for managing the obtained difference data.

[0009] Preferably, in the resource management device, the resource data management means is configured to control each of the managed devices corresponding to the received resource data based on the resource data received from the managed device. A specific resource determining unit that determines whether or not a predetermined specific device resource is included; and the specific device resources included in each of the managed devices, based on a result of the determination, and each of the managed devices. And second resource management means for managing the resource data.

[0010] Preferably, in the resource management device, the resource data management means determines whether each of the managed devices corresponding to the received resource data is based on the resource data received from the managed device. A specific resource determining unit that determines whether or not a predetermined specific device resource is included; and the specific device resources included in each of the managed devices, based on a result of the determination, and each of the managed devices. And second resource management means for managing the resource data.

Preferably, in each of the managed devices, the resource data generating means converts the resource data indicating the device resources of the managed device into a format suitable for input to the resource data receiving means; Alternatively, the resource data transmitting unit generates the resource data in a format (first format) different from this format, and converts the resource data generated in the first format into a format suitable for input to the resource data receiving unit. (2nd format) and transmit it to the resource management device.

[Resource Management Apparatus] The resource management apparatus according to the present invention is a resource management apparatus that manages the device resources of each of one or more managed apparatuses. Resource data receiving means for generating resource data indicating device resources of the management device, transmitting the generated resource data to the resource management device, and receiving the resource data from each of the managed devices; , Resource data management means for managing the received resource data of each of the managed devices.

Preferably, each of the managed devices generates the resource data indicating the device resources of each of the managed devices at least in response to a request for transmission of the resource data. In response to the transmission request, the generated resource data is transmitted to the resource management device, or, when the device resource is changed, a notification of the change of the device resource is sent to the resource management device. Resource data transmission request means for transmitting to the device and requesting the managed device to transmit the resource data in response to at least a device resource change notification from the managed device.

[0014] Preferably, the resource data management means includes standard data storage means for storing standard data indicating device resources which each of the managed devices has as a standard, and resource data received from the managed device. A difference data generating unit that generates difference data indicating a difference from the standard data corresponding to the received resource data, the resource data received from each of the managed devices, and the generated difference data. And first resource management means for managing

[0015] Preferably, the resource data management means determines, based on the resource data received from the managed device, each of the managed devices corresponding to the received resource data by a predetermined identification. Specific resource determining means for determining whether or not the device resource is included, and based on the result of the determination, the specific device resource included in each of the managed devices, and the resource data of each of the managed devices. And second resource management means for managing.

Preferably, each of the managed devices accepts the transmitted setting of the setting information, determines whether or not the setting of the setting information has been accepted, and accepts the setting of the setting information. A setting information generating unit for requesting the resource management device to transmit the setting information, and generating setting information to be set for each of the managed devices; Setting information transmitting means for transmitting information to each of the managed devices.

[Managed Device] The managed device according to the present invention is a managed device in which device resources are managed by a resource management device, and the resource management device is configured to receive data from each of the managed devices. Resource data generating means for receiving the resource data, managing the resource data of each of the received managed devices, and generating resource data indicating device resources of the managed device; Resource data transmitting means for transmitting the generated resource data.

Preferably, the resource management device responds to at least a device resource change notification from the managed device.
Requesting each of the managed devices to transmit the resource data, wherein the resource data generating means includes at least the resource indicating the device resources of each of the managed devices in response to the request for transmitting the resource data. Generating resource data, the resource data transmitting means transmitting the generated resource data to the resource management device at least in response to a request for transmission of the resource data, or changing the device resource. When there is, a notification of the change of the device resource is transmitted to the resource management device.

Preferably, the resource data generating means converts the resource data indicating the device resources of the managed device into a format suitable for input to the resource data receiving means, or a format different from this format. Generated in the first format, and the resource data transmitting unit converts the resource data generated in the first format into a format (second format) suitable for input to the resource data receiving unit. Converted and transmitted to the resource management device.

Preferably, the resource management device generates setting information to be set for each of the managed devices, and transmits the generated setting information to each of the managed devices in response to a request. Setting information accepting means for accepting the setting of the received setting information, determining means for judging whether or not the setting of the setting information is accepted, and the resource management when the setting of the setting information is not accepted. Setting information requesting means for requesting the device to transmit the setting information.

[Operation of Resource Management System] In the resource management system according to the present invention, for example, one management computer (resource management device) and this resource management device are used to control software resources and hardware resources or these resources. A plurality of computers (managed devices), one of which (device resources) is managed, is connected via a communication network such as a LAN, and performs device resource management of a computer network that transmits and receives data to and from each other.

[Operation of Resource Management Device and Managed Device]
In the resource management system according to the present invention, for example, in response to a user operation, or when receiving a notification from the managed device that device resources have been changed, the resource management device It inquires about the device resources installed in each of the managed devices via the communication network.

Each of the managed devices (including the managed device itself and peripheral devices connected to the managed device)
For example, in response to an inquiry from the resource management device, the API and registry of the operating system (OS) are checked, or the execution file (* .exe) in the file system is searched to determine which managed device is It is checked whether the managed device has such device resources, and resource data indicating the current state of the device resources of the managed device is generated and transmitted to the resource management device. Or,
For example, when the user installs or uninstalls new software, the managed device notifies the management device that the device resources have been changed.

When resource data is received from each managed device, the resource management device stores and manages the received resource data for each managed device. Furthermore, the resource management device compares, for example, device resources that each managed device should have as standard with device resources indicated by the received resource data, and displays information indicating excess or deficiency between these resources. Is stored and managed and displayed to the system administrator. Also,
Furthermore, the resource management device detects, for example, whether or not there is a specific device resource that must not be installed on the managed device among the device resources indicated by the received resource data, and stores and manages the detection result. , Displayed to the system administrator.

[Resource Data Transmission Request Means] In the management apparatus of the resource management system according to the present invention, the resource data transmission request means responds to, for example, an operation for managing the resource management apparatus by a user (system administrator). ,
At regular time intervals or when a notification of a device resource change is received from a managed device, a signal requesting transmission of resource data is transmitted to each managed device.

[Resource Data Receiving Means] The resource data receiving means receives the resource data transmitted from each of the managed devices via the communication network in response to the transmission request of the resource data.

[Resource Data Management Means] The resource data management means is a device resource database of the managed device.
It stores and manages the resource data received from each of the managed devices.

[Standard Data Storage Unit] The standard data storage unit stores, for example, standard data that is set in advance for each managed device and indicates a standard resource that each managed device has as a standard.

[Difference Data Generation Means] The difference data generation means compares the current state of the device resources of the managed device indicated by the received resource data with the standard resources of the managed device, and finds out as a result of the comparison. Create difference data indicating excess or deficiency with respect to the standard resource of each managed device.

[First Resource Management Means] The first resource management means is a database of the received resource data of each managed device and the difference data. The first resource management means stores these data and performs system management. These data are managed, for example, displayed according to the search operation of the user. In this way, the first resource management means displays the device resources indicated by the difference data, so that the system administrator of the company allows the user (employee) of each managed device to use his or her own computer (managed device). It is possible to monitor whether or not hardware and software unrelated to the execution of company operations are installed.

[Specific Resource Determining Means] The specific resource determining means is, for example, a game software such as a game software which is determined to be unfavorable for improving the work efficiency regardless of the performance of the business of the company (specific software). Designated software / hardware (equipment resources) that must be installed by all staff, such as (equipment resources) and process management software or communication boards, was previously received from the system administrator and received from the managed equipment. It is determined whether or not such a specific device resource is included in the device resource indicated by the resource data.

[Second Resource Management Means] The second resource management means stores the resource data of each managed device and the result of the judgment on the specific device resource, and further responds to the operation of the system administrator. Management such as displaying these is performed. In this way, the second resource management unit manages the presence or absence of a specific device resource for each managed device, so that the system administrator can, for example, remove undesirable software (device resources) from the computer system. Alternatively, users who have not installed essential software (device resources) can be encouraged to do so.

[Setting Information Generating Means] The setting information generating means is used for managing the managed device, such as the user name of the managed device and its contact information, and generates setting information set in the managed device.

[Setting Information Transmitting Means] The setting information transmitting means transmits the generated setting information to the requested managed device when the managed device requests the transmission of the setting information.

[Resource Data Generation Means] In the managed device, for example, when there is a request for transmission of resource data from the management device, the resource data generation means checks the OS API or the like as described above, and The hardware and software (device resources) installed in the management device are checked, and resource data indicating the device resources of the managed device determined as a result of the check is generated in a standard format independent of the input format of the management device. .

[Resource Data Transmission Means] The resource data transmission means responds to a request from the resource management device, and inputs the standard format resource data generated by the resource data generation device as described above to the management device. The data is converted into a suitable format and transmitted to the resource management device via the communication network. In addition, when there is a change in the device resources of the managed device, the resource data transmitting unit notifies the management device of the change.

[Setting Information Receiving Unit] The setting information receiving unit receives the setting information (user name and its contact information; management information, etc.) transmitted from the management device. It is stored as a part of the resource data on a hard disk or the like.

[Determining Means] The determining means reads resource data from the setting information receiving means of the managed device, for example, and determines whether or not the read resource data contains setting information.

[Setting Information Requesting Unit] The setting information requesting unit includes setting information in the resource data because, for example, the power of the managed device (or the peripheral device connected thereto) has been cut off without backup. If not, it requests the resource management device to transmit the setting information.

[Resource Management Method] A resource management method according to the present invention is a resource management method in which a resource management device manages device resources of one or more managed devices. Generates resource data indicating the device resources of the managed device, transmits the generated resource data to the resource management device, and the resource management device sends the resource data from each of the managed devices. Receiving resource data and managing the received resource data of each of the managed devices;

[Recording Medium] A first recording medium according to the present invention is a resource management device for managing device resources of at least one managed device, wherein each of the managed devices includes the managed device. A resource data receiving step of generating resource data indicating a device resource of a device, transmitting the generated resource data to the resource management device, and receiving the resource data from each of the managed devices. And a resource data management step of managing the received resource data of each of the managed devices.

[0042]

DESCRIPTION OF THE PREFERRED EMBODIMENTS [First Embodiment] A first embodiment of the present invention will be described below.

[Computer Network 1] FIG.
FIG. 1 is a diagram illustrating a configuration of a computer network 1 to which a first device resource management method according to the present invention is applied.
As illustrated in FIG. 1, a computer network 1
Is a single management device 10, a plurality of managed devices 20-i
(I = 1,..., N; hereinafter, the managed devices 20-1 and 20-2)
In the case where any one of 0-n is indicated without being specified, the device is simply referred to as a managed device 20) so that data is transmitted / received to / from each other via a communication network 30 such as a LAN, an ISDN communication network, or a dedicated data line. Connected and configured.

The computer network 1 shown in FIG.
, The management device 10 communicates with the managed device 20 via the communication network 30 in response to a user operation, for example.
Inquire each of them about the installed software resources and hardware resources or any of them (device resources).

Each of the managed devices 20 is
In response to the inquiry from the server, by searching for an executable file (* .exe) in the file system or the like, it is checked what kind of device resources it has, and resource data indicating its current state is generated. It is transmitted to the management device 10.

Upon receiving the resource data from each of the managed devices 20, the resource management device 10 stores the resource data for each of the managed devices 20, and furthermore, determines whether the device resources of each of the managed devices 20 are excessive or insufficient. It performs management such as detecting the presence or absence of a specific device resource and notifying the system administrator.

[Management Device 10 / Managed Device 20] The management device 10 and the managed device 20 include a CPU 100, an input device 102, a display device 104, a storage device 106, and a communication device 110. In other words, the management device 10 and the managed device 20 are the same in that both employ a configuration of a computer having a data communication function.
0 is used by the system administrator of the computer network 1, executes the system management program 4 (described later with reference to FIG. 2), is used by the system administrator of the computer network 1, and the managed device 20 5 (described later with reference to FIG. 6),
It differs in that it is used by general users of the computer network 1.

[CPU 100] The CPU 100 is composed of a microprocessor, a memory, and their peripheral circuits (none of which are shown).
0, an operating system (OS) 6 supplied via a recording medium 108 such as a CD and a magneto-optical disk (MO) and stored in a storage device 106, and software such as a system management program 4 or a managed program 5 in a memory. And run it. Note that CP
The U100 is provided with a connector, a slot, and the like (neither is shown) so that devices such as a video card and a hard disk device can be added.

[Input Device 102] The input device 102 includes operation input devices such as a keyboard and a mouse.
By accepting the operation of the system administrator or general user for the management device 10 and the managed device 20, the CPU 10
Output for 0.

[Display Device 104] The display device 104
A CD display device or a CRT display device,
A GUI image, management information image, and the like input from 100 are displayed and shown to a system administrator or a general user.

[Storage Device 106] The storage device 106 is a storage device such as a hard disk device (HDD), a flexible disk device (FDD), a CD-ROM device, and an MO device, and is controlled by software executed by the CPU 100. The CPU 100 operates to store data supplied from the CPU 100 and reproduces the stored data and the data supplied via the recording medium 108 to execute the CPU 10 operation.
Output to the 0 side.

[Communication Device 110] The communication device 110
An adapter device for an AN, a TA or a modem for an ISDN communication line, which operates under the control of software executed by the CPU 100, and
To send and receive data to and from the management device 10 or the managed device 20 via the.

[Software Configuration of Management Device 10] FIG.
FIG. 3 is a diagram illustrating a configuration of software executed by the management device 10 illustrated in FIG. 1. In FIG. 2, software that is not directly related to the description of the present invention is omitted for simplicity of illustration and description. As shown in FIG. 2, the management device 10 executes the system management program 4 and the OS 6.

[OS6] OS6 is operating system software such as OS / 2 (trade name of IBM Corporation) or Windows 95/98 (trade name of Microsoft Corporation). In the management apparatus 10, hardware control and software execution control are performed. And so on.

[System Management Program 4] The system management program 4 includes a communication unit 40, a data analysis unit 42, an input unit 44, a display unit 46, and a database unit 48. The communication unit 40 includes a transmission unit 400 and a reception unit 4
The database unit 48 includes a system management database (DB) 480 and a personnel / organization DB 482.
And a device resource information DB 484. The system management program 4 realizes the following functions of the management device 10 by these components.

[Resource Information Collection / Management] In other words, the system management program 4 sets the keywords set for each of the managed devices 20 via the communication network 30 (the keywords are set for each of the managed devices 20 in order to identify the user). Information, for example, an employee (user) using the managed device 20
, And resource data indicating device resources are collected, stored, and managed.

The system management data includes, for example,
Information unique to each managed device 20 (serial number,
Device name, network address, etc.), hardware (memory capacity, video card, additional storage device, etc.) and software (type of OS6, application software,
Standard resource data indicating plug-ins, executable files, etc.)
And the employee number of each user of the managed device 20;
Additional information indicating contact information, organization, etc. is included. Further, the personnel / organization data includes, for example, the organization of the company using the computer network 1, the organization configuration, the names of the users included in each organization, and the employee numbers of the users.

[Resource Information Display] FIG. 3 is a diagram illustrating a resource information display function of the resource information collection / management functions performed by the system management program 4. The system management program 4 includes, for each organization using the computer network 1 (for example, a department or section within a company) as a unit, the names and identifiers (employee numbers) of employees (users) belonging to the organization; Is stored in the personnel / organization information DB 482 in association with the identifier of the user. Further, the system management program 4 displays the data stored and managed in the personnel / organization information DB 482 on the display device 104 as a tree-type organization map as illustrated in FIG.

[Group Display Function] FIG. 4 is a diagram illustrating a group management function among the resource information collection / management functions performed by the system management program 4. The system management program 4 includes a personnel information DB 482 and a device resource information DB 4
When the user clicks any of the organizations displayed in FIG. 3 with a mouse or the like, the employee (user) belonging to the specified organization is assigned to these employees as shown in FIG. And displays the resource data of the managed device 20 used by each of the employees (users).

[List Display Function] FIG. 5 is a diagram illustrating a list display function of the resource information collection / management functions performed by the system management program 4. When the user designates any one of the managed devices 20 displayed by the group display function illustrated in FIG. 4 using a mouse or the like, the system management program 4 executes the designated managed device 20. , Resource data is collected, and the resulting resource data is displayed as an icon in a list format as illustrated in FIG.

[Remote Control Function] In the system management program 4, when one of the device resources of the managed device 20 displayed as illustrated in FIG. 5 is designated by a user using a mouse or the like, A request is made to the designated managed device 20 via the communication network 30 to execute the designated device resource (software), and the processing result of the software executed in response to the request is displayed on the display device 1.
04 is displayed.

[Resource Information Analysis] The system management program 4 is input to the input device 102 or the recording medium 1 in advance.
08, the device resources indicated by the standard resource data indicating the standard resources that each managed device 20 should have as standard, and the device resources indicated by the resource data collected from each managed device 20 by the system management program 4. Then, the difference between the device resource of each managed device 20 and the standard resource, that is, the excess or deficiency of the standard device resource of each managed device 20 is detected, stored as difference data, and managed (difference analysis processing). ).

The system management program 4 also stores data (for example, data indicating specific device resources set for the entire computer network 1 or for each of the managed devices 20 by inputting to the input device 102 or the like). It is determined whether or not the specific resource data) is included in the device resources indicated by the resource data of each managed device 20.
This determination result is stored and managed (matching analysis processing).

The specific resources include, for example, the managed device 2
For example, device resources that are prohibited from being installed for each of the devices (for example, software of game software not related to business) and, on the contrary, device resources that are required to be installed or ordered (for example, a communication board). Hardware necessary for business such as, and business software such as word processor and spreadsheet software)
And are included.

[Database Management] When any one of the system management data and the personnel / organization data is changed, the system management program 4 changes the data to the other so that no inconsistency occurs between the information. To reflect
Synchronize both contents.

[System Display] The system management program 4 includes personnel / organization data and system management data,
The resource data and the specific resource data are associated with each other, for example, for each individual or organization, the information is displayed on the display device 104, stored in the recording medium 108 in the storage device 106, or via the communication network 30. The data is transmitted to another communication node (the managed device 20 or a communication device not shown).

[Input unit 44] System management program 4
, The input unit 44 accepts a command input operation performed on the input device 102 by the system administrator, or accepts and accepts a command input operation performed on another communication node via the communication network 30. The command is output to the communication unit 40 and the data analysis unit 42.

[Communication Unit 40] The communication unit 40 realizes the resource information collection / management function of the system management program 4 in cooperation with the database unit 48.

[Transmission Unit 400] In the communication unit 40, when the transmission unit 400 receives the resource change notification of the managed device 20 from the input unit 44, and when the device resource information DB 4
When the necessary processing is completed by 84, a resource data generation request, a resource data transmission request, and a resource data processing end request are transmitted to the managed devices 20 via the communication network 30 as the processing proceeds.

[Receiving Unit 402] The receiving unit 402 receives the completion response and the resource data transmitted from each of the managed devices 20 in response to a request from the transmitting unit 400 or at an arbitrary timing, and performs data analysis. Output to the section 42 and the device resource information DB 484.

[Database unit 48] Database unit 4
Reference numeral 8 realizes the database function of the system management program 4 described above, and realizes the resource information collection / management function in cooperation with the communication unit 40.

[System Management DB 480] The system management DB 480 stores system management data input from the input device 102 or the like, and outputs it to the data analysis unit 42 and the display unit 46 in response to a read request. Also,
The system management DB 480 notifies the personnel / organization DB 482 of the change, for example, when the system administrator changes the content of the system management data. In addition, the system management DB 480 stores the personnel and organization data from the personnel and organization DB 482.
Upon receiving the notification of the change of the organization data, the contents of the system management data are updated so as not to cause inconsistency with the received change, and the synchronization with the personnel / organization data is maintained.

[Personnel / Organization DB 482] Personnel / Organization DB
Reference numeral 482 stores personnel / organization data input from the input device 102 or the like, and outputs the data to the data analysis unit 42 and the display unit 46 in response to a read request. In addition, HR
The organization DB 482 notifies the system management DB 480 of the change when the system administrator changes the contents of the personnel / organization management information. Personnel / Organization D
B482 receives the notification of the change of the system management data from the system management DB 480, updates the contents of the personnel / organization management information so as not to cause inconsistency with the received change, and keeps the synchronization with the personnel / organization data.

[Device Resource Information DB 484] The device resource information DB 484 includes resource data and keywords input from the receiving unit 402, system management data and personnel / organization data read from the system management DB 480 and the system management DB 482, and data analysis. The difference data generated by the unit 42 or the determination result of the specific resource is stored and managed in association with each other.

[Data analysis unit 42] Data analysis unit 42
Implements the resource information analysis function of the system management program 4 described above. That is, when a difference analysis processing command is input from the input unit 44, the data analysis unit 42
The standard resource data of each managed device 20 is read from the system management DB 480, and the device resource indicated by the resource data of each managed device 20 input from the receiving unit 402 is compared with the device resource indicated by the standard resource data, and the difference is calculated. The data is generated, and the display unit 46 and the device resource information DB 48
4 (difference analysis processing). When a matching analysis processing command is input from the input unit 44, the data analysis unit 42 reads the specific resource data from the system management DB 480, and specifies the specific resource data to the device resource indicated by the resource data of each managed device 20. It is determined whether or not the device resource indicated by the resource data is included, and this determination result is output to the display unit 46 and the device resource information DB 484 (matching analysis process).

[Display Unit 46] The display unit 46 implements the system display function of the system management program 4 described above. That is, the display unit 46 reads the personnel / organization data and the system management data from the system management DB 480 and the personnel / organization DB 482, and reads the read information, the resource data and the specific resource data, or the device resources indicated by any of them. Is output to the display device 104 or the like in association with each individual or each organization.

[Software Configuration of Managed Device 20] FIG. 6 is a diagram showing a software configuration of the managed device 20 shown in FIG. For simplicity of description and illustration, other programs not directly related to the description of the present invention are omitted in FIG. As shown in FIG.
The managed device 20 executes the OS 6 and the managed program 5.

[OS6] The OS6 performs hardware control, software execution control, and the like in the managed device 20 in the same manner as in the management device 10. OS6 is
In the managed device 20, the managed device 2
Every time software and hardware (device resources) are installed and uninstalled for 0, information (installation log) indicating whether the installation and uninstallation processing has been performed is output to the managed program 5.

In the managed device 20, the OS (6) responds to a request from the managed program 5 by an API (A
application program interface), a registry, installed software information determined from an execution file (* .exe) in the file system, hardware information, and the like are output to the managed program 5.

[Managed Program 5] The managed program 5 includes a communication unit 50, a log analysis unit 52, and a device resource collection unit 5.
4 and a database unit 56. Communication unit 5
0 is composed of a transmitting unit 500 and a receiving unit 502;
The database unit 56 includes an installation log DB 560 and a resource DB 562.

As described above, the managed program 5 uses these components in response to an inquiry from the management apparatus 10 or when there is a change in apparatus resources.
An executable file (* .exe) or the like in the file system is searched to find out what kind of device resources the managed device 20 currently has, and to generate resource data. Send to 10.

[Install Log DB 560] In the database unit 56, the install log DB 560
Each time the installation log is input from the OS 6, the input installation log is stored and output to the log analysis unit 52.

[Resource DB 562] The resource DB 562 includes keywords set for each managed device 20,
And an API input from the OS 6 as described above,
It stores a registry, an executable file, hardware information, and the like, and outputs the information to the device resource information collection unit 54 in response to a request.

[Receiving Unit 502] In the communicating unit 50, the receiving unit 502
, A resource data generation request, a resource data transmission request, and a resource data processing end request sent to the device resource information collection unit 54 and the transmission unit 500.

[Transmission Unit 500] When a resource data transmission request is input from the reception unit 502, the transmission unit 500 transmits the resource data input from the device resource information collection unit 54 to the management device 10. In addition, in response to a request from the log analysis unit 52, the transmission unit 500 transmits a resource change notification for notifying that a change has occurred in the device resources of the managed device 20. In response to the request, a completion response indicating that the resource data generation has been completed is
It is transmitted to the management device 10.

[Log Analysis Unit 52] When the installation log is input from the installation log DB 560, the log analysis unit 52 analyzes the input installation log, detects newly installed or uninstalled device resources, and , A request to notify the management device 10 of the change in the device resources to the transmission unit 500. As described above, a newly installed or uninstalled device resource is detected by not issuing an alert when a new installation or uninstallation is not detected, but issuing an alert only when a new installation or uninstallation is detected. It is to prepare.

[Device Resource Information Collecting Unit 54] Upon receiving a resource data transmission request from the receiving unit 502, the device resource information collecting unit 54 reads an API, a registry, an executable file, hardware information, and the like from the resource DB 562. It generates resource data indicating the device resources installed in the managed device 20 at that time, outputs the resource data to the transmission unit 500, and requests the transmission unit 500 to transmit a completion response.

[Operation of Computer Network 1] The operation of the computer network 1 will be described below with reference to FIGS. 7 to 15.

[Keyword Setting] FIG. 7 is a flowchart showing a keyword setting process (S10) for the managed device 20 shown in FIG. 1 and FIG. As shown in FIG. 7, in step 100 (S100), when the user of the managed device 20 (FIG. 1) inputs a keyword to the input device 102, in step 102 (S102), the resource DB 562 (FIG. 6) The input keyword is accepted, and stored and stored in the non-volatile recording medium 108 in the storage device 106.

[Main Flow of Management Apparatus 10] FIG.
FIG. 3 is a flowchart (main flow diagram; S12) illustrating an outline of a process of the management device 10 illustrated in FIGS. 1 and 2. As shown in FIG. 8, in step 120 (S120), for example, the system administrator
When a command input operation is performed on the input device 102, or at a fixed time interval, step 122 (S
At 122), the input unit 44 analyzes the input command and determines whether an information collection command has been input. When the information collection command is input, the input unit 44 outputs the information collection command to the transmission unit 400 and the reception unit 402, and the management device 10
The process proceeds to S20 and S22 for collecting resource data from 0 (described later with reference to FIG. 9), and otherwise proceeds to S124.

In step 124 (S124), the input section 44 determines whether or not the input command is a differential method analysis command. If the command is a difference method analysis command, the input unit 44 outputs the difference method analysis command to the data analysis unit 42 and uses the standard resource data to detect an excess or deficiency of the device resources of the managed device 20. The process proceeds to the type analysis process (S30 and S32; described later with reference to FIG. 12). Otherwise, the input unit 44
Determines that the input command is a match analysis command, and matches the match analysis command to the data analysis unit 4.
2, the management apparatus 10 uses the specific resource data to determine whether or not a specific device resource is installed in the managed device 20 (S matching analysis process).
40 and S42; described later with reference to FIG. 14).

The standard resource data includes, for example,
(1) Shortcut types (Programs, De
skTop, Common Programs, Com
mon DeskTop), (2) Link file name (Programs, Common Programs)
(3) Start-up file name (file name to be started when clicked, if necessary, register this in the dictionary file to generate a special dictionary file) And (4) display name (name displayed on menu or icon, used as software name).

[Information Collection Process] FIG.
The management device 10 (FIGS. 1 and 2)
6 is a flowchart showing processing (resource data collection processing; S20, S22) when collecting resource data from 6).
FIG. 10 is a flowchart showing the resource data generation process (S60 shown in FIG. 9) by the resource information collection unit 54.
FIG. 11 shows that the display unit 46 of the management device 10 shown in FIG.
FIG. 3 is a diagram illustrating a GUI image displayed on a display device 104.

First, processing on the management apparatus 10 side will be described.
As shown in FIG. 9, step 200 (S2
00), the system administrator selects and presses the button (all displays; * 4) of the process selection image 70 (FIG. 11) using the input device 102, and the management device 10 (FIGS. 1 and 2). ), Input the command for resource information collection, and specify the organization to be subject to difference analysis.
The input unit 44 outputs a resource information collection command to the transmission unit 400.

The transmission section 400 transmits a resource data generation request for requesting the managed device 20 to generate resource data. The resource data generation request transmitted in the process of S200 is received by the managed device 20 in the process of S220.

In step 202 (S202), the receiving unit 402 waits for reception of a completion response transmitted from the managed device 20 in the process of S226 and indicating that the managed device 20 has completed the generation of the resource data. If a response has been received, a completion response is output to the transmission unit 400, and the process proceeds to S204.

In step 204 (S204), transmitting section 400 transmits a resource data transmission request for requesting transmission of the generated resource data to managed device 20.
The resource data transmission request transmitted in the process of S204 is received in the process of S220 on the S20 side.

In step 206 (S206), the receiving unit 402 waits for reception of the resource data and the keyword transmitted by the managed device 20 in the process of S230.
If the resource data has been received, the resource data is output to the device resource information DB 484, and the process proceeds to S208.

In step 208 (S208), the device resource information DB 484 determines whether or not the received resource data has already been stored.
The process proceeds to the process of S210, and otherwise proceeds to the process of S210.

In step 210 (S210), the device resource information DB 484 determines that the managed device 20 that has transmitted the resource data is unregistered, and
0 is added and stored together with the keyword.

In step 212 (S212), the device resource information DB 484 reads the system management data and the personnel / organization data from the system management DB 480 and the personnel / organization DB 482, and stores the read information in association with the resource data. ·to manage. By the processing of S212. The device resource information DB 484 stores (1) types of shortcuts (Programs, DeskTop,
Common Programs, Common De
skTop), (2) Link file name (Program
ms, Common Programs, used as hierarchical information of menu), (3) Startup file name (file name to be started when clicked, if necessary, register this in a dictionary file, and register it in a special dictionary file Can be generated), (4) display name (the name displayed on a menu or an icon, used as a software name), (5) managed device name, (6) key information of the managed device, (7) Obtain and store information such as the address of the managed system and (8) the information acquisition time.

In step 214 (S 214), the device resource information DB 484 notifies the transmitting unit 400 that the processing of S 212 has been completed, and the transmitting unit 400 transmits to the managed device 20 the generation of the resource data. And a resource data processing termination request for requesting termination of the resource data processing to be transmitted. This resource data processing end request is received by the managed device 20 in the process of S220.

In step 216 (S 216), the device resource information DB 484 determines that resource data collection has not been completed for all managed devices 20 in the computer network 1, and the resource data processing is performed on the other managed devices 20. It is determined whether or not it is necessary to request resource management. If it is necessary to request another managed device 20 to process the resource data, a notification to that effect is sent to the transmission unit 400 and S200 is sent.
Otherwise, the display unit 46 reads the resource data of the managed device 20 from the device resource information DB 484 and displays it on the display device 104, and the management device 10 ends the collection of the resource data.

Next, processing on the managed device 20 side will be described. In step 220 (S220) of the process S22,
The receiving unit 502 (FIG. 6) waits for reception of a request from the system management program 4 of the management device 10. If a request has been received, the process proceeds to step S <b>222; otherwise, the process remains at step S <b> 220. .

In step 222 (S222), the receiving unit 502 determines whether the received request is a resource data generation request, and if the received request is a resource data generation request,
A resource data generation request is output to the device resource information collection unit 54, and the process proceeds to S60.
Proceed to step 28.

In step 60 (S60), the device resource information collection unit 54 obtains an API, a registry, executable files in the file system, hardware information, and the like from the OS 6, and obtains the device resources installed in the managed device 20. Resource data indicating the current state of the
Output for 0.

Hereinafter, referring to FIG. 10, the process of generating resource data using the shortcut information will be described as OS 6 by W
The case where Windows 95 / NT (trade name of Microsoft Corporation) is used will be described in more detail as a specific example.

In step 600 (S600), the device resource collection unit 54 sets a special folder (Programs, DeskTop, Com) in which the link file exists.
mon Programs, Common DeskT
op) is obtained from the OS 6 as registry information or an API.

In step 602 (S602), the device resource collection unit 54 determines whether or not the folder acquired in the process of S600 has a DeskTop relationship. If the folder has a DeskTop relationship, the process proceeds to S606. In other cases, the process proceeds to S604.

In step 604 (S 604), the device resource collection unit 54 sets the Program, Common
Information of a hierarchical folder such as Programs is acquired.

In step 606 (S606), the device resource collection unit 54 acquires the link file of the folder acquired in the processing of S600.

In step 608 (S608), the device resource collection unit 54 acquires and stores the display name of the shortcut of the link file acquired in the processing of S606 and the information of the hierarchized folder using the API or the like. .

In step 610 (S 610), the device resource collection unit 54 executes S
It is determined whether or not the processing of step 608 has been completed. If the processing has not been completed, the processing returns to step S608; otherwise, the processing proceeds to step S226 (FIG. 9).

By the processing of S60 described above, the device resource collection unit 54 sets (1) the type of shortcut (Pro
Grams, DeskTop, Common Prog
rams, Common DeskTop), (2) Link file name (Programs, Common P)
(Used as hierarchical information of programs in programs), (3) Start file name (File name to be started when clicked, if necessary, register this in the dictionary file, and generate special dictionary file (4) Display name (name displayed on menu or icon, used as software name) is acquired and stored.

Referring again to FIG. Step 226 (S
In 226), the transmission unit 500 transmits a completion response to the management device 10. This completion response is sent to the management device 1
On the 0 side, it is received in the processing of S202.

In step 228 (S228), receiving section 502 determines whether or not the received request is a resource data transmission request.
A resource data transmission request is output to the transmission unit 500 and the
Proceeding to the process at 230, otherwise, determine that the received request is a resource data processing end request and output the resource data processing end request to other components such as the transmission unit 500, The process proceeds to S232.

In step 230 (S230), the transmitting section 500 transmits the resource data input from the apparatus resource information collecting section 54 and the keyword read from the resource DB 562 to the management apparatus 10. This resource data is received by the management device 10 in the process of S206.

In step 232 (S232), each component of the managed device 20 performs processing such as clearing the storage area as necessary, and terminates the resource data processing and proceeds to S232.
It returns to the process of 220.

In step 22 (S22; FIG. 8), the management device 10 checks the device resources indicated by the resource data of each of the managed devices 20 obtained by the above-described resource data collection processing, the personnel / organization data, and the system management data. The data is associated with the data and displayed on the display device 104.

[Difference Analysis Processing] FIG. 12 is a flowchart showing the difference analysis processing (S30, S32) shown in FIG. As shown in FIG. 12, step 300 (S30
In (0), the system administrator uses the input device 102 to select and press the button (edit appropriate list; * 1) of the process selection image 70 (FIG. 11), and
When a command input operation of the difference analysis processing is performed on (FIGS. 1 and 2), and the organization to be subjected to the difference analysis is designated, the data analysis unit 42 of the management device 10 20 and reads out the standard resource data, and also reads out the personnel / organization data on the organization and the user to be subjected to the difference analysis from the personnel / organization DB 482.

In step 20 '(S20'), the management device 10 includes the resource information collection processing shown in FIG. 9 in the organization currently being processed, and the collection of the resource data is still completed. The process is performed for any one of the managed devices 20 that have not been performed, and the resource data of each of the managed devices 20 is obtained.

In step 70 (S 70), the data analyzer 42 compares the device resource indicated by any one of the standard resource data of the managed device 20 with the current device resource of the managed device 20. To generate difference data indicating the difference.

Hereinafter, the processing of S70 will be described in further detail with reference to FIG. FIG. 13 is a flowchart showing the difference data generation processing (S70) shown in FIG.

As shown in FIG. 13, step 700 (S
At 700), the data analysis unit 42 reads the standard resource data.

In step 702 (S702), the data analysis unit 42 acquires one record of the device resource data read in the process of S300 (FIG. 12).

In step 704 (S704), the data analysis unit 42 determines whether the comparison of all records of the device resource data has been completed, and terminates the processing if the comparison of all records has been completed. S322 (FIG. 12)
The process returns to step S706. Otherwise, the process proceeds to step S706.

In step 706 (S706), the data analysis unit 42 compares one record of the device resource data acquired in the process of S702 with the standard resource data read in the process of S700, Is detected.

In step 708 (S 708), the data analysis unit 42 determines whether or not a mismatched device resource has been detected. If detected, the process returns to step S 702. The process proceeds to S710.

In step 710 (S710), the data analysis unit 42 stores the device resource in which the mismatch was detected in S706 in association with the managed device.

Referring again to FIG. Step 322
In (S322), the data analysis unit 42 determines whether the process of generating difference data has been completed for all users (managed devices 20) included in one of the organizations to be processed. If the processing has been completed, the process proceeds to S324. Otherwise, the process proceeds to S20 '.

In step 324 (S324), the data analysis unit 42 determines whether or not collection of all the resource data of the user (managed device 20) included in the organization specified as the processing target has been completed. If the processing has been completed, the collected resource data is output to the display unit 46, and S32
Otherwise, the process proceeds to S20 '.

In step 32 (S32), the display unit 4
6 is a system management DB 480 and a personnel / organization DB 4
The system management data and the personnel / organization data read from the storage device 82 and the resource data of each managed device 20 obtained by the processing described above are associated with these data by using keywords, and the result of the difference analysis is obtained. , FIG.
As shown in FIG. 1, it is displayed on the display device 104 as the appropriate check list 72 (* 1).

[Match Analysis Process] FIG. 14 is a flowchart showing the match analysis process (S40, S42) shown in FIG. As shown in FIG.
In (S400), the system administrator operates the input device 10
2, a button (display of suspicious objects; * 2) of the process selection image 70 (FIG. 11) is selected and pressed, and a command of the matching analysis process is input to the management device 10 (FIGS. 1 and 2). When the operation is performed and the organization to be subjected to the difference analysis is designated, the display unit 46 of the management apparatus 10 (FIGS. 1 and 2)
Shows the result of the difference analysis processing shown in FIG.
4, and reads out personnel / organization data relating to the organization and the user to be subjected to the matching analysis from the personnel / organization DB 482. The system administrator inputs any device resources from the displayed difference analysis result to the input device 102.
When the user designates a specific resource by using the
Transmits this designation to the data analysis unit 42 and the device resource information D.
Output to B484.

In step 402 (S402), the device resource information DB 484 stores and manages the specific resource input from the input unit 44 as specific resource data.

In step 20 ′ (S 20 ′), the management apparatus 10 includes the resource information collection processing shown in FIG. 9 in the organization currently being processed, and the collection of the resource data is still completed. The process is performed for any one of the managed devices 20 that have not been performed, and the resource data of each of the managed devices 20 is obtained.

In step 420 (S420), the data analysis unit 42 compares the device resource indicated by the resource data obtained by the processing of S20 'with the specific resource indicated by the specific resource data, and the specific resource is installed. The keyword indicating the managed device 20 and the specific resource are output to the device resource information DB 484. Device resource information DB 484
Associates the keyword of the managed device 20 input from the data analysis unit 42 with the specific resource, and stores and manages the keyword as specific resource data.

In step 422 (S422), the data analysis unit 42 determines whether the process of generating difference data has been completed for all users (managed devices 20) included in one of the organizations to be processed. It is determined whether or not the process is completed. If the process is completed, the process proceeds to S424, otherwise, the process proceeds to S20 '.

In step 424 (S424), the data analysis unit 42 determines whether or not collection of all the resource data of the user (managed device 20) included in the organization specified as the processing target has been completed. , If finished, S4
The process proceeds to the process of step S2 ', and otherwise proceeds to the process of S20'.

In step 42 (S42), the display unit 4
6 is a system management DB 480 and a personnel / organization DB 4
The system management data and the personnel / organization data are read out from the device resource information DB 484, the specific device data is read from the device resource information DB 484, the data is associated using a keyword, and the result of the matching analysis is displayed, as shown in FIG. 74 is displayed on the display device 104 (* 1).

[Device Resource Collection Process Initiated by Managed Device 20] FIG. 15 is a diagram showing a resource data collection process when the managed device 20 (FIGS. 1 and 6) detects a change in device resources.

As shown in FIG. 15, step 520 (S
520), in the managed device 20 (FIG. 1, 6), the device resource information collecting unit 54
It is determined whether or not the resource data collection process has been started according to 2), and if it has been started, the process proceeds to S2 shown in FIG.
The process proceeds to S20, and otherwise proceeds to S522.

In step 522 (S522), the device resource information collection unit 54 collects resource data from the OS 6, stores it in the storage device 106 or the like, and activates the log analysis unit 52.

In step 524 (S524), the log analysis unit 52 reads the installation log from the installation log DB 560, and stores the read installation log this time in the storage device 106 or the like as an installation log used for the next processing.

In step 526 (S 526), log analysis section 52 determines whether or not the installation log has been changed, and if there has been a change, transmits a resource change notification indicating that to transmission section 500. Request.

At step 528 (S528), transmitting section 500 transmits a resource change notification to management apparatus 10, and proceeds to the processing of S20 ''. The resource change notification transmitted by the managed device 20 is transmitted to the managed device 20 at S500.
Is received in the process.

In step 500 (S500), the receiving unit 402 of the management apparatus 10 waits for the resource change notification from the managed apparatus 20, and upon receiving the resource change notification, returns to step S500.
Proceed to step 20 ''.

In step 20 '' (S20 ''), the management device 10 proceeds to the process of S200 shown in FIG. 9, and the managed device 20 proceeds to the process of S220 shown in FIG. The same processing as S20 and S22 (FIG. 9) is performed between the managed device 20 that has transmitted the device change notification and the management device 10, and the management device 10 transmits the device change notification to the managed device 20 that has transmitted the device change notification. Get resource data.

[Modification] Standard resource data may be sequentially replaced and updated with newly obtained resource data. Each time the managed device 20 detects a change in device resources, it sends resource data to the management device 12, and the management device 12 that has received the resource data updates the contents of each database. May be changed. Further, the processing contents and configuration of the computer network 1 described above are only examples, and can be appropriately changed according to the equipment used, the application, and the like as long as the same processing can be performed.

[Second Embodiment] Hereinafter, a second embodiment of the present invention will be described.

[Computer Network 7] FIG.
FIG. 2 is a diagram illustrating a configuration of a computer network 7 to which a second device resource management method according to the present invention is applied. As illustrated in FIG. 16, in the first embodiment, the computer network 7 includes the management device 12, the managed devices 22-i (i = 1,...) In the same manner as the computer network 1 illustrated in FIG. , N; hereinafter, when any of the managed devices 22-1 to 22-n is indicated without being specified, the managed device 22 is simply referred to as the managed device 22).
0, and the managed device 22 is further connected to a peripheral device 24-j (j = 1,.
In the case where any one of 4-1 to 24-p is indicated without being specified, the device is simply connected to a peripheral device 24). Hereinafter, among the components of the computer network 7, those components that are different from those of the computer network 1 will be described.

[Management Apparatus 12] The management apparatus 12 has the same device configuration as the management apparatus 10 (FIG. 1), executes the system management program 4 (FIG. 2), and transmits necessary data to and from the managed apparatus 22. Send and receive However, in the second embodiment, the processing contents of the system management program 4 are appropriately changed in order to realize a resource management function different from that in the computer network 1 (FIG. 1). 19 etc.).

[Managed Device 22] Each managed device 22 executes a managed system program 8 (described later with reference to FIG. 37 and the like) different from the managed program 4 of the managed device 20, and 12, necessary data is transmitted and received.

[Peripheral Device 24] The peripheral device 24 is a display device, a printer device, a scanner device, an external storage device, or the like, and realizes the functions of these devices.
The peripheral device 24 is detachable from the managed device 22. When all the peripheral devices 24 are removed, the managed device 22
May be in a state where the peripheral device 24 is not connected at all. The peripheral device 24 includes components (not shown) necessary for executing a program, such as the CPU 100 and the communication device 112, like the managed device 22, and a peripheral device program 26 (described later with reference to FIG. 31). Execute

FIG. 17 is a block diagram of the peripheral device 24 shown in FIG.
FIG. 2 is a diagram exemplifying resource data in a standard format (a format that does not depend on the input / output format of the system management program 4) set to be readable by software in 1 to 24-p. FIG. 18 shows that the resource data shown in FIG.
Resource data common to 1 to 24-p (common resource data)
And resource data (unique resource data) unique to each of the peripheral devices 24-1 to 24-p, and converted into a format suitable for the input / output format of the system management program 4 executed by the management device 12. It is a figure which illustrates resource data.

In addition, the peripheral device 24 includes the nonvolatile memory 2
60 (to be described later with reference to FIG. 31) or a hard disk device or the like, which incorporates a storage device capable of holding data even when the power is turned off. Common resource data (common resource data) depending on the type of the peripheral device 24 such as the model number and the installed OS, and the peripheral device 2 such as display resolution and print resolution.
4, resource data (unique resource data) unique to each is set so as to be readable by software (peripheral device program 26) executed in the peripheral device 24. The conversion from the resource data in the standard format shown in FIG. 17 to the resource data depending on the input / output of the system management program 4 shown in FIG. Is executed by

In addition, the peripheral device 24 stores data such as a management number, a user name, and a user contact set by software in the nonvolatile memory 260 or the like.

[Communication Device 112] The communication device 112 (not shown in the peripheral device 24) operates under the control of software executed by the CPU 100 in the managed device 22 and the peripheral device 24, and communicates with the managed device 22 and the peripheral device. Data is transmitted to and received from the device 24 via a communication line such as a serial cable, a parallel cable, or an infrared communication line.

In the computer network 7,
In addition to the management device 12 realizing the same functions such as resource data management as in the computer network 1, the management device 12 also includes a peripheral device 2 connected to the managed device 22.
4 Further management of each resource data is performed. Less than,
The functions related to resource management in the computer network 7 will be described.

[Detection of Peripheral Device] When a new unknown peripheral device 24 is connected to the managed device 22, the management device 12 detects the connection of the new peripheral device 24 and notifies the system administrator. .

[Management Information Setting / Restoration] The management device 12
Management information (management number, user name, etc.) for managing the peripheral device 24 is generated, and the management information generated via the managed device 22 is set in the peripheral device 24. Further, when the peripheral device 24 is reset to the state at the time of shipment from the factory for some reason, the management device 12 restores the management information before the reset based on the information stored in the managed device 22. With this function, the management apparatus 12 can display the management information of the peripheral device 24 that has been detached from the managed device 22 and has been abandoned, and can notify the user of the management.

[Modifications of Program] Hereinafter, changes made to software executed by the management device 12, the managed device 22, and the peripheral device 24 to realize these functions will be described.

[System Management Program 4] First, changes in the processing of the system management program 4 (FIG. 2) executed in the management device 12 (FIG. 16) will be described. Also in the second embodiment, the system management program 4 has the same configuration as in the first embodiment, but the following processing is added to the database unit 48 and the data analysis unit 42.

FIG. 19 shows the management device 12 and the managed device 22.
FIG. 4 is a list of signals transmitted and received between the peripheral device and the peripheral device; First, signals input and output by the management device 12 will be described. As shown in FIG. 19, the system management program 4 (FIG. 2) of the management device 12 transmits a resource data generation response and a resource data transmission from the managed system program 8 (described later with reference to FIG. 37) of the managed device 22. A response, a resource data change notification, and a management information generation request are received. Further, the system management program 4 of the management device 12 transmits a resource data generation request, a resource data transmission request, a resource data processing end request, and a management information generation response to the managed system program 8 of the managed device 22.

Among these signals, the resource data generation response is a signal for the managed device 22 to respond to the resource data generation request to the management device 12 to respond to the completion of the resource data generation. There is no additional information (this signal is simply described as “completion response” in the first embodiment). The resource data transmission response is a signal for the managed device 22 to transmit the generated resource data to the management device 12, and includes the resource data as additional information. In one embodiment, it is simply referred to as “resource data”). The resource data change notification is a signal for the managed device 22 to notify the management device 12 of the change of the resource data in the management device, and does not include additional information. In one embodiment, it is simply described as "resource change notification"). Also, the management information generation request is:
A signal for the managed device 22 to request the management device 12 to allocate management information to a resource having no management information, and information for specifying the resource (manufacturer, program name, or peripheral device model number) (This signal is a signal added in the second embodiment).

The resource data generation request is a signal for the management apparatus 12 to request the managed apparatus 22 to generate resource data, and does not include additional information. Also,
The resource data transmission request is a signal for the management apparatus 12 to request the managed apparatus 22 to transmit the generated resource data, and does not include additional information. The resource data processing end request is sent to the managed device 22 by the management device 1.
Reference numeral 2 denotes a signal for requesting termination of processing related to generation of resource data, and does not include additional information. The management information generation response is sent to the managed device 22 by the management device 1.
Reference numeral 2 denotes a signal for responding to the management information generation request, which includes the management information as additional information (this signal is a signal added in the second embodiment).

[System Management DB 480] FIG. 20 is a diagram exemplifying connectable device data indicating the peripheral devices 24 permitted to be connected to the managed device 22. In the second embodiment, the system management DB 480 of the database unit 48
Is, as standard resource data, as illustrated in FIG.
Connectable device data indicating the peripheral device 24 permitted to be connected to the managed device 22 is further stored and managed.

[Device Resource Information DB 484] FIG. 21 is a view showing an example of non-connectable device data in which keywords and device IDs of the managed device 22 to which the peripheral device 24 to which connection is not permitted are connected. is there. Device resource information D
B484 stores and manages resource data and keywords further including common epicenter data and specific resource data of the peripheral device 24, system management data and personnel / organization data, and difference data or determination results of specific resources in association with each other. . In addition, the device resource information DB 484 indicates that the peripheral devices 24 that are not permitted to connect to the managed device 22 other than the peripheral device 24 indicated by the connectable device data.
Is connected, the resource data (FIG. 17) of the peripheral device 24 to which the connection is not permitted, and the keyword and the device ID of the managed device 22 to which the peripheral device 24 to which the connection is not permitted are connected. Correspondingly, it is stored and managed as unconnectable device data as illustrated in FIG.

[Personnel / Organization DB 482] Personnel / Organization DB
The processing of 482 is the same as that of the first embodiment in the second embodiment.

[Data Analysis Unit 42] FIG. 22 is a diagram illustrating a data format of a management information generation request. FIG. 23 is a diagram illustrating a data format of the management information generation response. The data analysis unit 42 includes the managed device 22
The resource data generation request of the peripheral device 24 input from the receiving unit 402 or the like from FIG. 16 is processed. That is, the data analysis unit 42 determines the resource data of the peripheral device 24 (such as the manufacturer of the peripheral device 24) attached to the management information generation request shown in FIG. 22 and the connectable device data read from the system management DB 480 (FIG. ) And device resource information DB4
The peripheral device 24 determines whether or not the connection to the managed device 22 is permitted by comparing the unreachable data read from 84 with the non-connectable data.

When the connection of the peripheral device 24 is permitted, the data analysis unit 42 generates the management number of the peripheral device 24 according to a predetermined management number generation method, and further generates the management information. The personnel / organization DB 482 is searched using the keyword attached to the request, and management information is generated by associating the generated management number with the user name and user contact information obtained as a result of the search. The data analysis unit 42 adds the generated management information to the management information generation response, and transmits the management information generation response to the managed device 22 that has issued the management information generation request via the transmission unit 400.

For example, the system management DB 480 stores the maximum value of the management number currently used (for example, 123
4), the modifier character string of the management number (for example, "ABCD asset-") is stored, and the data analyzer 42 reads out the maximum value and the modifier character string, adds 1 to the maximum value, and connects the modifier value with the modifier character. New management number (ABCD asset-123
4).

On the other hand, when the connection to the peripheral device 24 is not permitted, the data analysis unit 42
4 is associated with the keyword and the device ID of the managed device 22, and the device resource information DB 48 is used as the unauthorized device data (FIG. 21).
4 for storage and management.

The processing of the system management program 4 is shown in FIG.
Further description will be made with reference to FIG. FIG. 24 shows a system management program 4 executed by the management device 12 shown in FIG.
It is a flowchart which shows a process (S54). In addition,
The process of receiving the resource data generation response and the resource data transmission response and the process of transmitting the air t generation request, the resource data transmission request, the resource data transmission request, and the resource data processing end request by the resource FIG. 2 is the same as the process in the first embodiment in which
The processing shown in FIG. 4 is replaced with the processing on the left side of FIG. As shown in FIG. 24, step 540 (S540)
, The receiving unit 402 of the system management program 4
(FIG. 2) receives a resource data change notification or a management information generation request from the managed device 22.

In step 542 (S542), when receiving the resource data change notification, the receiving section 402 proceeds to the processing of S20 shown in FIG. 9, and otherwise, proceeds to the processing of S544.

In step 544 (S544), the data analysis unit 42 performs system management based on the manufacturer and model number of the peripheral device 24 in the resource data of the peripheral device 24 included in the management information generation request received by the reception unit 402. D
Connectable device data and device resource information D in B480
By referring to the unconnectable device data in B484, it is determined whether the peripheral device 24 has been registered as a device permitted to be connected to the managed device 22. If the peripheral device 24 is registered in the system management DB 24, the data analysis unit 42 proceeds to the process of S546.
Proceed to step 50.

At step 546 (S546), the data analysis unit 42 refers to the standard resource data in the system management DB 480 based on the manufacturer and model number of the peripheral device 24 in the resource data of the peripheral device 24, and Generate a fixed asset number, etc. Further, the data analysis unit 42
Grinds the personnel / organization information DB 482 using the keyword attached to the management information generation request, and associates the user name and contact information of the managed device 22 with the generated management number and fixed asset number, The management information of the peripheral device 24 is generated.

FIG. 24 is a diagram exemplifying management information.
As shown in FIG. 24, the management information includes information such as a fixed asset number and a management number that can uniquely identify the peripheral device 24. The system management program 4 of the management device 12 Assign to
The format of the management information may be different for each organization as long as the peripheral device 24 can be uniquely specified. Further, other than the telephone number shown in FIG. 23, another number such as a mail address may be used as the contact information of the management information.

FIG. 25 is a diagram exemplifying a management information generation response. In step 548 (S548), the data analysis unit 42 adds the generated management information (FIG. 25) to the management information generation response signal, and transmits, via the transmission unit 400, the management target device 22 that has transmitted the management information generation request. Send to.

In step 550 (S550), the data analysis unit 42 stores the manufacturer and model number of the resource data of the peripheral device 24 added to the management information generation request, the keyword, the device ID, and the like in the device resource information DB 484. Is recorded as non-connectable device data.

[Managed System Program 8] Next, the managed system program 8 will be described. First, signals transmitted and received by the managed system program 8 will be described. FIG.
As shown in FIG. 9, the managed system program 8 of the managed device 22 includes, in addition to the signals transmitted to and received from the management device 12,
A resource data transmission response and a resource setting response are received from a peripheral device program 26 (described later with reference to FIG. 31) of the peripheral device 24, and a resource data transmission request and a management information setting request are transmitted to the peripheral device program 26. .

Of these signals, the resource data transmission response is a signal for the peripheral device program 26 of the peripheral device 24 to transmit resource data to the managed system program 8 in response to a resource data transmission request. Resource information as additional information. The resource data transmission request is a signal for the managed system program 8 to request the peripheral device program 26 of the peripheral device 24 to transmit resource data, and does not include additional information. Also,
The management information setting response is a signal for the peripheral device program 26 of the peripheral device 24 to respond to the managed system program 8 of the completion of the management information setting in response to the management information setting request. Not included. The management information setting request is transmitted to the peripheral device program 26 of the peripheral device 24.
Is a signal for requesting the managed system program 8 to set management information, and includes the management information as additional information.

FIG. 26 shows the managed device 22 shown in FIG.
FIG. 2 is a diagram showing a configuration of a managed system program 8 executed in. As shown in FIG. 26, the managed system program 8 includes a managed program 5 (FIG. 6) shown in the first embodiment and a peripheral device management program provided corresponding to each of the connected peripheral devices 24. 80
-1 to 80-m (hereinafter, simply referred to as a peripheral device management program 80 in the case where any one is not specified) is connected via a common data area 564.

[Peripheral Device Management Program 80] Each of the peripheral device management programs 80 includes a transmission unit 802, a reception unit 804, a peripheral device connection monitoring unit 806, and a common data area management unit 820. The peripheral device management program 80 manages the corresponding peripheral device 24 according to its type. Hereinafter, the peripheral device management program 80
A case where data is exchanged with the managed program 5 via the common data area 564 will be described as an example. However, Windows (a product name of Microsoft Corporation) that uses the peripheral device management program 80 as, for example, the OS 6
It is also possible to configure so as to exchange data with the managed program 5 by a method such as calling the dynamic link library as needed.

[Common Data Area Management Unit 820] The common data area management unit 820 receives the update of the resource data (FIG. 17) of the peripheral device 24 from the device resource information collection unit 54 via the common data area 564. Next, it inquires of the peripheral device connection unit 806 to determine whether the peripheral device 24 is connected. Also, the common data area management unit 820
When the peripheral device 24 is not connected, the device resource information collection unit 54 is notified of the completion of the update via the common data area 564, and when the peripheral device 24 is connected, The transmission unit 802 transmits a request for transmitting resource data to the peripheral device 24.

FIG. 27 is a diagram illustrating a format of a resource data transmission response received from the peripheral device 24.
Also, the common data area management unit 820 receives the resource data transmission response of the peripheral device 24 as illustrated in FIG. 27 from the reception unit 804, and manages the management number and the user name included in the received resource data transmission response. If the information is blank and the management information corresponding to the peripheral device 24 generated by the system management program 4 of the management information 12 is stored in the common data area 564, the management information is stored in the common data area 564. Based on the management information of the peripheral device 24, the transmission unit 802 requests the transmission unit 802 to transmit a management information setting request to the peripheral device 24.

When the common data area management unit 820 receives the resource data of the peripheral device 24 from the reception unit 804, it depends on the input / output format of the system management program 4 (FIG. 2). In the common data area 564 in a format that does not correspond to the input format of the system management program. I do.

[Transmission Unit 802] The transmission unit 802 responds to a request from the device resource information collection unit 54 and the peripheral device connection management unit 806s via the common data area 564 and a request from the peripheral device connection monitoring unit 806. And peripheral device 2
4 transmits a management information setting request. In addition, the transmission unit 802 transmits a resource data transmission request to the peripheral device 24 in response to a request from the common data area management unit 820.

[Receiving Unit 804] The receiving unit 804 receives a resource data generation response to which resource data has been added from the peripheral device 24, and stores the received resource data in the common data area 564 via the common data area management unit 820. Output to

[Peripheral Device Connection Monitoring Unit 806] The peripheral device connection monitoring unit 806 detects that the corresponding peripheral device 24 is connected to the managed device 22 at the moment of connection, and this peripheral device 24 is connected. The transmission unit 802 sends a resource data transmission request to the peripheral device 24 with the instant of the trigger as a trigger.
To be sent.

[Common Data Area 564] As described above, the common data area 564 stores the managed device 22 (FIG. 16).
Of the managed program 5
(FIGS. 6, 19) and the data transferred between the peripheral device management program 80 are stored. The data stored in the common data area 564 and passed between the managed program 5 and the peripheral device management program 80, except for the resource data (FIG. 17), are as follows.

[Resource Data Update Request] The resource data update request is written to the common data area 564 by the device resource information collection unit 54 of the managed program 5, and is read by the common data area management unit 820 of the peripheral device management program 80. . In response to the resource data update request, the managed program 5 requests the peripheral device management program 80 to update the resource data.

[Resource Data Update Response] The resource data update response is written to the common data area 564 by the common data area management section 820 and read by the apparatus resource information collection section 54. In response to the resource data update response, the common data area management unit 820 confirms that the update of the resource data has been completed or that the resource data has not been updated (for example, the peripheral device 24 was not connected and the resource data was collected during the previous connection). That is, when the resource data is used again as it is), the device resource information collecting unit 54 is notified.

[Resource Data Update Notification Transmission Flag] When the device resource information collection unit 54 of the managed program 5 transmits a resource data change notification, this flag is turned on.
This flag is turned off when the resource data change notification is transmitted.
f state. Even if a resource data transmission request is received while this flag is on, the device resource information collection unit 54
Does not collect the resource data of the peripheral device 24, and conversely, collects the resource data when it is received in the off state.

[Device Resource Information Collection Unit 54] The device resource information collection unit 54 receives the resource data transmission request and
Before reading the API, registry, executable file, hardware information, etc. from B562, the common data area 5
A request is made to each of the peripheral device management programs 80 via 64 to update the resource data (FIG. 17) of the corresponding peripheral device 24. When an update response is returned from each of the peripheral management device programs 80, the device resource information collection unit 54 reads the resource data of each of the peripheral devices 24 from the common data area 564, and reads the AP read from the resource DB 562.
Generate resource data in addition to the I, registry, executable file, and hardware information.

Note that, among the resource DB 562, the device resource information collection unit 54, and the peripheral device management program 80, the resource data of the peripheral device 24 is stored in the system management program 4 (FIG. 16) executed by the management device 12 (FIG. 16). 2)
Input / output is performed in a standard format that does not depend on the input / output format of. The device resource information collection unit 54 converts the resource data generated in the standard format according to the data input / output format of the system management program 4, adds the converted data to the completion response, and adds the completion response.
To the system management program 4 via the.

The processing of the managed program 5 and the peripheral device management program 80 according to the second embodiment will be further described with reference to FIGS. FIG. 28 and FIG.
9 is a first and a second flowchart showing the processing (S24) of the managed program 5 shown in FIG. 26 in the second embodiment.

As shown in FIG. 28, step 240 (S
At 240), the device resource information collection unit 54 of the managed program 5 determines whether the receiving unit 502 (FIG. 26) has received a request or a response from the system management program 4 (FIGS. 2 and 24). If a request or a response has been received, the process proceeds to S242; otherwise, FIG.
The process proceeds to S260 shown in FIG.

In step 242 (S 242), the device resource information collection unit 54 determines whether a management information generation response has been received from the system management program 4 of the management device 12. Proceeds to the process of S270 shown in FIG. 29, and in other cases, S24
Go to step 4.

In step 244 (S 244), the device resource information collection unit 54 determines whether a resource data generation request has been received from the system management program 4 of the management device 12. Is S2
The process proceeds to the process of 46, and otherwise proceeds to the process of S254.

In step 246 (S246), the device resource information collection unit 54 refers to the common data area 564 and has no record of transmitting the resource data change notification by the processing of S262 (FIG. 29) (resource data update notification). If the flag is OFF, it is determined that the resource data of the peripheral device 24 needs to be updated, and the process proceeds to S248. Otherwise, the process proceeds to S60 (FIG. 10). In the data collection process in S60, a conversion process for converting the resource data in the standard format into a format suitable for input / output of the system management program 4 is executed.

In step 248 (S248), the device resource information collection unit 54 outputs a resource data update request via the common data area 564, and updates the resource data of the peripheral device 24 to the peripheral device management program 80. Request.

In step 250 (S250), the device resource information collecting unit 54 sets the peripheral device management program 80
Is completed, that is, until the resource data update response is notified to the common data area 564.

At step 252 (S252), S
When the process of FIG. 60 (FIG. 10) is completed, the device resource information collecting unit 54 transmits the information to the management device 12 (FIG.
A resource data generation response (completion response) is transmitted to the system management program 4 (6, 19) of S6), and S240 is performed.
Return to the processing of.

At step 254 (S254), device resource information collection section 54 determines whether or not a resource data transmission request has been received. If a resource data transmission request has been received, the process proceeds to step S256. In the case of S25
Proceed to step 8.

[0205] In step 256 (S256), the device resource information collection unit 54 sends the information to the system management program 4 of the management device 12 via the transmission unit 500 in S60.
In step S240, the resource data of the managed device 22 including the resource data of the peripheral device 24 generated in the above process is associated with a keyword or the like and transmitted as a resource data transmission response.
Return to the processing of.

In step 258 (S258), the device resource information collecting section 54 ends the processing related to the generation of the resource data in response to the resource data processing end request, and clears the common data area 564 as necessary. Is performed, and the process returns to S240.

As shown in FIG. 29, step 260 (S
In 260), the device resource information collection unit 54 determines whether or not the resource data of the peripheral device 24 has been changed. If a change has occurred, the process proceeds to S262; otherwise, the process proceeds to S240. Proceed to processing.

In step 262 (S262), the device resource information collection unit 564 stores the fact that the resource data change notification has been transmitted to the common data area by setting the resource data change notification transmission flag to On.

[0209] In step 264 (S264), the device resource information collection unit 54 determines whether or not the resource data of the peripheral device 24 in the common data area 564 includes management information in the resource data. It is determined that the peripheral device 24 is not managed by the system management program 4 of the management device 12, and the process proceeds to S266.
In other cases, the process proceeds to S268.

At step 266 (S 266), the device resource information collection unit 54 transmits a resource data generation request to the system management program 4 of the management device 12 via the transmission unit 500.

In step 268 (S268), the device resource collection unit 54 transmits a resource data change notification via the transmission unit 500, and notifies that the resource data of the peripheral device 24 has been changed. The process returns to S240 shown above.

In step 270 (S 270), the transmission resource collection unit 54 stores the management information added to the management information generation response from the system management program 4 in the common data area 564 and in the resource data of the corresponding peripheral device 24. Add and memorize.

In step 272 (S 272), the device resource collection unit 54
It requests the peripheral device management program 80 to update the resource data of the peripheral device 24.

In step 274 (S274), the device resource collection unit 54 waits until the resource data update is completed and a resource data update response is returned from the peripheral device management program 80 via the common data area 564. The process returns to S240 shown in FIG.

FIG. 30 is a flowchart showing the processing (S80) of the peripheral device management program 80 shown in FIG. As shown in FIG. 30, step 800 (S80
In 0), the peripheral device connection monitoring unit 806 of the peripheral device management program 80 determines whether or not the corresponding peripheral device 24 is connected to the managed device 22. If the corresponding peripheral device 24 is connected, the process proceeds to S806. Otherwise, S802
Proceed to processing.

In step 802 (S802), the common data area management unit 820 determines whether or not a resource data update request has been issued from the managed program 5 via the common data area 564. If it has been issued, the process proceeds to S804; otherwise, the process proceeds to S822.

In step 804 (S804), the peripheral device connection monitoring unit 806 determines whether or not the peripheral device 24 is connected.
Otherwise, the process proceeds to S822.

At step 806 (S806), common data area management section 820 transmits
The resource data transmission request is transmitted to the peripheral device program 24 of the peripheral device 24.

At step 808 (S808), the common data area management unit 820 receives a resource data transmission response from the peripheral device 24 via the receiving unit 804.

In step 810 (S810), the common data area management unit 820 determines
Then, it is determined whether there is resource data of the peripheral device 24 before that. If there is resource data before, the process proceeds to S814. Otherwise, the process proceeds to S812.

In step 812 (S812), the common data area management unit 820 stores the resource data (FIG. 17) received from the peripheral device 24 in the common data area 564.

At step 814 (S814), common data area management section 820 determines whether or not unset management information is stored in common data area 564.
If it is stored, the process proceeds to S816; otherwise, the process proceeds to S820.

At step 816 (S816), common data area management section 820 transmits
The management information of the resource data of the corresponding peripheral device 24 is read from the common data area 564, added to the management information setting request, and transmitted to the peripheral device 24. At this time, as a method of associating the peripheral device 24 with the resource data stored in the common data area 564, the manufacturer and model number in the resource data in the resource data transmission response received in the processing of S808, For example, the resource data stored in 564 may be compared with the manufacturer, model number, or the like, and a matching item may be selected and associated.

In step 818 (S818), the common data area management unit 820
The management information setting response is received from the peripheral device 24.

At step 820 (S820), common data area management section 820 uses the resource data of peripheral device 24 included in the resource data transmission response received in the processing of S808 to store the resource data in common data area 564. Update.

At step 822 (S822), the common data area management unit 820 returns a resource data update response to the managed program 5 via the supply data area 564, and notifies that the resource data of the peripheral device 24 has been updated. I do.

[Peripheral Device Program 26] Next, the peripheral device program 26 will be described. FIG. 31 is a diagram showing a configuration of the peripheral device program 26 executed by the peripheral device 24 shown in FIG. As shown in FIG. 31, the peripheral device program 26 includes an information collecting unit 268, an information setting unit 270, a transmitting unit 264, and a receiving unit 266. The peripheral device program 26 uses these components to transmit and receive data to and from the managed device 22 and to store and manage management information set from the managed device 22.
Actually, the peripheral device 24 also executes software for realizing the respective functions, but other software irrelevant to the description of the present invention is omitted in FIG.

[Transmission Unit 264] The transmission unit 264 transmits a resource data generation response of the peripheral device 24 to the managed device 22 in response to a request from the information collection unit 268. Also,
The transmitting unit 264 transmits a management information setting response to the managed device 22 in response to a request from the information setting unit 270.

[Receiving Unit 266] The receiving unit 266 receives the resource data transmission request from the managed device 22, and
70 is output. Further, the receiving unit 266 receives the management information setting request from the managed device 22 and
0 is output as a resource data generation response.

[Information Collection Unit 268] Information Collection Unit 268
Receives the resource data transmission request from the receiving unit,
Resource data in a format that can be processed by the peripheral device management program 80 (FIG. 26) of the managed device 22 from the data set in the nonvolatile memory 260 of FIG. 17) is generated and transmitted to the managed device 22 via the transmission unit 264.

[Information setting section 270] Information setting section 270
Receives the management information setting request from the receiving unit 266, and stores the management information added thereto in the nonvolatile memory 2 of the peripheral device 24.
Set to 60. When the management information is set, the information setting unit 2
70 transmits a management information setting response to the managed device 22 via the transmission unit 264.

The processing of the managed system program 8 will be further described with reference to FIG. FIG. 32 is a flowchart showing the processing (S84) of the peripheral device program 26 shown in FIG.

As shown in FIG. 32, step 840 (S
840), the receiving unit 2 of the peripheral device program 26
The step 66 judges whether or not a request has been received from the managed device 22. If the request has been received, the process proceeds to S842; otherwise, the process remains at S840.

In step 842 (S842), the receiving section 266 determines whether or not a resource data transmission request has been received from the managed device 22, and if a resource data transmission request has been received, the process proceeds to S844. Otherwise, the process proceeds to S848.

In step 844 (S844), the information collecting unit 268 reads data from the nonvolatile memory 260 of the peripheral device and generates resource data (FIG. 17).

In step 846 (S846), the information collection unit 268 transmits the generated resource data generation response to the managed device 22 via the transmission unit 264.

In step 848 (S848), receiving section 266 determines whether or not a management information setting request has been received, and if a management information setting request has been received, the process proceeds to step S850. Goes to the processing of S854.

In step 850 (S850), information setting section 270 stores the management information included in the received management information setting request in nonvolatile memory 260 of peripheral device 24.

At step 852 (S852), information setting section 270 transmits a management information setting response to transmission section 264.
To the managed device 22 via the.

At step 854 (S854), the CPU or the like of the peripheral device 24 executes a program for performing processing in response to other processing requests (for example, a printing process when the peripheral device 24 is a printer).

[Operation of Computer Network 7] The operation of the computer network 7 shown as the second embodiment will be described below with reference to FIGS.
FIGS. 33 to 38 are first to sixth sequence diagrams showing the operation of the computer network 7 shown as the second embodiment.

First, referring to FIG.
System management program 4 in FIG. 16 (FIGS. 2, 19)
Is a case where the managed system program 8 (FIG. 26) of the managed device 22 is instructed to collect the resource data of the peripheral device 24 and the computer network 7 in the case where the peripheral device 24 is not connected. The operation will be described.

As shown in FIG. 33, the system administrator
When the management device 12 is instructed to collect resource data by operating the management device 12 (1), the management device 12 transmits a resource data generation request to the managed device 22 (2).

Upon receiving the resource data generation request, the managed device 22 uses the data stored in the common data area 564 (FIG. 26) to enter the system management program 4 of the management device 12 (FIGS. 2 and 19). The resource data in a format suitable for the output is generated (3), and a resource data generation completion response is transmitted to the management device 12 (4).

When receiving the resource data generation response, the management device 12 transmits a resource data transmission request to the managed device 22 (5). When receiving the resource data transmission request, the managed device 22 transmits the request to the management device 12 in addition to the resource data transmission response (6).

When receiving the resource data transmission response, the management device 12 transmits a resource data processing end request to the managed device 22 (7). Upon receiving the resource data processing end request, the managed device 22 ends the processing related to the generation and transmission of the resource data (8).

Next, referring to FIG.
(FIG. 16) shows a case where the managed device 22 is instructed to collect the resource data of the peripheral device 24,
The operation of the computer network 7 when is connected will be described.

As shown in FIG. 34, the system administrator
When the management device 12 is instructed to collect resource data by operating the management device 12 (1), the management device 12 transmits a resource data generation request to the managed device 22 (2).

When receiving the resource data generation request, the managed device 22 executes the peripheral device program 26 of the peripheral device 24.
A resource data transmission request is transmitted to (FIG. 31) (3). When receiving the resource data transmission request, the peripheral device 2
4 generates resource data (FIG. 17) in a standard format that does not depend on the input / output format of the system management program 4 (FIGS. 2 and 19) of the management device 12 (4), and transfers the generated resource data to the managed device 22. Is transmitted (5).

When receiving the resource data, the managed device 22
Stores the received standard format resource data in the common data area 564 (FIG. 26) (6), and transmits a resource data generation completion response to the management device 12 (7). Upon receiving the resource data generation completion response, the management device 12 transmits a resource data transmission request to the managed device 22 (8).

Upon receiving the resource data generation completion response, the management device 12 transmits a resource data transmission request to the managed device 22 (9). Upon receiving the resource data transmission request, the managed device 22 converts the resource data into a format suitable for the input / output format of the system management program 4 of the management device 12, and transmits the format to the management device 12 (10). Upon receiving the resource data, the management device 12 transmits a resource data processing end request to the managed device 22 (11) Upon receiving the resource data processing end request, the management device 22
Terminates the processing related to the generation and transmission of the resource data (1
2).

Next, referring to FIG. 35, the managed device 22
The operation of the computer network 7 when the managed system program 8 (FIG. 26) detects a change in the resource data of the peripheral device 24 will be described.

As shown in FIG. 35, when detecting that the peripheral device 24 has been connected (1), the managed device 22 transmits a resource data transmission request to the peripheral device (2).
Upon receiving the resource data transmission request, the peripheral device 24 generates resource data in a standard format (3), and transmits a resource data transmission response with the generated resource data added to the managed device 22 (4). .

The managed device 22 is a peripheral device 2 of a standard format.
4 is stored in the common data area 564 (FIG. 26) (5), and a change in the resource data of the peripheral device 24 is detected (6). Upon detecting the change, the managed device 22 notifies the management device 12 of the change in the resource data by the resource data change notification (7). Upon receiving the resource data change notification, the management device 12 transmits a resource data generation request to the managed device 22 (8).

Upon receiving the resource data generation request signal, the managed device 22 transfers the data of the peripheral device 24 in the standard format stored in the common area to the system management program 4 of the management device 12 (FIGS. 2 and 19). The resource data is converted into a format suitable for the output format to generate resource data (9), and a resource data generation response is transmitted to the management device 12 (10).

Upon receiving the resource data generation completion response, the management device 12 adds the resource data transmission request to the resource data transmission response and transmits the resource data transmission request to the managed device 22 (1).
1). Upon receiving the resource data transmission request, the managed device 2
2 adds the generated resource data to the resource data transmission response and transmits it to the management device 12 (12). Upon receiving the resource data transmission response, the management device 12 transmits a resource data processing end request to the managed device 22 (13).
Terminates the processing related to the generation and transmission of the resource data (1
4).

Next, referring to FIG. 36, the managed device 22
The operation of the computer network 7 for setting the management information for the peripheral device 24 when the peripheral device 24 is continuously connected to the peripheral device 24 will be described.

As shown in FIG. 36, when detecting that the peripheral device 24 is connected (1), the managed device 22
Transmits a resource data transmission request to the peripheral device (2). Upon receiving the resource data transmission request, the peripheral device 24
Generates resource data in a standard format (3), and sends a resource data generation response to which the generated resource data is added to the managed device 2.
2 (4).

The managed device 22 is a peripheral device 2 of a standard format.
4 is stored in the common data area 564 (FIG. 26) (5), and it is detected that the resource data of the peripheral device 24 does not include management information (6). If the management information is not included in the resource data of the peripheral device 24, the managed device 22 transmits a management information generation request for the peripheral device 24 to the management device 12 (7).

Upon receiving the management information generation request, the management device 12 generates management information of the peripheral device 24 in a format dependent on the input / output format of the system management program 4 (8), and generates the management information. It is transmitted to the managed device 22 in addition to the response (9). Upon receiving the management information generation response, the managed device 22 separates the management information included in the management information generation response, converts the management information into a standard format, stores it in the common data area 564 (FIG. 26) (10), and further The peripheral device 2 adds the management information in the standard format to the management information setting request.
4 (11).

When receiving the management information setting request, the peripheral device 24 stores the management information included in the received management information setting request in the nonvolatile memory 260 (12), and returns a management information setting response to the managed device 22. (13).

Next, a management information setting operation of the computer network 7 when the peripheral device 24 is disconnected while the management device 12 is generating management information will be described with reference to FIG.

As shown in FIG. 37, when detecting that the peripheral device 24 has been connected (1), the managed device 22 transmits a resource data transmission request to the peripheral device (2).
Upon receiving the resource data transmission request, the peripheral device 24 generates resource data in a standard format (3), adds the generated resource data to the resource data transmission request, and transmits the resource data transmission request to the managed device 22 (4). ).

The managed device 22 is a peripheral device 2 of a standard format.
4 is stored in the common data area 564 (FIG. 26) (5), and it is detected that the resource data of the peripheral device 24 does not include management information (6). If the management information is not included in the resource data of the peripheral device 24, the managed device 22 transmits a management information generation request for the peripheral device 24 to the management device 12 (7). Upon receiving the management information generation request, the management device 12
Generates the management information of the peripheral device 24 in a format depending on the input / output format of the system management program 4 (8).

Here, while the management device 12 is generating the management information, the response is delayed, for example, the connection with the peripheral device 24 is cut off for some reason. When the management device 12 returns the management information generation response by adding the generated management information to the managed device 22 (9), the managed device 22 stores the management information of the peripheral device 24 in the standard format in the common data area 564 ( (10). When detecting the connection of the peripheral device 24 (11), the managed device 22 requests the peripheral circuit 24 to transmit resource data (12).

Upon receiving the resource data transmission request, the peripheral device 24 generates standard format resource data (FIG. 17) (1).
3) The generated resource data is added to the resource data transmission response and transmitted to the managed device 22 (14). When receiving the resource data transmission response, the managed device 22 detects that the management information is not set in the resource data (1).
5) The management information setting request to which the management information stored in the common data area is added as described above is transmitted to the peripheral device 24 (16).

Upon receiving the management information setting request, the peripheral device 24 stores the management information added to the management information setting request in the non-volatile memory 260 (FIG. 31) (17). An information setting response is returned (18).

Next, referring to FIG. 38, when the peripheral device 24 is reset to the factory shipping state for the reason of power cutoff including the backup power supply, the managed device 2 is reset.
The operation of the computer network 7 for recovering the management information of the peripheral device 24 will be described.

As shown in FIG. 38, when the connection of the peripheral device 24 is detected (1), the managed device 22
Requesting transmission of resource data to the server (2). When transmission of the resource data is requested, the peripheral device 24 generates resource data (FIG. 17) (3), and transmits the generated resource data to the managed device (4).

When receiving the resource data transmission response from the peripheral device 24, the managed device 22 detects that the management information in the resource data of the resource device 24 has been reset and the resource data no longer contains the management information. (5) A management information setting request to which the management information of the peripheral device 24 stored in the common data area 564 is added is transmitted to the peripheral device 24. When receiving the management information setting request, the peripheral device 2
4 stores the management information included in the received management information setting request in the nonvolatile memory 260 (FIG. 31) (7),
A management information setting response is returned to the managed device 22 (8).

[Effects of Computer System 7] As described above, in the computer system 7 shown as the second embodiment, the peripheral device management program 80
However, the resource data of the peripheral device 24 is stored in a standard format, and the managed program 5 converts the resource data into a format suitable for input / output of the system management program 4. Therefore, the managed program 5 does not need to process data in different formats for each type of the peripheral device 24.

The managed device 22 automatically detects that the peripheral device 24 is not assigned an asset number, a user name, or the like (management information), and notifies the management device 12
Since the management information generated by the management device 12 can be set in the peripheral device 24, it is not necessary for the system administrator to set the management information in the peripheral device 24 when connecting to the managed device 22. it can.

[0273]

As described above, according to the resource management system, the resource management device, the managed device, and the method according to the present invention, a network system in which a plurality of computers and the like are connected via a network device. , It is possible to always manage what hardware resources and software resources (device resources) each device has, and what kind of change has occurred in each device resource.

The resource management system according to the present invention
According to the resource management device, the managed device and the methods thereof, it is possible to display resource information of each device constituting the network system, to facilitate the system management operation, and to reduce the user's labor required for the system management operation. it can.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a configuration of a computer network to which a first device resource management method according to the present invention is applied;

FIG. 2 is a diagram illustrating a configuration of software executed by the management device illustrated in FIG. 1;

FIG. 3 is a diagram showing resource information collection and execution performed by a system management program.
FIG. 5 is a diagram illustrating a resource information display function among management functions.

FIG. 4 is a diagram showing resource information collection and execution performed by a system management program.
FIG. 3 is a diagram illustrating a group management function among management functions.

FIG. 5 is a diagram illustrating a resource information collection / execution performed by the system management program.
FIG. 4 is a diagram illustrating a list display function among management functions.

FIG. 6 is a diagram illustrating a software configuration of the managed device illustrated in FIG. 1;

FIG. 7 is a flowchart showing a keyword setting process (S10) for the managed device shown in FIGS. 1 and 6;

FIG. 8 is a flowchart (main flow diagram; S12) showing an outline of the processing of the management device shown in FIGS. 1 and 2;

9 is a flowchart showing a process (resource data collection process; S20) when the management device (FIGS. 1 and 2) shown in FIG. 8 collects resource data from the managed devices (FIGS. 1 and 6). .

FIG. 10 is a flowchart showing a resource data generation process (S60 shown in FIG. 9) by the resource information collection unit.

11 is a diagram illustrating an example of a GUI image displayed on the display device by the display unit of the management device shown in FIG. 2;

12 is a diagram illustrating the difference analysis processing (S30, S3) illustrated in FIG.
It is a flowchart which shows 2).

13 is a diagram illustrating a difference data generation process (S7) illustrated in FIG. 12;
It is a flowchart which shows 0).

FIG. 14 is a diagram illustrating a matching analysis process (S40, S40) illustrated in FIG. 8;
It is a flowchart which shows 42).

FIG. 15 is a diagram showing resource data collection processing when the managed device (FIGS. 1 and 6) detects a change in device resources.

FIG. 16 is a diagram illustrating a configuration of a computer network to which a second device resource management method according to the present invention is applied;

17 is a diagram exemplifying resource data (common resource data and unique resource data) set to be readable by software in the peripheral device shown in FIG. 16;

FIG. 18 is a diagram illustrating an example in which the resource data shown in FIG. 17 is classified into resource data common to peripheral devices (common resource data) and resource data unique to each peripheral device (unique resource data), and is executed by the management device. FIG. 5 is a diagram illustrating resource data converted into a format suitable for an input / output format of a system management program.

FIG. 19 is a diagram illustrating a list of signals transmitted and received among a management device, a managed device, and a peripheral device.

FIG. 20 is a diagram exemplifying connectable device data indicating peripheral devices permitted to be connected to a managed device.

FIG. 21 illustrates an example of non-connectable device data in which a keyword and a device ID of a managed device to which a peripheral device that is not permitted to be connected is associated;

FIG. 22 is a diagram illustrating a data format of a management information generation request.

FIG. 23 is a diagram illustrating a data format of a management information generation response.

24 is a flowchart showing a process (S54) of a system management program executed by the management device shown in FIG.

FIG. 25 is a diagram illustrating a management information generation response.

26 is a diagram showing a configuration of a managed system program executed in the managed device shown in FIG.

FIG. 27 is a diagram illustrating a data format of a resource data transmission response received from a peripheral device.

FIG. 28 is a first flowchart showing a process (S24) in the second embodiment of the managed program 5 shown in FIG. 37;

FIG. 29 is a second flowchart showing a process (S24) of the managed program 5 shown in FIG. 37 in the second embodiment.

FIG. 30 is a flowchart showing processing (S80) of the peripheral device management program shown in FIG. 26;

FIG. 31 is a diagram showing a configuration of a peripheral device program executed by the peripheral device shown in FIG. 16;

FIG. 32 is a flowchart showing processing (S84) of the peripheral device program shown in FIG. 31;

FIG. 33 is a first sequence diagram showing an operation of the computer network shown as the second embodiment.

FIG. 34 is a second sequence diagram illustrating an operation of the computer network illustrated as the second embodiment.

FIG. 35 is a third sequence diagram showing the operation of the computer network 7 shown as the second embodiment.

FIG. 36 is a fourth sequence diagram illustrating the operation of the computer network 7 illustrated as the second embodiment.

FIG. 37 is a fifth sequence diagram showing the operation of the computer network 7 shown as the second embodiment.

FIG. 38 is a sixth sequence diagram showing the operation of the computer network 7 shown as the second embodiment.

[Explanation of symbols]

1, 7: Computer network 10, 12: Management device 20, 22, 20-1 to 20-i to 20-n, 22-1
22-i to 22-n managed device 30 communication network 100 CPU 102 input device 104 display device 106 storage device 108 recording medium 110 ... Communication device 4 ... System management program 40 ... Communication unit 400 ... Transmission unit 402 ... Reception unit 42 ... Data analysis unit 44 ... Input unit 46 ... Display unit 48 ... Database unit 480 ... System management DB 482 ... Human resources / organization DB 484 ... Device resource information DB 5 ... Managed program 50 ... Communication unit 500 ... Transmission unit 502 ... -Receiving unit 52-Log analyzing unit 54-Device resource information collecting unit 56-Database unit 560-Install log DB 562-Resource DB 564-Common data area 8: Managed system program 80-1 to 80-j to 80-m: Peripheral device management program 802: Transmission unit 804: Receiving unit 806: Peripheral device connection monitoring unit 806 820 ..Common data area management unit 6 OS 24 Peripheral device 260 Nonvolatile memory 26 Peripheral device program 264 Transmitting unit 266 Receiving unit 268 Information collection Unit 270: Information setting unit

 ──────────────────────────────────────────────────の Continued on the front page (72) Inventor Noriyuki Igawa 1623-14 Shimotsuruma, Yamato City, Kanagawa Prefecture Inside the Yamato Office of IBM Japan, Ltd. (72) Inventor Sugio Ishii Yamato City, Kanagawa Prefecture 1623 No. 14 Shimotsuruma F-term (reference) at the Yamato Office of IBM Japan, Ltd.

Claims (17)

[Claims] 1. A resource management system that includes a resource management device and one or more managed devices, and manages device resources of each of the managed devices, wherein each of the managed devices includes: Resource data generation means for generating resource data indicating the device resources of the resource management apparatus; and resource data transmission means for transmitting the generated resource data to the resource management apparatus. A resource management system comprising: resource data receiving means for receiving the resource data from each of the management devices; and resource data management means for managing the received resource data of each of the managed devices. 2. The resource management device according to claim 1, further comprising: a resource data transmission requesting unit for requesting each of the managed devices to transmit the resource data in response to at least a device resource change notification from the managed device. In each of the managed devices, the resource data generating means generates at least the resource data indicating the device resources of each of the managed devices in response to a request for transmission of the resource data; The transmission unit transmits the generated resource data to the resource management device at least in response to a request for transmission of the resource data, or when the device resource is changed, 2. The resource management system according to claim 1, wherein a notification of a resource change is transmitted to the resource management device. 3. The resource management device, wherein the resource data management means includes: standard data storage means for storing standard data indicating device resources which each of the managed devices has as a standard; The resource data, difference data generating means for generating difference data indicating a difference between the received standard data corresponding to the resource data, and the resource data received from each of the managed devices; 2. The resource management system according to claim 1, further comprising: first resource management means for managing the difference data. 4. The resource management device, wherein the resource data management means is configured to execute, based on the resource data received from the managed device, each of the managed devices corresponding to the received resource data in advance. A specific resource determining unit that determines whether or not a predetermined specific device resource is included; based on a result of the determination, the specific device resource included in each of the managed devices; 2. The resource management system according to claim 1, further comprising second resource management means for managing the resource data. 5. In each of the managed devices, the resource data generating means converts the resource data indicating the device resources of the managed device into a format suitable for input to the resource data receiving means, or The resource data transmitting unit generates the resource data in a format (first format) different from this format, and converts the resource data generated in the first format into a format suitable for input to the resource data receiving unit (first format). 2. The resource management system according to claim 1, wherein the resource management system converts the data into a second format and transmits the data to the resource management device. 6. The resource management device includes: a setting information generating unit configured to generate setting information to be set in each of the managed devices; and transmitting the generated setting information to each of the managed devices in response to a request. Each of the managed devices has a setting information receiving unit that receives the transmitted setting of the setting information, and a determining unit that determines whether the setting of the setting information has been received. The resource management system according to claim 1, further comprising: a setting information requesting unit that requests the resource management device to transmit the setting information when the setting of the setting information is not accepted. 7. A resource management device for managing device resources of each of one or more managed devices, wherein each of the managed devices generates resource data indicating the device resources of the managed devices, Resource data receiving means for transmitting the generated resource data to the resource management device and receiving the resource data from each of the managed devices; and receiving the resource data of each of the managed devices. A resource management device having resource data management means for managing. 8. Each of the managed devices includes at least:
Generates the resource data indicating the device resources of each of the managed devices in response to the request for transmission of the resource data, at least, in response to the request for transmission of the resource data, the generated resource data, Transmitting to the resource management device, or, when there is a change in the device resource, transmitting a notification of the change in the device resource to the resource management device; at least the device resource from the managed device; 8. The resource management device according to claim 7, further comprising resource data transmission requesting means for requesting each of said managed devices to transmit said resource data in response to said change notification. 9. The resource data management means includes: standard data storage means for storing standard data indicating device resources each of the managed devices has as a standard; the resource data received from the managed device; Difference data generating means for generating difference data indicating a difference from the standard data corresponding to the generated resource data, managing the resource data received from each of the managed devices, and the generated difference data The resource management device according to claim 7, further comprising: a first resource management unit that performs the operation. 10. The resource data management means, wherein, based on the resource data received from the managed device, each of the managed devices corresponding to the received resource data is a predetermined specific device. A specific resource determining unit for determining whether or not a resource is included; and managing the specific device resource included in each of the managed devices and the resource data of each of the managed devices based on a result of the determination. The resource management device according to claim 7, further comprising a second resource management unit. 11. Each of the managed devices accepts the transmitted setting of the setting information, determines whether the setting of the setting information has been accepted, and determines whether the setting of the setting information has not been accepted. Requesting the resource management device to transmit the setting information, setting information generating means for generating setting information to be set for each of the managed devices, and generating the setting information in response to the request. 8. The resource management device according to claim 7, further comprising setting information transmission means for transmitting the setting information to each of the managed devices. 12. A managed device in which device resources are managed by a resource management device, wherein the resource management device comprises:
Resource data generating means for receiving the resource data from each of the managed devices, managing the received resource data of each of the managed devices, and generating resource data indicating device resources of the managed device; And a resource data transmission unit for transmitting the generated resource data to the resource management device. 13. The resource management device requests transmission of the resource data to each of the managed devices in response to at least a device resource change notification from the managed device. , At least in response to a request for transmission of the resource data, generating the resource data indicating the device resources of each of the managed devices, wherein the resource data transmission unit responds at least to the request for transmission of the resource data. Transmitting the generated resource data to the resource management device, or transmitting a notification of the device resource change to the resource management device when the device resource is changed. The managed device according to claim 12. 14. The resource data generating means may convert the resource data indicating the device resources of the managed device into a format suitable for input to the resource data receiving means or a format different from this format (the 1), and the resource data transmitting means converts the resource data generated in the first format into a format (second format) suitable for input to the resource data receiving means. 13. The managed device according to claim 12, wherein the device is transmitted to the resource management device. 15. The resource management device generates setting information to be set for each of the managed devices, and transmits the generated setting information to each of the managed devices in response to a request. Setting information accepting means for accepting the setting of the setting information; determining means for judging whether or not the setting of the setting information is accepted; if the setting of the setting information is not accepted, the resource management device 13. The managed device according to claim 12, further comprising setting information requesting means for requesting transmission of the setting information. 16. A resource management method in which a resource management device manages device resources of each of one or more managed devices, wherein each of the managed devices includes resource data indicating the device resources of the managed devices. And transmitting the generated resource data to the resource management device. The resource management device receives the resource data from each of the managed devices, and each of the received managed devices. A resource management method for managing the resource data. 17. A recording medium storing a program executed in a resource management device that manages device resources of each of one or more managed devices, wherein each of the managed devices has a corresponding one of the managed devices. Generating resource data indicating device resources, transmitting the generated resource data to the resource management device, and receiving the resource data from each of the managed devices; And a resource data management step of managing the resource data of each of the managed devices.