Information processing device, server device, peripheral device management method, and program
Abstract
Problem to be solved.To manage a peripheral device which is not directly connected to a network so as to be able to communicate directly with a server device by the server device.
Solution.A user terminal 1 communicatively connected to a server device 2 via a network 9 acquires terminal information including a terminal ID of the user terminal 1, and what is a network interface 16 to which the network 9 is connected? Information acquisition unit 101 that acquires peripheral device information including the device type and serial number of peripheral device 3 connected to user terminal 1 via different peripheral device connection interfaces 15, and server device 2 that acquires terminal information and peripheral device information. It is equipped with a transmission / reception unit 102 for transmitting to. [Selection diagram] Fig. 2

Term
3.5 yearsto projected expiry
Projected expiry 19 March 2030, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
14 claims: 6 independent, 8 dependent
- 1ネットワークを介してサーバ装置と通信可能に接続される情報処理装置であって、 該情報処理装置を識別可能な情報を含む、該情報処理装置に関連する端末情報を取得する端末情報取得手段と、 前記ネットワークが接続されている通信インターフェースとは異なる周辺装置接続用インターフェースを介して該情報処理装置に接続される周辺装置を識別可能な情報を含む、該周辺装置に関連する周辺装置情報を取得する周辺装置情報取得手段と、 前記端末情報および前記周辺装置情報を前記サーバ装置に送信する送信手段と、 を備える情報処理装置。
- 2前記周辺装置が該情報処理装置に対して接続または切断されたことを検出する接続状況検出手段と、 検出された接続または切断に係る日時情報を含む、該接続または該切断に関連する接続情報を取得する接続情報取得手段と、を更に備え、 前記周辺装置情報取得手段は、前記接続状況検出手段による接続または切断の検出を受けて、該接続または該切断に係る周辺装置に関連する周辺装置情報を取得し、 前記送信手段は、前記接続状況検出手段による接続または切断の検出を受けて、前記端末情報、前記周辺装置情報および前記接続情報を前記サーバ装置に送信する、 請求項1に記載の情報処理装置。
- 3ネットワークを介して通信可能に接続される情報処理装置から送信された、該情報処理装置を識別可能な情報を含む端末情報と、該ネットワークが接続されている通信インターフェースとは異なる周辺装置接続用インターフェースを介して該情報処理装置に接続されている周辺装置を識別可能な情報を含む周辺装置情報と、を受信する受信手段と、 前記端末情報および前記周辺装置情報を、情報の送信元である前記情報処理装置を識別可能な情報および前記周辺装置を識別可能な情報に関連づけて蓄積する情報蓄積手段と、 を備えるサーバ装置。
- 4前記受信手段は、前記情報処理装置から送信された、該情報処理装置において検出された周辺装置の接続または切断に係る日時情報を含む接続情報を更に受信し、 前記情報蓄積手段は、前記接続情報を、前記接続または前記切断に係る前記情報処理装置を識別可能な情報および前記周辺装置を識別可能な情報に関連づけて蓄積する、 請求項3に記載のサーバ装置。
- 5前記周辺装置を識別可能な情報を用いて、前記情報蓄積手段によって蓄積された前記接続情報を検索することで、該周辺装置の、情報処理装置に対する接続および切断の履歴を抽出し、該周辺装置が1の情報処理装置から切断され他の情報処理装置に接続されて移動したことを検出する移動検出手段を更に備える、 請求項4に記載のサーバ装置。
- 6前記受信手段は、前記情報処理装置から送信された、該情報処理装置に接続された周辺装置の起動状態を更に受信し、 前記受信手段によって受信された前記接続情報に基づいて、前記情報蓄積手段によって蓄積されている前記周辺装置情報を、該周辺装置情報に係る周辺装置が情報処理装置に接続されているか否かを判定可能に更新する情報更新手段と、 前記起動状態および前記周辺装置情報を参照することで、起動されていない周辺装置および情報処理装置に接続されていない周辺装置を検出する未使用周辺装置検出手段と、を更に備える、 請求項4または5に記載のサーバ装置。
- 7指定日時の入力を受け付ける入力受付手段と、 前記情報蓄積手段によって蓄積された前記接続情報から、接続に係る日時が前記指定日以前であり、且つ切断に係る日時が前記指定日以降または未記録である接続情報を抽出することで、前記指定日時に何れかの情報処理装置に接続されていた周辺装置を抽出する周辺装置抽出手段と、 を更に備える、請求項4から6の何れか一項に記載のサーバ装置。
- 8前記受信手段は、前記情報処理装置から送信された、該情報処理装置において発生したイベントのイベントログを更に受信し、 前記情報蓄積手段は、前記イベントログを、前記イベントに係る前記情報処理装置を識別可能な情報および該イベントに係る前記周辺装置を識別可能な情報に関連づけて更に蓄積し、 前記情報蓄積手段によって蓄積された前記イベントログを、所定の周辺装置を識別可能な情報を用いて検索することで、該周辺装置に係るイベントログを抽出するイベントログ抽出手段を更に備える、 請求項4から7の何れか一項に記載のサーバ装置。
- 9前記移動検出手段によって、所定の周辺装置が1の情報処理装置から切断され他の情報処理装置に接続されて移動していることが検出されている場合に、前記イベントログ抽出手段によって抽出された該所定の周辺装置に係るイベントログの内容に、前記移動の前後で変化があったか否かを判断することで、イベントの発生原因を推定する推定手段を更に備える、 請求項8に記載のサーバ装置。
- 10前記受信手段は、前記情報処理装置から送信された、該情報処理装置に接続された周辺装置にインストールされているソフトウェアの情報、および該情報処理装置にインストールされている該周辺装置関連のソフトウェアの情報、を含むソフトウェア情報を更に受信し、 前記情報処理装置および前記周辺装置にインストールされているソフトウェア間の対応関係を判断するための対応関係情報を保持する対応関係情報保持手段と、 前記受信手段によって受信されたソフトウェアの情報に基づいて前記対応関係情報を参照することで、前記情報処理装置および前記周辺装置にインストールされているソフトウェアが所定の対応関係を有しているか否かを判断する対応関係判断手段と、 前記情報処理装置および前記周辺装置にインストールされているソフトウェアが前記所定の対応関係を有していないと判断された場合に、該所定の対応関係を満たすために必要なソフトウェアの変更要求を、前記情報処理装置に対して送信する要求送信手段と、 を更に備える、請求項3から9の何れか一項に記載のサーバ装置。
- 11ネットワークを介してサーバ装置と通信可能に接続されるコンピュータが、 該コンピュータを識別可能な情報を含む、該コンピュータに関連する端末情報を取得する端末情報取得ステップと、 前記ネットワークが接続されている通信インターフェースとは異なる周辺装置接続用インターフェースを介して該コンピュータに接続される周辺装置を識別可能な情報を含む、該周辺装置に関連する周辺装置情報を取得する周辺装置情報取得ステップと、 前記端末情報および前記周辺装置情報を前記サーバ装置に送信する送信ステップと、 を実行する周辺装置管理方法。
- 12サーバ装置としてのコンピュータが、 ネットワークを介して通信可能に接続されるユーザ端末から送信された、該ユーザ端末を識別可能な情報を含む端末情報と、該ネットワークが接続されている通信インターフェースとは異なる周辺装置接続用インターフェースを介して該ユーザ端末に接続されている周辺装置を識別可能な情報を含む周辺装置情報と、を受信する受信ステップと、 前記端末情報および前記周辺装置情報を、情報の送信元である前記ユーザ端末を識別可能な情報および前記周辺装置を識別可能な情報に関連づけて蓄積する情報蓄積ステップと、 を実行する周辺装置管理方法。
- 13ネットワークを介してサーバ装置と通信可能に接続されるコンピュータを、 該コンピュータを識別可能な情報を含む、該コンピュータに関連する端末情報を取得する端末情報取得手段と、 前記ネットワークが接続されている通信インターフェースとは異なる周辺装置接続用インターフェースを介して該コンピュータに接続される周辺装置を識別可能な情報を含む、該周辺装置に関連する周辺装置情報を取得する周辺装置情報取得手段と、 前記端末情報および前記周辺装置情報を前記サーバ装置に送信する送信手段と、 として機能させるための周辺装置管理用プログラム。
- 14コンピュータを、 ネットワークを介して通信可能に接続されるユーザ端末から送信された、該ユーザ端末を識別可能な情報を含む端末情報と、該ネットワークが接続されている通信インターフェースとは異なる周辺装置接続用インターフェースを介して該ユーザ端末に接続されている周辺装置を識別可能な情報を含む周辺装置情報と、を受信する受信手段と、 前記端末情報および前記周辺装置情報を、情報の送信元である前記ユーザ端末を識別可能な情報および前記周辺装置を識別可能な情報に関連づけて蓄積する情報蓄積手段と、 として機能させるための周辺装置管理用プログラム。
Independent claims14
116 paragraphs, as filed
The present invention relates to the management of peripheral devices connected to an information processing device.
In a system consisting of peripheral devices connected to a network, a server, and a personal computer, when downloading resources, two types of addresses, a device-specific address such as a MAC address and an address that can be set by the user such as an IP address, are used. It is managed on the server together with the resources to be downloaded, and by comparing the MAC address and network address of the peripheral devices on the network with the information managed on the server on a regular basis, the peripheral devices can be moved and exchanged. There is a technique for automatically determining the value (see Patent Document 1).
<p><patcit num="1"><text>Japanese Unexamined Patent Publication No. 2002-108734</text></patcit></p>
<p> Conventionally, there is a technique of collecting terminal information and event logs using agent software installed on a managed terminal and notifying the server device, and centrally managing the terminals by the server device.</p><p> However, in the conventional technology, terminals (including devices such as printers and scanners) directly connected to the network capable of communicating with the server device can be managed by the server device, but the terminal is not directly connected to the network. Manage peripheral devices connected to various peripheral device connection interfaces such as USB (Universal Serial Bus), SCSI (Small Computer System Interface), and IEEE (The Institute of Electrical and Electronics Engineers, Inc.) standards. I couldn't.</p><p> In view of the above problems, it is an object of the present invention to manage peripheral devices that are not directly connected to the network so as to be able to communicate directly with the server device by the server device.</p>
<p> In the present invention, the following means are adopted in order to solve the above problems. That is, the present invention is an information processing device communicably connected to a server device via a network, and acquires terminal information related to the information processing device, including information that can identify the information processing device. Related to the peripheral device, which includes information that can identify the terminal information acquisition means and the peripheral device connected to the information processing device via a peripheral device connection interface different from the communication interface to which the network is connected. It is an information processing device including a peripheral device information acquisition means for acquiring peripheral device information and a transmission means for transmitting the terminal information and the peripheral device information to the server device.</p><p> The information processing device according to the present invention is for connecting a peripheral device different from an interface (for example, a wired or wireless LAN interface or a WAN interface) to which a network that mediates communication between a server device and the information processing device is connected. Peripheral devices that cannot be managed directly from the server device because they are connected to the interface can also be managed by the server device by acquiring information on the information processing device side and sending it to the server device. It makes sense. The peripheral device connection interface referred to here includes, for example, various peripheral device connection interfaces such as USB, SCSI, and IEEE standards.</p><p> In addition, the information processing device according to the present invention includes a connection status detecting means for detecting that the peripheral device is connected or disconnected from the information processing device, and date and time information related to the detected connection or disconnection. The peripheral device information acquisition means further includes connection information acquisition means for acquiring connection information related to the connection or disconnection, and the peripheral device information acquisition means receives detection of connection or disconnection by the connection status detection means and receives the connection or disconnection. The peripheral device information related to the peripheral device related to the disconnection is acquired, and the transmission means receives the detection of the connection or disconnection by the connection status detecting means and transmits the terminal information, the peripheral device information, and the connection information to the server. It may be sent to the device.</p><p> According to the present invention, by detecting the connection or disconnection of the peripheral device to the information processing device and sequentially transmitting the connection information related to the detection to the server device, the management database of the peripheral device managed by the server device is updated. Can be kept at. In addition, the connection information includes date and time information related to connection or disconnection. Therefore, the date and time when the peripheral device is connected to or disconnected from the information processing device can be recorded as a history.</p><p> Further, the present invention may be grasped as a server device for managing the information processing device as described above. That is, in the present invention, the terminal information including the information that can identify the information processing device transmitted from the information processing device that is communicably connected via the network and the communication interface to which the network is connected are defined. Information on receiving means for receiving peripheral device information including information that can identify peripheral devices connected to the information processing device via different peripheral device connection interfaces, terminal information, and peripheral device information. It is a server device including information that can identify the information processing device that is the source of the information processing and information storage means that stores the peripheral device in association with the identifiable information.</p><p> The server device according to the present invention receives and stores information transmitted from the information processing device side even for peripheral devices that cannot be directly managed from the server device because it is not connected to a network capable of direct communication. Peripheral devices can be managed by the server device.</p><p> Further, in the present invention, the receiving means further receives the connection information including the date and time information related to the connection or disconnection of the peripheral device detected in the information processing device, which is transmitted from the information processing device. The storage means may store the connection information in association with information that can identify the information processing device related to the connection or disconnection and information that can identify the peripheral device.</p><p> According to the present invention, the management database of the peripheral device managed by the server device can be kept up-to-date by sequentially receiving the connection information related to the connection or disconnection of the peripheral device to the information processing device from the information processing device. .. Further, since the connection information includes the date and time information related to the connection or disconnection, the date and time when the peripheral device is connected or disconnected from the information processing device can be recorded as a history.</p><p> Further, the server device according to the present invention uses information that can identify the peripheral device to search for the connection information accumulated by the information storage means, thereby connecting the peripheral device to the information processing device and A movement detecting means for extracting the disconnection history and detecting that the peripheral device is disconnected from one information processing device and connected to another information processing device to move may be further provided.</p><p> By providing the movement detecting means as described above, according to the present invention, the administrator or the user can immediately grasp that the peripheral device has moved. The movement detection means is, for example, The latest connection information related to the peripheral device is the connection information indicating the connection to the information processing device, and the connection information related to this peripheral device is the connection information indicating that the device was previously connected to another information processing device. Is present, it can be detected that the peripheral device has moved.</p><p> Further, in the present invention, the receiving means further receives the activated state of the peripheral device connected to the information processing device transmitted from the information processing device, and the server device receives the received by the receiving means. An information updating means for updating the peripheral device information accumulated by the information storage means based on the connection information so that it can be determined whether or not the peripheral device related to the peripheral device information is connected to the information processing device. , An unused peripheral device detecting means for detecting a peripheral device that has not been started and a peripheral device that is not connected to the information processing device by referring to the activated state and the peripheral device information.</p><p> By detecting unused peripherals, the administrator can instantly identify peripherals that are not currently in use, extract idle assets, or connect to an information processing device but are not in use. Can be considered to be moved to another information processing device.</p><p> Further, the server device according to the present invention is related to disconnection when the date and time related to the connection is before the designated date and from the input receiving means for receiving the input of the designated date and time and the connection information accumulated by the information storage means. Peripheral device extraction means for extracting peripheral devices connected to any information processing device at the designated date and time by extracting connection information whose date and time is after or unrecorded may be further provided. Good.</p><p> By providing the peripheral device extraction means as described above, according to the present invention, the administrator can specify a past date and time and check the connection status of the peripheral device and the information processing device at the designated date and time. ..</p><p> Further, in the present invention, the receiving means further receives an event log of an event generated in the information processing device transmitted from the information processing device, and the information storage means converts the event log into the event. The information processing device is further accumulated in association with the identifiable information and the peripheral device related to the event in association with the identifiable information, and the server device stores the event log accumulated by the information storage means in a predetermined periphery. An event log extraction means for extracting an event log related to the peripheral device may be further provided by searching the device using identifiable information.</p><p> By accumulating and extracting such event logs, the administrator can track the event log of the desired peripheral device even when the peripheral device is moving between a plurality of information processing devices. You can. The event log extraction means extracts the event log related to the information processing device by searching the event log accumulated by the information storage means using information that can identify a predetermined information processing device. You may.</p><p> Further, in the server device according to the present invention, when it is detected by the movement detection means that a predetermined peripheral device is disconnected from one information processing device and connected to another information processing device to move. , Further, an estimation means for estimating the cause of the event by determining whether or not the content of the event log related to the predetermined peripheral device extracted by the event log extraction means has changed before and after the movement. You may prepare.</p><p> By providing such an estimation means, according to the present invention, when an event such as an error occurs in connection with the peripheral device, whether the occurrence of the event is caused by the peripheral device or is connected. It is possible to determine whether the cause is caused by the information processing device that is being used and to estimate the cause of the event.</p><p> Further, in the present invention, the receiving means is the information of the software installed in the peripheral device connected to the information processing device transmitted from the information processing device, and the information of the software installed in the information processing device. Further receiving software information including software information related to the peripheral device, the server device holds the correspondence relationship information for determining the correspondence relationship between the information processing device and the software installed in the peripheral device. By referring to the correspondence information based on the information of the correspondence information holding means and the software received by the receiving means, the information processing device and the software installed in the peripheral device have a predetermined correspondence relationship. When it is determined that the correspondence relationship determination means for determining whether or not the information processing device and the software installed in the information processing device and the peripheral device do not have the predetermined correspondence relationship, the predetermined correspondence relationship is determined. A request transmission means for transmitting a software change request necessary for satisfying the correspondence relationship to the information processing apparatus may be further provided.</p><p> According to the present invention, not only keeping the software up-to-date as in the conventional software update, but also making a plurality of software that need to be compatible for cooperation between a plurality of devices, such as compatibility. It is possible to maintain the correspondence relationship. Further, since the software change request according to the present invention is made for the purpose of maintaining the correspondence such as compatibility, it is not merely a request for software version upgrade, but in some cases, an older version of software may be used. It may be a request for a change in the above, or if the correspondence is lost due to a software update, a process such as suppressing a request for version upgrade may be performed. Regarding security concerns that may arise due to version down requests and suppression of updates, it is preferable to separately deal with security updates by methods such as not performing version downs and not suppressing updates.</p><p> The present invention may also be understood as an invention of a method executed by a computer, an invention of a program, or an invention of a computer-readable recording medium on which such a program is recorded. For example, the present invention includes a terminal information acquisition step in which a computer communicably connected to a server device via a network acquires terminal information related to the computer, including information that can identify the computer, and the network. Peripheral device information acquisition to acquire peripheral device information related to the peripheral device, including information that can identify the peripheral device connected to the computer via a peripheral device connection interface different from the communication interface to which the computer is connected. It is a peripheral device management method that executes a step and a transmission step of transmitting the terminal information and the peripheral device information to the server device.</p>
<p> According to the present invention, even peripheral devices that are not directly connected to the network so as to be able to communicate directly with the server device can be managed by the server device.</p>
<figref num="1">It is a figure which shows the structure of the whole peripheral device management system which concerns on embodiment.</figref><figref num="2">It is a figure which shows the functional structure of the user terminal and the server apparatus which concerns on embodiment.</figref><figref num="3">It is a figure which shows the structure of the terminal table which concerns on embodiment.</figref><figref num="4">It is a figure which shows the structure of the peripheral device table which concerns on embodiment.</figref><figref num="5">It is a figure which shows the structure of the use history table which concerns on embodiment.</figref><figref num="6">It is a figure which shows the structure of the event log table which concerns on embodiment.</figref><figref num="7">It is a figure which shows the structure of the connection information table which concerns on embodiment.</figref><figref num="8">It is a figure which shows the structure of the consumables characteristic table which concerns on embodiment.</figref><figref num="9">It is a figure which shows the structure of the use tendency table which concerns on embodiment.</figref><figref num="10">It is a figure which shows the structure of the software correspondence table which concerns on embodiment.</figref><figref num="11">It is a flowchart which shows the flow of the information collection process which concerns on embodiment.</figref><figref num="12">It is a flowchart which shows the flow of the connection disconnection detection process which concerns on embodiment.</figref><figref num="13">It is a flowchart which shows the flow of the movement determination processing of the peripheral device which concerns on embodiment.</figref><figref num="14">It is a flowchart which shows the flow of the unused peripheral device determination process which concerns on embodiment.</figref><figref num="15">It is a flowchart which shows the flow of the peripheral device configuration trace processing which concerns on embodiment.</figref><figref num="16">It is a flowchart which shows the flow of the event trace processing which concerns on embodiment.</figref><figref num="17">It is a flowchart which shows the flow of the consumables management process which concerns on embodiment.</figref>
Hereinafter, embodiments of the peripheral device management system 100 using the information processing device, server device, method, and program according to the present invention will be described with reference to the drawings. It should be noted that the embodiments described below show an example of the case where the present invention is carried out, and the present invention is not limited to the specific configuration described below. In carrying out the present invention, it is preferable that a specific configuration according to the embodiment is appropriately adopted.
<Structure> FIG. 1 is a diagram showing the configuration of the entire peripheral device management system 100 according to the present embodiment. The peripheral device management system 100 is a system in which a user terminal 1 and a server device 2 are connected via a network 9, and the user terminal 1 is provided with various peripheral device connection interfaces 15 such as USB, SCSI, and IEEE standards. Peripheral devices 3 such as a printer 3b, a scanner 3a, and an external memory 3c are connected via the printer 3b and the scanner 3a. In addition, the network 9 that mediates communication between the server device 2 and the user terminal 1 includes various LANs (Local Area Networks) such as IEEE 802.3 and FDDI (Fiber-Distributed Data Interface), as well as various WANs (Wide Areas). A network of various standards such as Network) may be adopted.
The user terminal 1 and the server device 2 have CPUs (Central Processing Units) 11 and 21, RAMs (Random Access Memory) 12 and 22, ROMs (Read Only Memory) 13 and 23, and a display, mouse, and keyboard. These are computers in which the input / output devices 14 and 24, the network interfaces 16 and 26, and the auxiliary storage devices 19 and 29 are electrically connected. As the auxiliary storage device 19, for example, EEPROM (Electrically Erasable Programmable ROM), HDD (Hard Disk Drive), SSD (Solid State Drive), or the like can be used.
Further, the user terminal 1 is specifically an information processing device used by a user such as a personal computer or a KIOSK terminal, and the peripheral device 3 is connected to the user terminal 1 as described above. The peripheral device connection interface 15 is provided. Here, the peripheral device connection interface 15 is an interface different from the network interface 16 connected to the network 9, and the peripheral device 3 connected to the peripheral device connection interface 15 communicates via the network 9. It is not possible to establish a direct connection with the server device 2 to be performed.
CPUs 11 and 21 are central processing units, and by processing instructions and data expanded in RAM12, 22 and the like, RAM12, 22, auxiliary storage devices 19, 29, input / output devices 14 , 24 etc. are controlled. RAMs 12 and 22 are main storage devices and are controlled by CPUs 11 and 21, and various instructions and data are written and read. Auxiliary storage devices 19 and 29 are non-volatile storage devices, and information to be retained is mainly written and read even when the power of the user terminal 1 or the server device 2 is turned off. The contents input from the input device are recorded in RAMs 12 and 22, and processed by CPUs 11 and 21.
The auxiliary storage devices 19 and 29 include the OS (Operating System) of the user terminal 1 and the server device 2 loaded in the RAMs 12 and 22, and various programs for executing the processes shown in the flowcharts shown in FIGS. 11 and 11 and later. , Various data used by the user terminal 1 or the server device 2 is stored.
FIG. 2 is a diagram showing a functional configuration of the user terminal 1 and the server device 2 according to the present embodiment. In the user terminal 1 according to the present embodiment, the CPU 11 interprets and executes various programs expanded in the RAM 12, so that the information acquisition unit 101, the transmission / reception unit 102, the connection status detection unit 103, and the limit value calculation unit It functions as an information processing device according to the present invention, which includes 104, a usage tendency calculation unit 105, a threshold value calculation unit 106, a comparison unit 107, and a notification output unit 108. Each of these functional units executes a function corresponding to each means provided in the information processing apparatus according to the present invention. Further, in the present embodiment, an example in which all of these functions are executed by the general-purpose CPU 11 is described, but some or all of these functions are realized by one or more dedicated processors. You may.
The information acquisition unit 101 periodically or receives the detection of the connection or disconnection of the peripheral device 3 by the connection status detection unit 103, and the terminal related to the user terminal 1 and the peripheral device 3 connected to the user terminal 1. Information (terminal ID, related application information, driver information, power status), event log information (event occurrence date and time, message), peripheral device information (device type, serial number, firmware information, power status, consumable usage), Acquire various information such as connection detection information (including connection date and time or disconnection date and time).
The acquired information is transmitted to the server device 2 by the transmission / reception unit 102 described later, but is also stored in the database built on the auxiliary storage device 19 in the user terminal 1. The user terminal 1 transfers the acquired information to a peripheral device table, a usage history table, an event log table, a connection information table, a consumables characteristic table, a usage tendency table, etc. in a local database different from the database of the server device 2. save. The information acquisition unit 101 calculates the cumulative usage amount for each consumable item by accumulating the acquired consumable item usage amount for each consumable item, and stores it in the peripheral device table held in the user terminal 1. To do.
The transmission / reception unit 102 transmits various information such as terminal information, peripheral device information, event log information, connection information, etc. acquired by the information acquisition unit 101 to the server device 2, and is transmitted from the server device 2 of the software. Receive change requests, etc.
The connection status detection unit 103 detects that the peripheral device 3 is connected or disconnected from the user terminal 1. Specifically, it detects that the peripheral device 3 is connected or disconnected from the user terminal 1 by receiving the notification of the connection or disconnection event of the peripheral device 3 notified from the OS or driver of the user terminal 1. To do. However, other detection methods such as a method of detecting that the peripheral device 3 is connected or disconnected from the user terminal 1 by directly monitoring the peripheral device connection interface 15 by the connection state detection unit 103 itself are adopted. May be done.
The limit value calculation unit 104 calculates the limit value of the estimated usage amount for the consumables based on the cumulative usage amount of the consumables at the occurrence date and time of the event related to the event log including the contents related to the consumables. More specifically, the limit value calculation unit 104 is a consumable item at the date and time when the event occurs. The cumulative usage of is determined as the limit value as it is, or the average of the cumulative usage of consumables at the time of occurrence of the event and one or more limit values calculated in the past is newly estimated usage. Calculated as the limit value of the amount.
The usage tendency calculation unit 105 calculates the usage amount of the consumables per unit time as the usage tendency of the consumables by dividing the cumulative usage amount by the usage period of the consumables. More specifically, the usage tendency calculation unit 105 uses the time from the connection date and time to the disconnection date and time or from the connection date and time to the current date and time included in the connection information as the usage period of the consumable, and the unit time of the consumable. Calculate the amount used per unit.
The threshold value calculation unit 106 calculates a threshold value for determining the output timing of the replacement replenishment reminder notification by comparing with the current cumulative usage amount based on the usage tendency and the limit value of the consumables. More specifically, the threshold value calculation unit 106 calculates the threshold value by subtracting the value obtained by multiplying the amount of consumables used per unit time by the period required for replacement and replenishment of consumables from the limit value.
The comparison unit 107 compares the cumulative usage with the threshold value periodically or at the timing when the cumulative usage is updated. Then, the notification output unit 108 outputs a replacement / replenishment reminder notification of consumables when the cumulative usage amount exceeds the threshold value as a result of the comparison by the comparison unit 107.
Further, in the server device 2 according to the present embodiment, the CPU 21 interprets and executes various programs expanded in the RAM 22, and the transmission / reception unit 201, the information storage unit 202, the movement detection unit 203, and the information update unit 204, unused peripheral device detection unit 205, peripheral device extraction unit 206, event log extraction unit 207, estimation unit 208, correspondence information holding unit 209, correspondence relationship judgment unit 210, and request transmission unit 211. And, it functions as a server device 2 including an input receiving unit 212. Each of these functional units executes a function corresponding to each means provided in the server device 2 according to the present invention. Further, in the present embodiment, an example in which all of these functions are executed by a general-purpose CPU 21 is described, but some or all of these functions are realized by one or more dedicated processors. You may.
The transmission / reception unit 201 includes terminal information (terminal ID, related application information, driver information, power status), event log information (event occurrence date / time, message), peripheral device information (device type, serial number, etc.) transmitted from user terminal 1. Receives various information such as firmware information, power status), connection detection information (including connection date and time or disconnection date and time).
The information storage unit 202 stores various information such as terminal information, peripheral device information, event log information, and connection information received by the transmission / reception unit 201 in association with the terminal ID of the user terminal 1 and the serial number of the peripheral device 3. .. Here, the information storage unit 202 classifies and stores various received information into various tables such as a connection information table described later.
The movement detection unit 203 extracts the connection and disconnection history of the peripheral device 3 by searching the connection information table using the serial number of the peripheral device 3, and the peripheral device 3 is disconnected from the user terminal of 1 and another. Detects that it is connected to the user terminal and moved. Further, the information updating unit 204 updates the contents of the peripheral device table based on the connection information received by the transmitting / receiving unit 201.
The unused peripheral device detection unit 205 refers to the power status, connection date and time, and disconnection date and time of the terminal table and the peripheral device table to detect the peripheral device 3 that has not been started and the peripheral device 3 that is not connected to the user terminal 1. To detect. Further, the input receiving unit 212 receives the input of the designated date and time by the administrator or the user via the input / output devices 14 and 24.
The peripheral device extraction unit 206 is connected to the user terminal 1 at the specified date and time by extracting the connection information from the connection information table whose connection date and time is before the specified date and the disconnection date and time is after the specified date or is NULL. Extract peripheral device 3. Further, the event log extraction unit 207 extracts the event log related to the corresponding peripheral device 3 by searching the event log table using the serial number of the peripheral device 3.
In this embodiment, various information included in the records stored in the table described later, such as the connection date and time and the disconnection date and time, is initialized with NULL. Therefore, in the present embodiment, it can be determined whether or not the corresponding information (disconnection date and time, etc.) has not been detected or input based on whether or not the information is NULL. However, various information contained in the table record may be initialized with other predetermined values (for example, a value indicating that the information has not been detected or input), and the information has not been detected or input. , The determination may be made based on the predetermined value.
The estimation unit 208 is extracted by the event log extraction unit 207 when the movement detection unit 203 detects that the peripheral device 3 is disconnected from the user terminal of 1 and is connected to another user terminal to move. The cause of an event such as an error is estimated by determining whether or not the contents of the event log have changed before and after the movement.
The correspondence information holding unit 209 holds a software correspondence table for determining the correspondence between the driver installed in the user terminal 1, the related application, and the firmware installed in the peripheral device 3.
The correspondence relationship determination unit 210 determines the driver installed in the user terminal 1, the related application, and the firmware installed in the peripheral device 3 by referring to the software correspondence table based on the received software information. Judge whether or not they have a correspondence relationship.
The request transmission unit 211 has determined that the driver installed in the user terminal 1, the related application, and the firmware installed in the peripheral device 3 do not have the predetermined correspondence relationship specified in the software compatibility table. In this case, a software change request necessary for satisfying this predetermined correspondence is transmitted to the user terminal 1.
<Data structure> The server device 2 and the user terminal 1 each hold information used in various processes executed in the peripheral device management system 100. Here, various kinds of information to be held are recorded in various tables described below. Further, among the various tables described below, the peripheral device table, the usage history table, the event log table, the connection information table, the consumables characteristic table, and the usage tendency table are also held on the user terminal 1 side. However, the table held in the user terminal 1 does not hold information (terminal ID, etc.) related to the other user terminal 1.
FIG. 3 is a diagram showing a configuration of a terminal table according to the present embodiment. In the terminal table, the terminal ID, the device type of the peripheral device 3, the serial number of the peripheral device 3, the driver information of the peripheral device 3, the related application information related to the peripheral device 3, and the power supply status of the user terminal 1 are recorded. Here, the terminal ID is information that can uniquely identify the user terminal 1 in at least the network 9 managed by the server device 2. As the terminal ID, for example, a terminal name set so as not to be duplicated in the network 9, a MAC address of the user terminal 1, and the like can be used.
The device type is information indicating the type of the peripheral device 3 connected to the user terminal 1. In the present embodiment, the device types are classified according to their main functions, and as the device type, information that can determine whether the peripheral device 3 is a printer 3b, a scanner 3a, an external memory 3c, or the like is acquired. To. Further, the serial number of the peripheral device 3 is acquired to identify the peripheral device 3.
The driver information is information related to a program (driver) installed in the user terminal 1 to control the peripheral device 3 from the user terminal 1 and executed by the user terminal 1. In the present embodiment, the driver information includes driver version information.
The related application information is information related to an application related to the peripheral device 3. Related applications include applications for performing processing using the functions realized by the peripheral device 3 and processing using the input / output results of the peripheral device 3. In the present embodiment, the related application information includes the version information of the application related to the function of the peripheral device 3.
FIG. 4 is a diagram showing a configuration of a peripheral device table according to the present embodiment. In the peripheral device table, the device type, serial number, firmware information of peripheral device 3, power status of peripheral device 3, consumable name, cumulative usage of consumables, and output time of replacement replenishment reminder notification of consumables are determined. The threshold for is recorded.
Here, the firmware information is information related to the firmware applied to the peripheral device 3. In the present embodiment, the firmware information includes the version information of the firmware applied to the peripheral device 3. The information that overlaps with the information recorded in the terminal table described with reference to FIG. 3 will be omitted.
Further, in the peripheral device table, the names of consumables used in the peripheral device 3 and the cumulative usage amount are accumulated for each table record related to the peripheral device 3. Therefore, when the peripheral device consumables information is received, the cumulative usage amount in the peripheral device table is accumulated by adding the usage amount included in the peripheral device consumables information to the currently held cumulative usage amount. To. If the cumulative usage is reset at the timing of replacement or replenishment of consumables, it will be added every time peripheral device consumables information is received until the next reset, so that the consumables will be replenished. Keep the total usage.
FIG. 5 is a diagram showing a configuration of a usage history table according to the present embodiment. In the usage history table, the device type, serial number, consumable name, consumable usage amount, connection date and time of peripheral device 3, and disconnection date and time of peripheral device 3 are recorded. Further, every time the peripheral device 3 is connected or disconnected, a new record recording the usage amount of consumables is added to the usage history table together with information indicating the connection date and time and the disconnection date and time. That is, the usage amount of consumables is accumulated in the usage history table for each connection period of the peripheral device 3. This makes it possible to grasp the period during which the peripheral device 3 is connected to the user terminal 1, the amount of consumables used during this period, and the like.
FIG. 6 is a diagram showing a configuration of an event log table according to the present embodiment. In the event log table, the date and time when the event (including errors, etc. in addition to normal processing) occurred, the terminal ID of the terminal where the event occurred, the device type of the peripheral device 3 related to the occurrence of the event, the serial number, and the event that occurred. Event log information including the names of consumables related to the event, messages related to the event (contents of the event), etc. is recorded.
FIG. 7 is a diagram showing a configuration of a connection information table according to the present embodiment. In the connection information table, the terminal ID of the user terminal 1 related to the detected connection or disconnection, the detected connection or The device type, serial number, connection date and time, and disconnection date and time of the peripheral device 3 related to the disconnection are recorded.
FIG. 8 is a diagram showing a configuration of a consumables characteristic table according to the present embodiment. In the consumables characteristic table, the device type, serial number, consumable name, and consumable usage limit value (maximum amount of consumables that can be used) of the peripheral device 3 in which the consumable is used are recorded.
FIG. 9 is a diagram showing a configuration of a usage tendency table according to the present embodiment. In the usage tendency table, the device type, serial number, consumable name, and usage amount of the consumables per unit time as the usage tendency of the peripheral device 3 in which the consumables are used are recorded.
FIG. 10 is a diagram showing the structure of the software correspondence table according to the present embodiment. The software correspondence table records the combination of the driver installed on the user terminal 1 having a predetermined correspondence (generally compatibility), the related application, and the firmware installed on the peripheral device 3. There is.
<Processing details> Hereinafter, the flow of processing for managing peripheral devices according to this embodiment will be described with reference to FIGS. 11 to 17. Prior to the process described below, the server device 2 provides the user terminal 1 connected to the network 9 with a peripheral device management program for monitoring the peripheral device 3 connected to the user terminal 1. To deliver. The user terminal 1 executes the peripheral device management program distributed by the server device 2 and makes it resident in the RAM 12 while the user terminal 1 is running. In the present embodiment, the peripheral device management program includes a consumables management program.
FIG. 11 is a flowchart showing the flow of the information collection process according to the present embodiment. The processing shown in this flowchart is periodically executed by the peripheral device management software resident in the user terminal 1, or triggered by the user terminal 1 detecting the connection or disconnection of the peripheral device 3. Is executed as. The specific contents and order of the processes shown in this flowchart are examples, and it is preferable that the processing contents and order suitable for the embodiment are appropriately adopted.
In steps S101 and S102, various information is collected in the user terminal 1, and the collected information is transmitted to the server device 2. The information acquisition unit 101 of the user terminal 1 monitors the connection status of the connected peripheral device 3, and when the peripheral device 3 connected to the user terminal 1 is detected, the terminal information to which the peripheral device 3 is connected is detected. (Terminal ID, related application information, driver information, power status of user terminal 1), event log information (event occurrence date and time, message), and peripheral device information (device type, serial number, firmware information, power status of peripheral device 3) ) Etc. (step S101), and the transmission / reception unit 102 transmits the collected information to the server device 2 (step S102). This information can be obtained from the peripheral device 3 and the driver management function provided in the OS of the user terminal 1. However, instead of the method of acquiring from the OS or the like, a method of acquiring such information by directly inquiring the peripheral device 3 from the peripheral device management software may be adopted.
The collected information is also held in the peripheral device table, usage history table, event log table, connection information table, consumables characteristic table, and usage tendency table held by the user terminal 1. Each time the information is collected, the user terminal 1 compares the previously collected information held in each local table with the newly collected information, and if there is a difference or the content of the information The collected information may be transmitted to the server device 2 only when there is a change.
In steps S103 and S104, the information collected by the user terminal 1 is received and stored in the database. The transmission / reception unit 201 of the server device 2 receives the terminal information, the event log information, the peripheral device information, and the like transmitted by the user terminal 1 (step S103), and the information storage unit 202 associates the received information with each other. Accumulate in the database (step S104). More specifically, the server device 2 stores the terminal information in the terminal table, the event log in the event log table, and the peripheral device information in the peripheral device table. Further, in the terminal table, the device type and serial number of the peripheral device 3 connected to the corresponding user terminal 1 are stored in association with the terminal ID. In the present embodiment, by treating the device type and serial number stored in the terminal ID as an external key of the peripheral device table, the user terminal 1 recorded in the terminal table in the database and the user terminal 1 are connected to the user terminal 1. It is possible to associate with the peripheral device information related to the peripheral device 3 that is installed. Further, in the event log table, the terminal ID of the user terminal 1 related to the event, the device type of the peripheral device 3, and the serial number are recorded in order to associate the user terminal 1 and the peripheral device 3 related to the event with the event log.
FIG. 12 is a flowchart showing the flow of the connection disconnection detection process according to the present embodiment. The processing shown in this flowchart is periodically executed by the peripheral device management software resident in the user terminal 1, or triggered by the user terminal 1 detecting the connection or disconnection of the peripheral device 3. Is executed as. The specific contents and order of the processes shown in this flowchart are examples, and it is preferable that the processing contents and order suitable for the embodiment are appropriately adopted.
In steps S201 to S203, the connection or disconnection of the peripheral device 3 is detected, various information is collected, and the collected information is transmitted to the server device 2. The connection status detection unit 103 of the user terminal 1 receives a notification of a connection or disconnection event of the peripheral device 3 notified from the OS or driver of the user terminal 1, or monitors the status of the peripheral device connection interface 15. Detects the connection or disconnection of peripheral device 3 (step S201). When the connection or disconnection is detected, the information acquisition unit 101 of the user terminal 1 triggers the detection of the connection or disconnection, and triggers the device type and serial number of the peripheral device 3 related to the connection or disconnection, and the connection date and time or The connection detection information including the disconnection date and time and the terminal ID are acquired (step S202), and the transmission / reception unit 102 transmits the acquired information to the server device 2 (step S203). After that, the process proceeds to step S204.
In step S204 and step S205, the information collected by the user terminal 1 is received and stored in the database. The transmission / reception unit 201 of the server device 2 receives the device type, serial number, connection detection information, and terminal ID (hereinafter, these information are collectively referred to as connection information) transmitted by the user terminal 1 (step S204). ), The information storage unit 202 stores the received information in the database in association with each other (step S205). More specifically, the information storage unit 202 stores the terminal ID, device type, serial number, and connection detection information (connection date / time or disconnection date / time) in the connection information table.
However, if the information included in the received connection detection information is the disconnection date and time, the server device 2 connects the connection information accumulated when the connection of the peripheral device 3 related to the detected disconnection is detected. Identified by searching the information table and extracting records that include the received terminal ID, device type, serial number, and the disconnect date and time is NULL (or a value indicating that the disconnection date and time has not been notified). To do. Then, the information storage unit 202 records the received disconnection date and time in the specified record.
The information storage unit 202 cumulatively (adds) the connection information notified from the user terminal 1. Accumulate in the connection information table. That is, when the same peripheral device 3 is reconnected to a different user terminal 1 and the connection information related to the peripheral device 3 for which the connection information has already been accumulated is received, the information storage unit 202 is the same. A new record is added and the connection information is stored in the connection information table without deleting the record in which the past connection information related to the peripheral device 3 is recorded from the connection information table. According to the present embodiment, by accumulating the connection information, the date and time when the peripheral device 3 is connected to the user terminal 1 and the date and time when the peripheral device 3 is disconnected are recorded as a history, and the peripheral device 3 is connected to the user terminal 1. It is possible to grasp the period that was being done. After that, the process proceeds to step S206.
In step S206, the information of the peripheral device 3 recorded in the terminal table is updated. The information update unit 204 of the server device 2 uses the connection information received in step S204 or the latest connection information extracted from the connection information table to provide information on the terminal table (in this embodiment, the device type and serial). Update the number) to the latest status. Specifically, when the new connection information is information related to the disconnection of the peripheral device 3 (in other words, when the connection detection information is the disconnection date and time), the information update unit 204 is included in the connection information. Using the terminal ID, the record of the user terminal 1 related to the disconnection is specified in the terminal table, and the device type and serial number of the disconnected peripheral device 3 are deleted from the record.
On the other hand, when the new connection information is the information related to the connection of the peripheral device 3 (in other words, when the connection detection information is the connection date and time), the information update unit 204 is included in the connection information. Using the terminal ID, the record of the user terminal 1 related to the connection is specified in the terminal table, and the device type and serial number of the newly connected peripheral device 3 are added to the record. As a result of searching the terminal table using the device type and serial number of the peripheral device 3 related to the connection, the device type and serial number of the peripheral device 3 are recorded in the record of the user terminal 1 that should have already been disconnected. If so, the device type and serial number may be deleted from this record. After that, the process proceeds to step S207.
According to the process shown in this flowchart, the information in the terminal table is updated to the latest state using the connection information, so that the terminal table is immediately updated when the peripheral device 3 is connected or disconnected, and the terminal table is updated. You can keep it up to date.
In steps S207 and S208, version information of various software applied to the user terminal 1 and the peripheral device 3 is acquired, and the correspondence status of the software version is determined. If the new connection information is related to the connection of the peripheral device 3, the server device 2 reads the current firmware version applied to the peripheral device 3 from the peripheral device table, and the peripheral device 3 is currently connected. Read the driver version and related application version installed on user terminal 1 from the terminal table (step S207). Then, the correspondence relationship determination unit 210 of the server device 2 acquires and refers to the software correspondence table from the correspondence information holding unit 209, and various version information read in step S207 is defined in the software correspondence table. It is confirmed whether or not there is a corresponding relationship (step S208). When it is determined that the various version information read in step S207 has the correspondence relationship specified in the software correspondence table, the processing shown in this flowchart ends. If it is determined that there is a combination of software that does not match the correspondence relationship specified in the software correspondence table, the process proceeds to step S209.
In step S209, a software change request is sent. The correspondence relationship determination unit 210 supports software when a combination of the driver version of the user terminal 1, the related application version, and the firmware version of the peripheral device 3 that does not match the correspondence relationship specified in the software correspondence table is included. Refer to the table and cause Identify the software to be used. Then, the request transmission unit 211 of the server device 2 requests the user terminal 1 to change the software that causes the change so that the version correspondence status between the various softwares has the correspondence relationship specified in the software correspondence table. Send. If necessary, the server device 2 holds change software such as updaters for various software in the auxiliary storage device 29 of the server device 2 in advance, and distributes the necessary change software to the user terminal 1. Or you may confirm that the software change process has been completed on the user terminal 1. After that, the process shown in this flowchart ends.
According to the process shown in this flowchart, there is some correspondence such as compatibility between the user terminal 1 and the peripheral device 3 instead of simply keeping the software up-to-date as in the conventional software update. It is possible to maintain necessary software such as drivers, firmware, and related applications in a state in which correspondence such as compatibility is maintained. In addition, since software change requests are made for the purpose of maintaining correspondence such as compatibility, they do not simply request software version upgrades, but in some cases request changes to older versions of software. It may be the one, or if the correspondence is lost due to the software update, processing such as suppressing the request for version upgrade may be performed.
In addition, according to the processing shown in this flowchart, various software such as drivers, firmware, and related applications related to peripheral device 3 are not simply kept up to date, but are compatible by referring to the software compatibility table. You can check for sex and keep it compatible.
FIG. 13 is a flowchart showing the flow of the movement determination process of the peripheral device 3 according to the present embodiment. The processing shown in this flowchart is executed periodically or when information such as connection information is received from the user terminal 1. The specific contents and order of the processes shown in this flowchart are examples, and it is preferable that the processing contents and order suitable for the embodiment are appropriately adopted.
In step S301, peripheral device information is acquired. The server device 2 acquires all peripheral device information from the peripheral device table. After that, the process proceeds to step S302. In the processing of steps S302 to S306 described below, the peripheral devices 3 to be judged are processed for each loop until the judgment processing is completed for all the peripheral devices 3 specified by the device type and the serial number. It is executed repeatedly while changing to.
In steps S302 to S305, it is determined whether or not the peripheral device 3 has been moved by referring to the connection date and time and the disconnection date and time. The movement detection unit 203 of the server device 2 stores a value (date and time) in the connection date and time of the latest connection information table record related to the peripheral device 3 to be judged (not NULL), and the disconnection date and time is Determine if it is NULL (step S302). Further, the movement detection unit 203 determines whether or not there is a connection information table record one before the latest related to the peripheral device 3 to be determined (step S303). If the judgment results in steps S302 and S303 are both positive, that is, the value is stored in the connection date and time of the latest connection information table record, the disconnection date and time is NULL, and one before the latest. If the connection information table record of is present, the process proceeds to step S305. On the other hand, if any one of the above conditions is not satisfied, the process proceeds to step S304.
In step S304, the value is not stored in the connection date and time of the latest connection information table record, the disconnection date and time is not NULL (the value is stored in the disconnection date and time), or the latest value. Executed when the previous connection information table record does not exist. In this case, the movement detection unit 203 is based on the history recorded in the connection information table that the peripheral device 3 to be determined is currently connected to any user terminal 1 and disconnected from the other user terminal 1 in the past. Since it is not possible to read what has been done, it is determined that the peripheral device 3 has not moved. After that, the process proceeds to step S306.
Step S305 is executed when the value is stored in the connection date and time of the latest connection information table record, the disconnection date and time is NULL, and the connection information table record immediately before the latest exists. In this case, the movement detection unit 203 is connected to any user terminal 1 at present and disconnected from the other user terminal 1 in the past from the history recorded in the connection information table. Since it is possible to read that, it is determined that the peripheral device 3 has moved. After that, the process proceeds to step S306.
In step S306, it is determined whether or not the process of determining the presence or absence of movement of all the peripheral devices 3 has been completed. If the determination process is not completed for all the peripheral devices 3, the peripheral device 3 to be determined is changed, and the process proceeds to step S302. When the determination process for all peripheral devices 3 is completed, the process proceeds to step S307. That is, the processes from steps S302 to S306 are repeatedly executed until the determination process is completed for all the peripheral devices 3 recorded in the peripheral device table.
In step S307, the terminal table is updated according to the result of the movement determination. The information update unit 204 updates the information in the terminal table (in the present embodiment, the device type and the serial number) to the latest state by using the latest connection information of the peripheral device 3 determined to have moved in step S305. .. The information update unit 204 identifies the record of the user terminal 1 related to the connection in the terminal table by using the terminal ID included in the connection information, and the device type and serial of the peripheral device 3 determined to have moved to the record. Add a number. As a result of searching the terminal table using the device type and serial number of the peripheral device 3 related to the movement, the device type and serial number of the peripheral device 3 are recorded in the record of the user terminal 1 that should have already been disconnected. If so, the device type and serial number may be deleted from this record. After that, the process shown in this flowchart ends.
According to the process shown in this flowchart, the information in the terminal table is updated to the latest state when the movement of the peripheral device 3 is detected. Therefore, the terminal table is kept up to date, and the administrator can immediately grasp the movement of the peripheral device 3. The result of the movement determination made in steps S302 to S305 may be output as a notification to the administrator, the user, or the like. As for the output method, the optimum output method is appropriately adopted according to the embodiment, such as output to a display, print output, transmission output of e-mail, etc., output to a storage device such as auxiliary storage devices 19 and 29, etc. Is preferable.
FIG. 14 is a flowchart showing the flow of the unused peripheral device determination process according to the present embodiment. The processing shown in this flowchart is executed periodically or when an instruction to start processing from a user or the like is input via an input device or a network 9. The specific contents and order of the processes shown in this flowchart are examples, and it is preferable that the processing contents and order suitable for the embodiment are appropriately adopted.
In step S401, peripheral device information is acquired. The server device 2 acquires all peripheral device information from the peripheral device table. After that, the process proceeds to step S402. In the processing of steps S402 to S408 described below, the peripheral devices 3 to be judged are processed for each loop until the judgment processing is completed for all the peripheral devices 3 specified by the device type and the serial number. It is executed repeatedly while changing to.
In step S402, it is determined whether or not the peripheral device 3 to be determined is connected to any user terminal 1. The unused peripheral device detection unit 205 of the server device 2 searches the terminal table using the device type and serial number related to the peripheral device 3 to be judged, and the peripheral device 3 to be judged is one of them. Determine if it is connected to user terminal 1. If the device type and serial number related to the peripheral device 3 to be judged are retrieved from the terminal table, the process proceeds to step S404. If the device type and serial number related to the peripheral device 3 to be judged are not searched from the terminal table, the process proceeds to step S403.
In step S403, it is determined that the peripheral device 3 to be determined is an unused peripheral device (not connected). If the device type and serial number related to the peripheral device 3 to be judged is not searched from the terminal table in step S402, the unused peripheral device detection unit 205 determines which user terminal 1 is the peripheral device 3 to be judged. It is determined that the peripheral device 3 is not connected to the peripheral device 3 as well, and the peripheral device 3 is determined to be an unused peripheral device (not connected). After that, the process proceeds to step S408.
In step S404, the state of the power supply of the peripheral device 3 to be determined is determined. The unused peripheral device detection unit 205 refers to the value of the power supply state in the peripheral device table record related to the peripheral device 3 to be judged, so that the power supply of the peripheral device 3 is currently ON or OFF. Is determined. If it is determined that the power of the peripheral device 3 is ON, the process proceeds to step S405. If it is determined that the power of the peripheral device 3 is OFF, the process proceeds to step S406.
In step S405, the state of the power supply of the user terminal 1 to which the peripheral device 3 to be determined is connected is determined. The unused peripheral device detection unit 205 refers to the value of the power state in the terminal table record related to the user terminal 1 to which the peripheral device 3 to be determined is connected, which is searched for in step S402. Determines whether the power supply of the user terminal 1 is ON or OFF at the present time. If it is determined that the power of the user terminal 1 is ON, the process proceeds to step S407. If it is determined that the power of the user terminal 1 is OFF, the process proceeds to step S406.
In step S406, it is determined that the peripheral device 3 to be determined is an unused peripheral device (power OFF). The unused peripheral device detection unit 205 determines in step S404 that the power supply of the peripheral device 3 to be judged is turned off, or in step S405, the power supply of the user terminal 1 to which the peripheral device 3 is connected is turned off. If it is determined that there is, it is determined that the peripheral device 3 to be determined is not utilized, and the peripheral device 3 is determined to be an unused peripheral device (power OFF). After that, the process proceeds to step S408.
In step S407, it is determined that the peripheral device 3 to be determined is the peripheral device used. The unused peripheral device detection unit 205 determines in step S404 that the power supply of the peripheral device 3 to be determined is ON, and in step S405, the power supply of the user terminal 1 to which the peripheral device 3 is connected is ON. If it is determined that there is, it is determined that the peripheral device 3 to be determined is used, and the peripheral device 3 is determined to be the peripheral device used. After that, the process proceeds to step S408.
In step S408, it is determined whether or not the determination process has been completed for all the peripheral devices 3. If the determination process has not been completed for all the peripheral devices 3, the peripheral device 3 to be determined is changed, and the process proceeds to step S402. When the determination process for all peripheral devices 3 is completed, the process proceeds to step S409. That is, steps S402 to S408 The process in is repeatedly executed until the determination process is completed for all the peripheral devices 3 recorded in the peripheral device table.
In step S409, the determination result is output and notified to the administrator. The server device 2 is the result of the determination by the processing up to step S408, that is, whether the managed peripheral device 3 is a used peripheral device 3, an unconnected unused peripheral device, or the power is turned off. Outputs information to notify if it is an unused peripheral device. As for the information output format, it is preferable that the optimum output format is appropriately adopted according to the embodiment. For example, a list notifying the above-mentioned determination results for all peripheral devices 3 may be output, or an output notifying only unused peripheral devices may be performed. As for the output method, the optimum output method can be appropriately selected according to the embodiment, such as output to a display, print output, transmission output of e-mail, etc., output to a storage device such as auxiliary storage devices 19 and 29, etc. May be adopted.
According to the process shown in this flowchart, the administrator can extract idle assets by immediately grasping the peripheral device 3 that is not currently used, or is connected to a certain user device but is used. It is possible to consider moving the missing peripheral device 3 to another user device.
FIG. 15 is a flowchart showing the flow of the peripheral device configuration trace processing according to the present embodiment. The processing shown in this flowchart is executed when an instruction to start processing from a user or the like is input via an input device or network 9. The specific contents and order of the processes shown in this flowchart are examples, and it is preferable that the processing contents and order suitable for the embodiment are appropriately adopted.
In step S501, the input of the specified date and time is accepted. The input receiving unit 212 of the server device 2 receives the input of the designated date and time specified by the user via the input device. Here, the designated date and time is a date and time indicating a time when the user wants to know the connection status of the peripheral device 3 to the user terminal 1 under the control of the server device 2. Input of the specified date and time may be accepted in the format of year, month, day and time, and various formats such as "1 day ago" and "1 week ago" indicating the time relative to the current time. It may be accepted using the form. Regardless of the format, the specified date and time is converted into a format that can be compared with the connection date and time and disconnection date and time recorded in the connection information table. After that, the process proceeds to step S502.
In step S502, connection information is acquired. The server device 2 acquires all connection information from the connection information table. After that, the process proceeds to step S503. The processes from steps S503 to S506 described below are repeatedly executed while changing the connection information to be determined for each loop until the determination process for all the connection information is completed.
In steps S503 to S505, it is determined whether or not the connection information to be determined is the connection information indicating that the corresponding peripheral device 3 was connected to any user terminal 1 at the designated date and time. Peripheral device extraction unit 206 extracts the values of connection date and time and disconnection date and time from the connection information to be determined, and conditions that the specified date and time entered in step S501 is after the connection date and time and before the disconnection date and time, or the specified date and time Determines whether or not any of the conditions that is after the connection date and time and that the disconnection date and time is NULL is satisfied (step S503). If it is determined that any of the above conditions is satisfied, the process proceeds to step S505. If it is determined that none of the above conditions is satisfied, the process proceeds to step S504.
Either the specified date and time entered in step S501 is after the connection date and time and before the disconnection date and time, or the specified date and time is after the connection date and time and the disconnection date and time is NULL. If is not satisfied, the peripheral device extraction unit 206 determines that the connection information to be processed is not the connection information indicating that the peripheral device 3 was connected to any user terminal 1 at the specified date and time (). Step S504). After that, the process proceeds to step S506.
When either the condition that the specified date and time entered in step S501 is after the connection date and time and before the disconnection date and time, or the condition that the specified date and time is after the connection date and time and the disconnection date and time is NULL is satisfied. Peripheral device extraction unit 206 determines that the connection information to be determined is connection information indicating that the peripheral device 3 was connected to any user terminal 1 at the designated date and time (step S505). After that, the process proceeds to step S506.
In step S506, it is determined whether or not the determination process has been completed for all the connection information. If the determination process is not completed for all the connection information, the connection information to be determined is changed, and the process proceeds to step S503. When the determination process for all the connection information is completed, the process proceeds to step S507. That is, the processes from steps S503 to S506 are repeatedly executed until the determination process for all the connection information recorded in the connection information table is completed.
In step S507, the configuration information is output. In the processing up to step S506, the server device 2 creates and outputs the configuration information based on the connection information determined to be the configuration information of the specified date and time input in step S501. The configuration information may simply output the connection information determined to be the configuration information of the specified date and time side by side, or based on the terminal ID, device type, serial number, etc. included in the connection information. A network configuration diagram showing the connection status of the peripheral device 3 may be created and output graphically. As for the output method, the optimum output method can be appropriately selected according to the embodiment, such as output to a display, print output, transmission output of e-mail, etc., output to a storage device such as auxiliary storage devices 19 and 29, etc. May be adopted. After that, the process shown in this flowchart ends.
According to the process shown in this flowchart, the server device 2 refers to the connection information table in which the connection information is accumulated, and the connection date and time is before the specified date and time and the disconnection date and time is after the specified date and time (the disconnection date and time has not been input). By extracting the connection information (including the record), the administrator can refer to the history of the configuration information at the specified date and time.
FIG. 16 is a flowchart showing the flow of the event trace processing according to the present embodiment. The processing shown in this flowchart is executed when an instruction to start processing from a user or the like is input via an input device or network 9. The specific contents and order of the processes shown in this flowchart are examples, and it is preferable that the processing contents and order suitable for the embodiment are appropriately adopted.
In step S601, the event log is acquired. The server device 2 acquires all event logs from the event log table. After that, the process proceeds to step S602. The processes from steps S602 to S608 described below are repeatedly executed while changing the peripheral devices 3 to be the aggregation process for each loop until the aggregation process is completed for all the peripheral devices 3.
In steps S602 and S603, the event log is narrowed down for each peripheral device 3, and the narrowed down event log is aggregated. The event log extraction unit 207 of the server device 2 searches the event log using the device type and the serial number, and extracts the event log related to the peripheral device 3 to be aggregated (step S602). Then, the event log extraction unit 207 performs event aggregation processing including analysis and aggregation of error contents for the extracted event log (step S603). For example, the event log extraction unit 207 is a collection. It is possible to calculate the number of errors and classify the error contents (messages) within a predetermined period for the peripheral device 3 to be processed. For example, in the event log shown in Fig. 6, when aggregation processing is performed for the scanner 3a whose serial number is A, the message "Error 1" is displayed between January 1, 2010 and January 4, 2010. The fact that the error occurred three times is output as the aggregation result. After that, the process proceeds to step S604.
In step S604, it is determined whether or not the peripheral device 3 is moving. The server device 2 refers to the event log related to the peripheral device 3 to be aggregated, which is extracted in step S602, and includes an event log having a terminal ID indicating a user terminal different from the currently connected user terminal. By determining whether or not the peripheral device 3 is connected, it is determined whether or not the peripheral device 3 has been connected to a user terminal different from the currently connected user terminal in the past. By limiting the event log to be judged to the event log related to the occurrence date and time within the past predetermined period (for example, within the past one week) from the current date and time, only the connection status in the near past is judged. It may be decided. If it is determined that the peripheral device 3 has been connected to a user terminal different from the currently connected user terminal in the past, the process proceeds to step S605. In other cases, the process proceeds to step S608.
In step S605, the events that occurred before and after the movement of the peripheral device 3 are compared. The estimation unit 208 is the same as or equal to the error currently occurring in the peripheral device 3 when the peripheral device 3 to be aggregated is connected to a user terminal different from the currently connected user terminal in the past. Check if a related error has occurred. More specifically, when the estimation unit 208 includes an event log having a terminal ID indicating a user terminal different from the currently connected user terminal in the event log related to the peripheral device 3 to be aggregated. In addition, it is determined whether or not the message recorded in this event log is the same as or related to the message of the error currently occurring (the message recorded in the recent event log).
Here, the event log referred to for identifying the message of the error currently occurring may be the latest event log related to the peripheral device 3 to be aggregated, or the peripheral device 3 to be aggregated. It may be the last event log within the past predetermined period (for example, within the past one day) related to the device 3. The predetermined period set for identifying the error message currently occurring in this step is a period different from the predetermined period for determining the connection status to the different user terminal 1 described in step S604. And a shorter period is set.
As a result of the determination, when the peripheral device 3 to be aggregated is connected to a user terminal 1 different from the currently connected user terminal 1 in the past, it is the same as the error currently occurring in the peripheral device 3 or If it is determined that a related error has occurred, the process proceeds to step S606. On the other hand, if it is determined that a different error has occurred, the process proceeds to step S607.
In steps S606 and S607, the cause of the error currently occurring is estimated. When the peripheral device 3 to be aggregated is connected to another user terminal 1 in the past, the estimation unit 208 also causes an error that is the same as or related to the error that is currently occurring. Is determined to be an error caused by the peripheral device 3 (step S606). On the other hand, the estimation unit 208 does not generate an error that is the same as or related to the error that is currently occurring when the peripheral device 3 to be aggregated is connected to another user terminal 1 in the past. If so, it is determined that the error currently occurring is an error caused by the user terminal 1 or the peripheral device 3 (step S607). After that, the process proceeds to step S608.
In step S608, it is determined whether or not the aggregation process has been completed for all the peripheral devices 3. If the aggregation process has not been completed for all the peripheral devices 3, the peripheral device 3 to be aggregated is changed, and the process proceeds to step S602. When the aggregation process for all peripheral devices 3 is completed, the process proceeds to step S609. That is, the processes from steps S602 to S608 are repeatedly executed until the aggregation process is completed for all the peripheral devices 3 recorded in the peripheral device table.
In step S609, the aggregation result is output. The server device 2 outputs the result of the event log aggregation processing performed in step S603 and the estimation result of the cause of the error currently occurring in step S606 or S607. Similar to the output performed in the other flowcharts described above, the output method includes output to a display, print output, transmission output such as e-mail, output to a storage device such as auxiliary storage devices 19 and 29, and the like. The optimum output method may be appropriately adopted according to the form of. After that, the process shown in this flowchart ends.
In this flowchart, in order to perform aggregation for each peripheral device, the method of narrowing down the event log by using the device type and serial number and totaling it has been described. Instead, the event log is aggregated using the terminal ID. By narrowing down, it may be possible to perform aggregation for each user terminal. According to the process shown in this flowchart, the administrator can grasp the event log history based on the user terminal 1 and the peripheral device 3, and can easily grasp the estimation result of the cause of the error.
FIG. 17 is a flowchart showing the flow of the consumables management process according to the present embodiment. The processing shown in this flowchart is executed periodically or when an instruction to start processing from a user or the like is input via an input device or a network 9. The specific contents and order of the processes shown in this flowchart are examples, and it is preferable that the processing contents and order suitable for the embodiment are appropriately adopted.
Information related to consumables (for example, toner, paper, battery, etc.) used in the process shown in this flowchart includes information collection process step S101 and connection disconnection detection process step S101 described above. In S202 and the like, it is collected or acquired by the user terminal 1 and stored in the peripheral device table, usage history table, event log table, connection information table, consumables characteristic table, usage tendency table, etc. on the user terminal 1 side.
In step S701, the characteristics of consumables are analyzed for each consumable, and the limit value of the amount of consumables used is set. The limit value calculation unit 104 of the user terminal 1 analyzes the consumables characteristics based on the cumulative usage of consumables acquired from the peripheral device table and the event log related to the consumables, and limits the consumables usage. Calculate the value and update the limit value set in the consumables characteristic table. Here, the limit value of the usage amount is a value indicating how much consumables need to be replaced (replenishment required), and may be calculated by various methods. For example, a method of setting the cumulative usage at the time of event occurrence as the limit value as it is, a method of setting the average of the cumulative usage at the time of event occurrence and the previous limit value as the limit value, the cumulative usage at the time of event occurrence and the past A method of setting the average of the actual limit values as the limit value can be considered.
Specifically, when the method of setting the cumulative usage amount at the time of event occurrence as the limit value as it is is adopted, if the cumulative usage amount at the time of event occurrence is 10000 times, 10000 is set as the limit value. If the method of setting the average of the cumulative usage at the time of the event occurrence and the previous limit value as the limit value is adopted, the previous limit value is 20000 times, and the cumulative usage at the time of the event occurrence. If the dose is 10000 times, the average of these 15000 (= (20000 + 10000) / 2) is set as the limit value. In addition, if the method of setting the cumulative usage at the time of the event occurrence and the average of the past limit value results as the limit value is adopted, the limit values set so far are 18000, 17000, 19000, and when the event occurs. If the cumulative usage of is 10000 times, the average of these 16000 (= (18000 + 17000 + 19000 + 10000) / 4) is set as the limit value. After that, the process proceeds to step S702.
In the consumables characteristic table shown in FIG. 8, the value described as "default" is the upper limit of the usage amount provided by the peripheral device vendor. As the limit value, a usage upper limit value provided by the vendor may be set as an initial value. Further, in the calculation of the limit value at the time when the previous limit value or the past limit value is not accumulated, the usage upper limit value provided by the vendor can be used as the previous limit value or the past limit value.
In step S702, the usage tendency is analyzed, and the usage amount of consumables in a predetermined unit time (1 day in this embodiment) is set. The usage tendency calculation unit 105 of the user terminal 1 analyzes the usage tendency of peripheral device consumables for each peripheral device 3 based on the usage period and the usage amount during the usage period grasped from the usage history table, and determines a predetermined unit. Calculate the amount of consumables used over time. Specifically, the amount of consumables used in a unit time can be calculated by dividing the amount used during the trial period by the period of use. Here, the usage period can be obtained by calculating the time from the connection date and time read from the usage history table to the disconnection date and time. If the disconnection date and time is NULL, the usage period may be calculated by calculating the time from the connection date and time to the current date and time. The calculated usage amount per unit time is set in the usage tendency table.
For example, regarding the use of consumables a in scanner 3a with serial number A, the usage period for two days from January 1, 2010 to January 3, 2010 is 400 times, and the usage period is 2010. If the usage for 4 days from January 6 to the time of usage trend analysis (here, January 10, 2010) is 800 times, the usage of consumables per unit time is 200. Times / day (= (400 + 800) times / (2 + 4) days). Once the usage for the predetermined unit period has been calculated and set, the process then proceeds to step S703.
In step S703, a threshold value for notification output is calculated and set from the consumable characteristics and usage tendency. The threshold value calculation unit 106 of the user terminal 1 informs the administrator based on the limit value of the consumables usage amount set in step S701 and the consumables usage amount in the predetermined unit time set in step S702. On the other hand, a threshold value for determining the timing for outputting a notification for notifying the replacement and replenishment time of consumables is calculated and set in the peripheral device table.
Here, the threshold value is a value for determining the timing for outputting a notification to notify the administrator of the replacement and replenishment time of consumables, considering how long it takes to replace and replenish the consumables. It may be calculated by various methods. For example, a method of setting a threshold value obtained by subtracting the usage amount per unit time * replacement replenishment required period from the limit value can be considered. Specifically, if the replacement and replenishment required period is set to 10 days, the limit value is 10000 times, and the usage amount per unit time is 130 times / day, 8700 (= 10000-130 * 10) is the threshold value. Is set as.
The replacement replenishment required period used for calculating the threshold value may be set by the administrator, or the cumulative usage amount may be reset from the notification output in the past (replacement or replenishment of consumables). The cumulative usage is reset to 0 due to such reasons). A method of variably setting the replacement and replenishment required period for each consumable item based on the stored period may be adopted. For example, if the past notification output for a consumable is January 10, 2009, and the cumulative usage reset due to replacement and replenishment of consumables in response to the notification is January 20, 2009, replacement and replenishment Since it was found that it took 10 days for the consumables, 10 days is set as the period required for replacement and replenishment.
When the calculation and setting of the threshold value are completed, the processing shown in this flowchart ends. The comparison unit 107 of the user terminal 1 monitors the cumulative usage of consumables of the connected peripheral device 3, and sets the threshold value set in step S703 periodically or every time the cumulative usage is updated. Compare with cumulative usage. Then, when the cumulative usage exceeds the threshold value, the notification output unit 108 of the user terminal 1 outputs a notification to notify the administrator of the replacement and replenishment time of the consumables. Specifically, if the consumable item is the toner of the printer 3b, a notification message such as "Toner will run out in about 10 days. Please replenish the toner by then" is output to the display and printed out. , E-mail transmission output, output to storage devices such as auxiliary storage devices 19 and 29, etc., and output to the administrator by an output method according to the embodiment.
According to the process shown in this flowchart, an alert regarding consumables used in the peripheral device 3 can be notified to the administrator and the user at an appropriate timing. In the present embodiment, the execution body of the consumables management process is described as the user terminal 1, but the consumables management process may not be performed on the user terminal 1 to which the peripheral device 3 is connected. For example, the consumables management process may be executed by the server device 2 after transmitting information (tables and the like) necessary for the process from the user terminal 1 to the server device 2.
1 User terminal (information processing device) 2 Server device 3 Peripherals 15 Peripheral device connection interface
18 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| JP2016136307A | Cited by | Japan | Search report |
| US9678742B2 | Cited by | United States of America | Applicant |
| JP2015001814A | Cited by | Japan | Search report |
| JP2015060278A | Cited by | Japan | Search report |
| JP2014052923A | Cited by | Japan | Search report |
| JP2002027552A | Cites | Japan | Examiner |
| JP2003122710A | Cites | Japan | Examiner |
| JP2003296044A | Cites | Japan | Examiner |
| JP2006185251A | Cites | Japan | Examiner |
| JP2008015616A | Cites | Japan | Examiner |
4 members in 2 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 2010064297 | Japan | A | |
| JP20100064297 | – | – | – |
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2011231542A1 | United States of America | A1 | |
| JP2011198056AThis record | Japan | A | |
| JP5479176B2 | Japan | B2 | |
| US9432549B2 | United States of America | B2 |
7 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 2011198056
- Publication, DOCDB
- 2011198056
- Publication, EPODOC
- JP2011198056
- Application
- 64297
- Application, DOCDB
- 2010064297
- Application, EPODOC
- JP20100064297
Titles2
- Japanese
- 情報処理装置、サーバ装置、周辺装置管理方法およびプログラム
- English
- Information processing equipment, server equipment, peripheral equipment management methods and programs
Classification
- CPC, 12
- H04N1/32122
- H04N1/00238
- H04N1/00241
- H04N1/00344
- H04N1/00832
- H04N2201/0081
- H04N2201/0082
- H04N2201/3202
- H04N2201/3204
- H04N2201/3205
- H04N2201/3274
- H04N2201/3278
- IPC, 2
- G06F13 00
- G06F3 12