JP2013214324A - Server device, control method of server device, program and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mechanism capable of visually displaying an allocation status of devices connected to a network corresponding to a terminal of an operator.SOLUTION: A server device comprises: client information storage means for storing a setting state including arrangement place information of a client device; device information storage means for storing a setting state including arrangement place information of a device; device determination means for determining a device whose arrangement place information same as the arrangement place information of the client device is stored; device map generation means for generating a device map in which the device determined by the device determination means is displayed in a seat table which corresponds to the arrangement place information; and installed device determination means which can determine a device supporting a device driver installed in the client device. When the setting state of the device determined by the installed device determination means is different from the setting state of the device stored in the device information storage means, the device map generation means displays and controls that effect on the device map.

Description

  The present invention relates to a technique for displaying an arrangement status of devices connected to a network on a floor map.

  In recent years, development of Web applications that can display a list of network devices connected to a network, display the status of network devices, and various types of information set in the network devices has become active.

  In addition, a network device has been developed that provides a function for displaying the status of the network device and various information set in the network device from the web browser of the PC by bundling the web server inside the network device. Yes.

  As one function of such a Web application, there is a function of arranging and displaying a management target network device on a virtual map so that the installation location of the network device in the real world can be known. (Hereafter, the map created by this function is called “device map”.)

  However, even if a device map is used, it may be difficult to grasp the arrangement status on a floor where there are a plurality of devices such as an office.

As a technique corresponding to this, in Patent Document 1, the position information of each device connected to the network is hierarchically managed to identify the position of the device requested to be searched on the hierarchical structure. A technique for enabling the user to display the position of the user in an easily understandable manner is disclosed.
JP 2001-84210 A

  However, according to Patent Document 1, the device map can only identify the current device location. For this reason, there is a problem that it is difficult to determine which device can be used, for example, when the location of the device is changed or when the user moves.

  For example, it is desirable to be able to visually determine whether or not there is a device nearby that can use a plurality of printer drivers set in the computer.

  In view of the above problems, an object of the present invention is to provide a mechanism capable of visually displaying an arrangement state of devices connected to a network corresponding to an operator's terminal.

  To achieve the above object, client information storage means for storing a setting state including installation location information of the client device, device information storage means for storing a setting state including device installation location information, and an installation location of the client device A device map for identifying a device in which the same installation location information is stored, and a device map for generating a device map displayed on a seating chart corresponding to the installation location information by the device specified by the device specification unit And an installation device specifying unit capable of specifying a device corresponding to the device driver installed in the client device. The device map generating unit includes a setting state of the device specified by the installation device specifying unit, device information Device stored in storage means If the setting condition is different, and displaying control to that effect on the device map.

  An object of the present invention is to provide a mechanism capable of visually displaying the arrangement status of devices connected to a network corresponding to an operator's terminal.

1 is a system configuration diagram of a device management system according to an embodiment of the present invention. It is a hardware block diagram of the information processing apparatus which can apply the device management system which concerns on embodiment of this invention. It is a functional block diagram of the device management system which concerns on embodiment of this invention. It is a figure which shows an example of the menu screen of the device management system which concerns on embodiment of this invention. It is a figure which shows an example of the device map screen in the device management system which concerns on embodiment of this invention. It is a flowchart which shows an example of the main flow in the device management system which concerns on embodiment of this invention. It is a flowchart which shows an example of the display process of the device list in the device management system which concerns on embodiment of this invention. It is a flowchart which shows an example of the difference process in the device management system which concerns on embodiment of this invention. It is a figure which shows an example of the client information registration screen in the device management system which concerns on embodiment of this invention. It is a figure which shows an example of the device registration screen in the device management system which concerns on embodiment of this invention. It is a figure which shows an example of the client registration information in the device management system which concerns on embodiment of this invention. It is a figure which shows an example of the device registration information in the device management system which concerns on embodiment of this invention. It is a figure which shows an example of the floor map in the device management system which concerns on embodiment of this invention. It is a flowchart which shows an example of the acquisition process of the driver in the device management system which concerns on embodiment of this invention. It is a flowchart which shows an example of the driver installation process in the device management system which concerns on embodiment of this invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a system configuration diagram of a device management system according to an embodiment of the present invention.

  As a device management system, a client apparatus 101, a multifunction peripheral 102, a printer 103, and a server apparatus 104 are connected via a communication network 500 in a communicable state. Multiple devices can be installed.

  The client apparatus 101 inquires of the server apparatus 104 about the arrangement status of devices such as the MFP 102 and the printer 103 connected on the network.

  When the server apparatus 104 receives an inquiry about the device arrangement status from the client apparatus 101, the server apparatus 104 returns a content arrangement status corresponding to the terminal.

  In this embodiment, the MFP 102 and the printer 103 are exemplified as devices for managing the arrangement status. However, any device that can be connected to a network may be used, and a FAX and a scanner are also included.

  FIG. 2 is a hardware configuration diagram of an information processing apparatus to which the device management system according to the embodiment of the present invention can be applied. The present invention can be applied as the client device 101 or the server device 104.

  Based on the program stored in the program ROM 203, each device connected to the system bus 200 is controlled to control the entire information processing apparatus.

  The data ROM 204 stores various data. A RAM 202 functions as a main memory, work area, and the like for the CPU 201.

  A keyboard controller (KBC) 205 controls input from a keyboard (KB) 209 or a pointing device (not shown) such as a mouse.

  A display controller (DC) 206 controls display on the display 210. The display may be a CRT or another type of display device such as an LCD.

  A memory controller (MC) 207 controls access to the hard disk (HD) 211.

  A peripheral device connection interface (USB I / F) 208 controls access to a portable storage medium (not shown) and other peripheral devices.

  A network interface (NW I / F) 220 controls communication with the output device 230 via the network 150.

  FIG. 3 is a functional configuration diagram of an information processing apparatus to which the device management system according to the embodiment of the present invention can be applied.

  The hardware configuration such as the CPU 201 in FIG. 2 is a software configuration that functions by operating in cooperation with each other.

  Various data can be stored in a hard disk or the like of the client device 101 or the server device 104.

  The server device 104 stores an office map 311, client information 312, device information 313, and a device driver 314.

  The client device 101 stores client (holding) information 315.

  The floor map 311 is a model of a floor layout for displaying the arrangement status of devices and client devices. The map generation unit 301 synthesizes the arrangement status of the devices and client devices into the floor map and displays it on the client device 101.

  The client information 312 stores information on clients that use the device management system, and details will be described with reference to FIG.

  Device information 313 stores information on devices managed by the device management system, and will be described in detail with reference to FIG.

  The device driver 314 is a device driver managed by the device management system, and is used by being downloaded from a client device that needs to be installed.

  The client (holding) information is stored in the client device, and information on device drivers installed in the client device is stored. Details will be described with reference to FIG.

  The client information 312 and the client (holding) information 315 are acquired by the client information acquisition unit 302, the device information 312 is acquired by the device information acquisition unit 303, and the map generation unit 301 generates a map reflecting the arrangement status.

  The driver processing unit 304 controls driver download and installation for client devices that require device driver installation.

  The storage destination of various information is an example, and all information can be managed by the server device, or all information can be managed by the client device. It is also possible to configure the information to be distributed and stored.

  FIG. 4 is a diagram showing an example of a menu screen of the device management system according to the embodiment of the present invention.

  The device map menu 400 is displayed on the screen of the client device when an application is started from the client device. The application activation includes, for example, accessing a predetermined URL of a Web server.

  A device map display button 401, a client information registration menu 402, and a device information registration menu 403 are displayed in a selectable state.

  When the device map display menu 401 is selected, a process for displaying a device map, which will be described later, is started, and a device map 500 displaying the arrangement status shown in FIG. 5 is displayed.

  FIG. 5 is a diagram showing an example of a device map screen in the device management system according to the embodiment of the present invention.

  The device map 500 is displayed by arranging the position of the client device and the device and the current state of the device installed in the client device on the floor map.

  Reference numeral 501 indicates that the PR 9900 is connected to the network. 502 indicates that the MFP 222 is not connected to the network. It also indicates that the IP address and driver version have been changed.

In 503 and 504, it can be seen by arrow that PR8800 has been moved from 503 to 504. It can also be seen that it is connected to the network.
Reference numeral 504 denotes the location of the operating client device.

  The operating client device is displayed as My computer 509.

  In the unnecessary printer setting column 505, it can be seen that the device installed in the terminal device has disappeared from the floor. It is also possible to delete a device driver as an unnecessary driver.

  The My computer information 506 displays a list of device arrangement statuses with respect to connected client apparatuses.

  When the previous device location display 507 is selected, the device location stored at the time of the previous information update is displayed based on the information stored in the device information 312.

The previous access date 508 displays the date when the previous device management system was accessed.
Returning to the description of FIG.

  When the client information registration menu 402 is selected, a client information registration screen 900 shown in FIG. 9 is displayed.

  FIG. 9 is a diagram showing an example of a client information registration screen in the device management system according to the embodiment of the present invention.

  On the client information registration screen 900, it is possible to input basic information 901 and a seating method 905 of a client device that uses the device management system.

  In the basic information 901, a computer name 902, a MAC address 903, and an IP address are input.

  In the seating method 905, a floor, a floor, a block, a seat number, and the like on which the client device is installed are input. The information entered here is used as the location on the device map.

  As an input method, manual input by an operator of the client device may be used, or information may be acquired from a terminal management DB (not shown) using login information to the system.

  When the registration button 906 is pressed, it is stored as client information 312 in the server device.

  FIG. 11 is a diagram showing an example of client registration information in the device management system according to the embodiment of the present invention.

  The client registration information 1101 is a table showing an example of client information 312 stored in the server device. The contents registered from the client information registration screen 900 are stored.

  The last access date indicates the date when the client device last accessed the device management system.

  The client holding information 1102 is a device name and a MAC address installed in the client device. Stored as client (holding) information 315 in the client device.

When displaying a device map, it is used to determine the status of devices installed on the client. In this embodiment, the MAC address is used to identify the device, but the present invention is not limited to this, and any device that can identify the device can be used.
Returning to the description of FIG.

  When the device information registration menu 403 is selected, a device information registration screen 1000 shown in FIG. 10 is displayed. This menu is desirably made available only to the administrator. In this case, “administrator only” may be displayed so that only the administrator can select.

  FIG. 10 is a diagram showing an example of a device registration screen in the device management system according to the embodiment of the present invention.

  On the device information registration screen 1000, basic device information 1001, a seating method 1005, and driver information 1006 managed by the device management system can be input.

  In the basic information 1001, a device name 1002, a MAC address, and an IP address 1004 are input.

  In the seating method 1005, the floor, floor, block, and seat number on which the device is installed are input. The information entered here is used as the location on the device map.

  In the driver information 1006, the device driver version 1007 and the storage destination 1008 are input. Register when the device driver of a device is changed. When the storage destination 1008 is a shared folder or the like, it is necessary to copy the device driver. It is possible to download and install the device driver registered in this menu from the client terminal on which the device map is displayed.

  When the registration button 1009 is pressed, it is stored as device information 313 in the server apparatus.

  FIG. 12 is a diagram showing an example of device registration information in the device management system according to the embodiment of the present invention.

  The device registration information 1201 is a table showing an example of the device information 313 stored in the server device. The contents registered from the device information registration screen 1000 are stored. The update date indicates the date when the device information is updated.

  FIG. 6 is a flowchart showing an example of a main flow in the device management system according to the embodiment of the present invention.

  The processing is started when the device map display 401 is selected in FIG.

  In step S601, the device registered in the client and the MAC address of the device are acquired from the computer name of the client device that accepted the process and the client holding information.

  In step S602, using the computer name acquired in step S601 as a key, “floor” and “floor” to be displayed are specified from the client registration information 1101, and a floor map for display is determined.

  In step S603, the device list to be displayed is acquired from the device registration information 1201 using the specified “floor” and “floor” as keys. Here, the displayed device list indicates devices having the same installation location information as the identified “floor” and “floor”.

  In step S604, the device included in the client holding information 1102 is added to the device list acquired in step S603.

  In step S605, a device list display process is performed. Details will be described with reference to FIG.

  FIG. 7 is a flowchart showing an example of a device list display process in the device management system according to the embodiment of the present invention.

  In step S604 of FIG. 6, the device installation status is displayed based on the created device list.

  In step S701, one device is acquired from the device list. The process is repeated for all devices in this device list.

  In step S702, device information with the latest update date is acquired from the device registration information 1201 using the device name of the target device as a key.

  In step S703, it is determined whether or not the corresponding device information exists. If not, the process proceeds to step S704, where the device icon and the current status are displayed in the unnecessary printer setting field of the device map, and the process proceeds to step S709.

  For example, when the target device is the MFP 220 added from the client holding information 1102, it is not included in the device registration information 1201, so “Not connected” and “Discard” are displayed.

  On the other hand, if there is a corresponding device in step S703, the process proceeds to step S705, where “floor” “floor” set in the device information and “floor” “floor” of the computer name set in the client information are the same. It is determined whether it is installed, that is, whether it is installed in the same place.

  If it is determined in step S705 that the “floor” and “floor” are not the same, the process advances to step S706 to display the device icon and the current status (changed “floor” “floor”) in the unnecessary printer setting field of the device map. Display, and the process proceeds to step S709.

  For example, it is assumed that the target device is PR110xx and the client device is the computer name “KDA117947”. According to the client registration information, it is “24th floor” and “north floor”, and according to the device registration information, PR110xx is “23rd floor” and “south floor”. Therefore, since “floor” and “floor” are not the same, “connected” and “23rd floor south floor” are displayed.

  On the other hand, if “floor” and “floor” are the same in step S705, the process proceeds to step S707, and a device icon is displayed at a position corresponding to the block and seat number in the device map.

  In step S708, difference processing is performed. The difference process indicates a process for displaying the status of the difference when the device driver installed in the client device is different from the current arrangement status. This will be described in detail with reference to FIG.

  In step S709, if it is not determined whether all devices in the device list have been processed, the process returns to step S701 to repeat the processing. If all devices have been processed, the process ends.

  FIG. 8 is a flowchart showing an example of difference processing in the device management system according to the embodiment of the present invention.

  In step S801, the last access date acquired from the client registration information is compared with the latest update date of the corresponding device. If the last access date is newer than the update date, that is, if the device information has not been updated since the last access by the client device, no difference will occur and the processing ends.

  On the other hand, if the update date is newer than the last access date, the process advances to step S802 to determine whether there is a device information having the same device name and having a plurality of update dates. If there are multiple, it can be seen that the setting may have been changed.

  If a plurality of device information does not exist in step S803, there is no difference, and the process ends. On the other hand, when there are a plurality, the difference between the device information registered in the client device and the latest device information is determined from the last access date and the update date.

  For example, in the case of the computer name “KDA 117947” of the client device, since the last access date is “2010/9/20”, when the device is “PR8800”, the state of “2009/8/31” of “No. 7” Is registered. Therefore, the comparison with the state of “2010/11/10” of “No. 6” is performed.

  In step S804, it is determined whether the IP addresses are the same. If they are the same, the process proceeds to step S806. If they are different, in step S805, the fact that the IP address has been changed is displayed near the target device icon. For example, the MFP 222 is applicable.

  In step S806, it is determined whether the device driver versions are the same. If they are the same, the process proceeds to step S808, and if they are different, in step S807, the fact that the version of the device driver has been changed is displayed near the target device icon. For example, the MFP 222 is applicable.

  In step S808, it is determined whether the “floor” and “floor” of the device are the same. If they are the same, the process proceeds to step S810. If they are different, in step S809, the fact that the “floor” or “floor” has been moved is displayed near the target device icon. For example, PR9900 is applicable. (In this example, it is not displayed because of the update date.)

  In step S810, it is determined whether “block” and “seat number” are the same. If they are the same, the process ends.

  On the other hand, if they are different, the process proceeds to step S811, and a device icon is displayed in the “block” and “seat number” installed in the past.

  Next, in step S812, an arrow from the device icon installed in the past to the current device icon is displayed.

  In step S813, the fact that the installation position has been moved is displayed near the current device icon, and the process is terminated.

  As a result, the difference between the device information stored in the client device and the current device information can be displayed, so that the user of the client device can now display the difference when the floor movement or layout change is performed, for example. It is possible to easily change the location of a device that has been used up to now or change the setting of a newly installed device.

  FIG. 13 is a diagram showing an example of a floor map in the device management system according to the embodiment of the present invention.

  It shows the layout of the floor for creating a device map. "Floor", "Floor", "Block", "Seat number", etc. are designated in advance. A floor map corresponding to the target “floor” and “floor” may be prepared.

  The server apparatus creates a device map by adding a device icon and an arrangement state to the floor map.

  FIG. 14 is a flowchart illustrating an example of a driver acquisition process in the device management system according to the embodiment of the present invention.

  The process can be started by clicking the device icon of the device map in which the device driver is registered. For example, a device driver download may be selected by right-clicking the mouse on the MFP 222 in the device map of FIG.

  Steps S1401 to S1403 indicate processing on the client device side, and steps S1404 and S1405 indicate processing on the server device side.

  In step S1401, the client apparatus accesses the server apparatus, and in step S1404, the server creates a device map and performs display control.

  In step S1402, a desired device driver can be downloaded by operating a device map icon displayed on the client. The download destination is a storage destination stored in the device registration information 1201.

  The server apparatus that has received the download request from the client in step S1405 transmits a device driver to the client, and receives the device driver in step S1403.

  FIG. 15 is a flowchart showing an example of driver installation processing in the device management system according to the embodiment of the present invention.

  In step S1501, the device driver installer acquired in FIG. 14 is executed, and in step S1502, the driver is installed.

  In step S1503, device information corresponding to the installed device driver is stored in the client holding information 1102 of the client apparatus. The device information is a device name or a MAC address, and is not limited to this as long as it is a device-specific item.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The program according to the present invention is a program that can be executed by a computer according to the processing method of the flowchart shown in the present invention. The storage medium according to the present invention stores a program that can be executed by a computer. The program in the present invention may be a program for each processing method of each device.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by executing the reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk, solid state drive, or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention.

  In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

201 CPU
202 RAM
203 Program ROM
204 Data ROM
205 KBC
206 DC
207 MC
208 UBS I / F
220 NW I / F

Claims (7)

A server device capable of communicating with a device connected to a network and a client device capable of installing a device driver for using the device;
Client information storage means for storing a setting state including installation location information of the client device;
Device information storage means for storing a setting state including installation location information of the device;
Device identification means for identifying a device in which the installation location information of the client device and the same installation location information are stored;
Device map generating means for generating a device map displayed on the seating chart corresponding to the installation location information by the device specified by the device specifying means;
An installation device specifying unit capable of specifying a device corresponding to a device driver installed in the client device;
If the device setting state specified by the installation device specifying unit is different from the device setting state stored in the device information storage unit, the device map generation unit controls display on the device map. And a server device.   When the device installed on the client device is moved within the same device map, the device map generation means displays the device at the location where it was previously installed and is displayed at the current location. The server apparatus according to claim 1, wherein display control is performed on a mark indicating that the device has moved relative to the device.   3. The device map generation means, when a device installed in the client device is an installation location that is not displayed on the same device map, controls display of the device as a deletion target. Server device.   4. The device according to claim 1, further comprising: a driver providing unit that provides a device driver of the changed version when the version of the device driver of the device displayed in the device map is changed. The server device according to item. A client information storage means capable of communicating with a device connected to a network and a client device capable of installing a device driver for using the device, and storing a setting state including installation location information of the client device; A control method of a server apparatus having device information storage means for storing a setting state including device installation location information,
A device specifying step for specifying a device in which the installation location information of the client device and the same installation location information are stored;
A device map generating step in which the device specified by the device specifying step generates a device map displayed on a seating chart corresponding to the installation location information;
An installation device specifying step capable of specifying a device corresponding to a device driver installed in the client device;
In the device map generation step, if the setting state of the device specified in the installation device specifying step is different from the setting state of the device stored in the device information storage means, the fact is displayed on the device map. A control method for a server device. A client information storage means capable of communicating with a device connected to a network and a client device capable of installing a device driver for using the device, and storing a setting state including installation location information of the client device; A server device having device information storage means for storing a setting state including device installation location information,
Device identification means for identifying a device in which the installation location information of the client device and the same installation location information are stored;
Device map generating means for generating a device map displayed on the seating chart corresponding to the installation location information by the device specified by the device specifying means;
An installation device specifying unit capable of specifying a device corresponding to a device driver installed in the client device;
If the device setting state specified by the installation device specifying unit is different from the device setting state stored in the device information storage unit, the device map generation unit controls display on the device map. A program for causing a server device to function.   A recording medium on which the program according to claim 6 is recorded.

Images