JP3663881B2 - Device information management device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a device information management apparatus that periodically inquires device information of a device to be managed and manages a device information group obtained by the inquiry.
[0002]
[Prior art]
In recent years, a system in which devices such as printers and so-called multifunction devices (that is, devices having functions such as printers, copiers, and facsimile machines) are connected to a network and can be shared by a plurality of clients (personal computers, etc.) It has become.
[0003]
For example, when sending a print job from a client to a printer or the like, the printer is out of paper or out of toner, and the queuing status of the print job (number of jobs waiting for processing, size, etc.) It is convenient if the client side can grasp the status (status) of the printer. For this reason, some client applications have a function of inquiring about the status of the printer and displaying the result. In addition, the client can use information such as the network protocol used by the printer, the format of print data that can be processed, information on the font currently owned by the printer, etc., or “the cover is open”, “ Inquiries about the status of mechanical systems such as printers such as "paper jams." Such status and other information held by the printer or the like is hereinafter referred to as “device information”.
[0004]
The inquiry of device information from the client to the printer or the like is performed using a standard data structure called MIB (Machine Information Base or Management Information Base), for example. In this method, a printer or the like manages its own device information as an MIB format database, and a client inquires of the MIB such as a printer for necessary device information using a predetermined protocol.
[0005]
However, in general, a printer or the like often has a poor network function. If a large number of inquiries are received at the same time, processing such as original printing (especially reception of a print job) is delayed and performance is degraded.
[0006]
In order to avoid such a problem, conventionally, in a network of a certain size, a device management server for managing device information such as printers is provided separately from the printer, and the device management server collectively responds to inquiries from clients. A method of responding is adopted. In this case, the device management server performs polling (inquiries) on printers, etc., periodically acquires each device information, always grasps the latest device information as much as possible, and can respond to inquiries from clients. Yes.
[0007]
Some device information changes frequently and some does not. For example, the queuing status of a printer changes relatively frequently, whereas the type of font that the printer has does not change so frequently. Therefore, when considering the response load of the printer, it is more efficient to make an inquiry at an appropriate frequency by changing the polling time interval (hereinafter referred to as “inquiry cycle”) for each piece of device information. For this reason, in the conventional device management server, an appropriate inquiry cycle is set in advance for each piece of device information, and an inquiry is made to the printer or the like at each set inquiry cycle for each piece of device information. If there is device information that matches the inquiry timing, they are inquired by the same thread.
[0008]
[Problems to be solved by the invention]
In the above-mentioned conventional device management server, when the inquiry timing of each device information matches, it was possible to inquire all at once, but when the inquiry timing of each device information is slightly shifted, they are inquired separately. I was supposed to be. In such a case, the printer or the like receives an inquiry at a short interval, and the load for response temporarily increases during that time, and the efficiency of the original processing of the print job or the like may decrease during that time.
[0009]
Also, depending on the type of device information, there are cases where the load (for example, required time) when a printer or the like responds to an inquiry is large. For example, in the case of an inquiry about fonts possessed by a printer or the like, if the printer has a large number of fonts, the response may take a long time (for example, about 1 second). On the other hand, if all the device information having the same inquiry timing is inquired collectively, the response load of the printer or the like may become extremely large depending on the combination of the inquiring device information. During the inquiry response process, the printer or the like basically cannot process the original print job, so when an inquiry with a large response load is received, the printer or the like has a longer period during which the original process such as the print job cannot be performed, There was a problem that the processing efficiency was lowered.
[0010]
Such a problem is not limited to a printer or a multifunction peripheral, and the same problem may occur for other devices connected to the network.
[0011]
The present invention has been made to solve such problems, and dynamically controls the inquiry timing of device information from a device information management device such as a device management server to a managed device such as a printer. Thus, it is intended to alleviate an increase in response load of the managed device with respect to the inquiry and to suppress a decrease in efficiency of processing inherent to the managed device due to the device information inquiry.
[0012]
[Means for Solving the Problems]
In order to achieve the above object, the present invention is a device information management device for periodically inquiring each device information held by a device to be managed and managing the device information group acquired as a result, A query cycle table in which a query cycle of the device information is registered for each piece of information, and a scheduling unit that determines a query time for the query for each device information based on the query cycle table and registers the query time in the scheduling table And inquiry means for referring to the scheduling table every predetermined time and inquiring device information to the managed device if there is device information for which the inquiry time has arrived. Forward possible time storage means for storing for each device information the possible advance time that can be advanced from the time determined according to the inquiry cycle time of inquiry by the inquiry means; And when the inquiry means makes an inquiry about the device information to the managed device, the inquiry means Corresponds to the device information Check whether there is any advanceable device information for which the inquiry time comes within the advanceable time by referring to the scheduling table. If there is advanceable device information, the advanceable device information With the device information for which the inquiry time has arrived. It is characterized by inquiring at the same time.
[0013]
In this configuration, the inquiry target device information is registered in the scheduling table. In the scheduling table, the inquiry time (timing) is set for each piece of device information by the scheduling means. The inquiry means refers to the scheduling table, and sequentially inquires the managed device about the device information at the inquiry time. The phrase “inquiry time has arrived” includes not only the case where the inquiry time has just come, but also the case where the current time has passed the inquiry time. When inquiring about certain device information, the inquiry means also inquires about the device information (that is, “advanceable device information”) at the same time if another device information is within a predetermined advance possible time. In other words, for the device information within the advance possible time, execution of the inquiry is advanced ahead of schedule.
[0014]
According to this configuration, when the difference in the inquiry time between the pieces of device information is small (that is, the difference is within an advanceable time), the device information management apparatus collectively inquires the device information group at a time. The processing necessary for the inquiry of each piece of device information, such as access processing, can be performed only once. In other words, in the past, such common processing was performed repeatedly for each inquiry about device information, so if the inquiry interval for the device information was short, the original processing of the device (in the case of a printer) The overhead of the common processing cannot be ignored for the period during which the print job can be executed. On the other hand, according to this configuration, such overhead is reduced, and once a query is made, there is no next query for at least the time that can be moved forward. A sufficient period of time can be taken.
[0015]
In the above configuration Is Establish possible advance time for each piece of device information according to the nature of the piece of device information ing. This Depending on the individual device information, there may be a difference in how much the inquiry timing may deviate from a predetermined schedule. In this configuration, detailed processing according to the properties of the individual device information is performed in such a case. It becomes possible.
[0016]
In a preferred aspect of the present invention, the device information management device has an inquiry response load table in which the response load amount of the managed device for the inquiry is registered for each device information, and the inquiry means refers to the table. The device information for which the inquiry processing is advanced is selected within a range in which the sum of the response load amounts is equal to or less than a predetermined upper limit value.
[0017]
If the inquiry is advanced, the response load for a single inquiry (the sum of the response load amounts of a plurality of pieces of device information inquired at that time) may become too large in some cases. In such a case, the efficiency of the original processing of the managed device may be reduced instead of moving forward. On the other hand, according to this aspect, the upper limit value of the response load amount that can be received at one time by the managed device is determined, and the advancement is performed within the range of the upper limit value or less. Therefore, such a problem can be avoided. The upper limit value of the response load amount may be determined from the allowable limit of the processing efficiency reduction of the managed device.
[0018]
In this aspect, an inquiry priority table in which the inquiry priority of the device information is registered for each piece of device information is provided, and when the device information to be advanced is selected, the higher the inquiry priority, the higher priority is selected. Is also suitable. According to this aspect, by giving higher inquiry priority to device information having a higher advance effect, when there are a plurality of advanceable device information, it is possible to preferentially select the device information having a higher advance effect. For example, easily changeable device information such as job queuing status needs to be updated to the latest information as soon as possible, which will give a high inquiry priority. For device information that does not change that often, such as fonts that the printer has, the query priority will be set low.
[0019]
Further, in another aspect of the present invention, the device information management apparatus has an inquiry characteristic table in which the response load amount and inquiry priority of each device information is registered, and the device information to be moved forward is set as the response load amount. Select by combination of query priority. For example, a method may be considered in which an evaluation formula having response load amount and inquiry priority as parameters is used, and a device information group having the best evaluation formula value is advanced.
[0020]
In addition, the present invention provides an inquiry cycle table in which the inquiry cycle of the device information is registered for each device information, and an inquiry response in which the response load amount of the managed device for the inquiry of the device information is registered for each device information. Based on the load table and the query cycle table, a query time to be queried for each device information is determined, and a scheduling means for registering in the scheduling table, referring to the scheduling table every predetermined time, the query time If there is device information that has arrived, inquiry means for making an inquiry of the device information to the managed device, A post-rotatable time storage unit that stores a postponeable time that can be postponed from the time determined by the interrogation period according to the query cycle; And the inquiry means refers to the inquiry response load table when there are a plurality of pieces of device information whose inquiry time has arrived when referring to the scheduling table, the response load amount for each piece of device information. Of the pieces of device information to be simultaneously queried at that time is selected within a range where the sum of the response loads is equal to or less than a predetermined upper limit, and the remaining pieces of device information are registered in the scheduling table. Time Corresponds to the device information It is characterized in that it is deferred by a postponed time (that is, the inquiry is postponed).
[0021]
According to this configuration, when the sum of the response load amounts of the device information group to be inquired at the same time becomes too large, the inquiry of some device information is deferred by a predetermined delay time, so the response load of the managed device at that time Temporary increase can be avoided, and reduction in the efficiency of the original processing of the managed device during that time can be prevented.
[0022]
In this configuration, it is also preferable to determine the postponement possible time for each piece of device information according to the properties of the individual piece of device information. For example, device information that changes quickly and needs to be updated as frequently as possible should have a short postponed time.
[0023]
In this configuration, if query priority is set for each piece of device information and the query priority is set in descending order, device information with a higher query priority can be queried at an earlier timing. .
[0024]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention (hereinafter referred to as embodiments) will be described with reference to the drawings.
[0025]
[Embodiment 1]
FIG. 1 is a diagram showing a system configuration example when the present invention is applied to a network printing system. The device management server 10 is a server having the function of the device information management device according to the present invention, and is a printer 22 or a multi-function device (a device having functions of a printer, a copier, a facsimile, etc.) 24 connected via a network 26. Manage device information. That is, the printer 22 and the multifunction device 24 are managed devices of the device management server 10. The device management server 10 can manage a plurality of managed devices in this way. Each of these managed devices holds each piece of device information relating to its own state in the form of a predetermined database such as an MIB. The device management server 10 inquires device information to these managed devices (printer 22 and multifunction device 24) using a predetermined protocol (for example, SNMP), and obtains device information obtained as a result of the inquiry for each managed device. And manage it as a database.
[0026]
The client 20 is a device that uses the printer 22 or the multifunction device 24 such as a personal computer or a workstation. The client 20 makes an inquiry to the device management server 10 when device information of the printer 22 or the multifunction device 24 is necessary. The client 20 is loaded with software for this inquiry.
[0027]
In the present embodiment, the client 20 has a function of periodically querying the device management server 10 for device information in order to enable dynamic grasp of changes in device information. For example, when a command for requesting inquiry of certain device information is input from the user, the client 20 inquires the device management server 10 for the device information at a predetermined cycle until the inquiry request disappears, and the client 20 is always up-to-date during that time. The information is presented to the user. For example, when receiving an inquiry request from the user, the client 20 generates a screen (window or the like) that displays the device information to be introduced, inquires the device management server 10 for the device information, and displays the device information on the display screen. The contents of the device information displayed on this display screen are periodically updated by inquiries to the device management server 10 performed every predetermined cycle. Then, when the user inputs a command for stopping the inquiry of the device information, the client 20 ends the display of the display screen and stops the periodic inquiry to the device management server 10. Note that some types of device information do not need to be periodically inquired (for example, those that do not change). For such device information, the client 20 only receives the inquiry request from the user. Inquires the management server 10.
[0028]
When receiving an inquiry from the client 20, the device management server 10 basically searches for the device information of the managed device requested by the inquiry from the database of each managed device managed by the device 20. (However, as will be described later, if the managed device information is older than the allowable limit, the client 20 receives the latest information from the target managed device and obtains the latest information. Answer). Here, the device management server 10 determines whether or not the device information queried from the client 20 is likely to be repeatedly queried thereafter, and for what may be repeatedly queried, It has a function to periodically inquire device information about the managed device in advance in preparation for subsequent inquiries. This function is realized by a polling database 14 and a polling control unit 16 described later. Details of this function will be described later in the description of the polling control unit 16. The access from the client 20 to the device management server 10 is usually performed via a network. The client 20 may be connected on the network 26 or may be connected to another network to which the device management server 10 is connected. The device management server 10 can respond to inquiries from a plurality of clients 20.
[0029]
As described above, in this embodiment, the device management server 10 basically inquires the managed device about the device information to be introduced only when there is a query from the client 20 and when it is expected that there will be a query. ing. In other words, the device management server 10 avoids inquiring of the managed device as much as possible for the device information that is not inquired by the client 20 (that is, that the client 20 does not need) during the period of no inquiry. . With such a configuration, it is possible to reduce the load on the managed device and the network 26 caused by the inquiry.
[0030]
Next, details of the device management server 10 will be described. The device management server 10 includes a device information inquiry reception unit 12, a polling database 14, a polling control unit 16, and a device information collection unit 18.
[0031]
The device information inquiry receiving unit 12 receives a device information inquiry from the client 20 and registers necessary items in the polling database 14 in accordance with the inquiry.
[0032]
The polling database 14 has various pieces of information for determining the timing of inquiry (polling) of each device information to each managed device. The polling database 14 includes a property table 142 and a scheduling table 144.
[0033]
In the property table 142, for each piece of device information, characteristic information unique to the piece of device information regarding determination of polling timing is registered. FIG. 2 shows the registered contents of the property table 142 in this embodiment. As shown in FIG. 2, in the property table 142, an inquiry cycle and an advanceable time are registered for each inquiry item (that is, device information).
[0034]
The inquiry cycle is a repeated time interval when the inquiry of the inquiry item is repeated from the device management server 10 to the managed device. For example, device information that changes rapidly, such as the queuing status of a print job queue such as a printer, is always set to be as short as possible, so the inquiry cycle is set short (for example, several seconds to several tens of seconds). On the contrary, since the font information of the printer does not change so frequently, the inquiry cycle is set to be long (for example, several hours to several tens of hours). Some inquiry items do not need to be repeated, and no inquiry period is set for such items.
[0035]
Here, the inquiry cycle of each inquiry item defines a reference cycle, and is preferably set in the form of an integer multiple of the reference cycle. This is because there is a high possibility that the inquiry times of the inquiry items match. If the inquiry times match, they can be inquired at the same time, thereby reducing the load on the managed device.
[0036]
This inquiry cycle is determined in conjunction with the inquiry cycle performed by the client 20 to the device management server 10 described above. That is, the inquiry cycle from the client 20 to the device management server 10 and the inquiry cycle from the device management server 10 to the managed device take into account the nature of each piece of device information (for example, whether the change is fast or slow). Determined for each piece of device information. In the present embodiment, every time a managed device is inquired about certain device information, the next inquiry timing (referred to as “inquiry time”) is determined based on the inquiry cycle of the device information.
[0037]
The advance-possible time is an allowable limit time during which an inquiry can be advanced from the inquiry time determined in this way. As is clear from the definition, the advance-possible time is usually a value shorter than the inquiry cycle (it is meaningless to set a value longer than the inquiry cycle). The advanceable time is determined for each piece of device information in consideration of the nature of the individual piece of device information. For example, for device information that is considered to have little change (for example, a list of fonts held by a printer or the like), the inquiry timing may not be so strict, and the advanceable time can be set to a longer value.
[0038]
The scheduling table 144 is a schedule table for inquiries (polling) to managed devices. In the scheduling table 144, for each piece of device information, the time when the next inquiry is made (ie, “inquiry time”) is, for example, X hour. Registered in the format of Y minute Z second. As described above, the value of this inquiry time is determined and updated for each piece of device information with reference to the inquiry cycle of the property table 142 every time the device information is queried. This update process is performed by the polling control unit 16. Further, in the present embodiment, in the scheduling table 144, among all the device information held by each managed device, only the information that has been inquired by the client 20 or expected to be inquired from the client is registered. .
[0039]
The polling control unit 16 refers to the polling database 14 and controls inquiry (polling) of the device information to the managed device. In other words, the polling control unit 16 refers to the scheduling table 144 to detect device information at the inquiry time, and if there is such device information, instructs the device information collection unit 18 to collect the device information. Do.
[0040]
The device information collection unit 18 makes an inquiry about the device information group instructed by the polling control unit 16 to the managed devices such as the printer 22 and the multifunction device 24, and acquires the device information from the managed devices. . The acquired device information group is registered in a device information database (not shown) of each managed device included in the device management server 10, and the information in the device information database is thereby updated. This device information database can be configured as an MIB, for example.
[0041]
In addition, every time the polling control unit 16 issues an instruction to collect device information to the device information collection unit 18, the polling control unit 16 determines the next inquiry time for the device information and registers it in the scheduling table 144.
[0042]
The device information group acquired from the managed device by such a mechanism and registered in the device information database of the device management server 10 is notified to the client 20 in response to an inquiry from the client 20. Since the registration of the device information acquired from the managed device in the database and the notification of the response to the inquiry of the client 20 are not the object of the present invention, the description thereof will be omitted. A known method may be used for these.
[0043]
Next, with reference to FIG. 4, the flow of inquiry (polling) processing for the managed device of the device management server 10 of this embodiment will be described.
[0044]
The inquiry process of the present embodiment basically includes two loops, a loop that accepts an inquiry from the client 20 and a loop that makes an inquiry to the managed device. These two loops can be executed completely independently.
[0045]
The loop of the inquiry reception process from the client is executed by the device information inquiry reception unit 12. The device information inquiry receiving unit 12 confirms whether there is a device information inquiry from the client 20 every predetermined time (for example, 1 second) (S10). For example, the device information inquiry accepting unit 12 may be configured to have a queue for accumulating inquiry requests coming from the client 20, check the queue every predetermined time, and take out any inquiry requests in the queue. it can. If there is no inquiry in S10, the process of S10 is repeated after a predetermined time. If there is a query in S10, the device information query acceptance unit 12 registers the device information for which the query has been made in the scheduling table 144 as a query item (S12). Specifically, the device information inquiry receiving unit 12 checks whether the queried device information is already registered in the scheduling table 144, and if not registered, newly registers the device information as an inquiry item. At the same time, the current time at that time is registered in the scheduling table 144 as the first inquiry time of the inquiry item. On the other hand, when the inquired device information is already registered in the scheduling table 144 as an inquiry item, it is not newly registered. When there are a plurality of inquiries in S10 or inquiries about a plurality of device information, the above processing is performed for each of the inquired device information. The device information inquiry receiving unit 12 repeatedly performs the processing described above.
[0046]
In response to the inquiry from the client 20 accepted by the device information inquiry accepting unit 12, an answer processing unit (not shown) answers. If the inquired device information has already been registered in the scheduling table 144, the response is made by reading the value of the device information from the device information database of the device management server 10 and replying. Is called. If the queried device information is not registered in the scheduling table 144, the value of the device information registered in the device information database is likely to be older than the allowable limit. Then, after waiting for the result of the inquiry about the device information executed by the polling control unit 16 or the like, the client 20 is answered.
[0047]
The polling control unit 16 executes the process according to the following procedure independently of the inquiry reception and answer process described above.
[0048]
The polling control unit 16 checks whether it is time to check the scheduling table 144 (S20). In this embodiment, since the scheduling table 144 is checked at every predetermined basic processing interval time, it is checked whether or not the basic processing interval time has passed since the time of the previous check.
[0049]
If the determination result in S20 is Yes, the polling control unit 16 extracts from the scheduling table 144 query items that satisfy a predetermined condition, such as a query item whose query time has arrived, and queries the managed device for these query items. Is executed (S22). That is, an inquiry instruction for these inquiry items is issued to the device information collection unit 18 to make an inquiry to the managed device.
[0050]
In S22, not only the inquiry item whose inquiry time has come, but also an inquiry item (referred to as an “advanceable item”) that becomes the inquiry time within the advance possible time from the current time is inquired at the same time. The process of S22 will be described in more detail later.
[0051]
Then, the polling control unit 16 checks whether or not the inquiry item inquired in S22 is an object to be repeatedly inquired periodically, and determines the next inquiry time for the relevant inquiry item to determine the scheduling table 144. (S24). It is determined with reference to the property table 142 whether or not it is a repeat target. That is, if a query cycle is set in the property table 142, the query item is a repetition target. The polling control unit 16 determines the next inquiry time by adding the inquiry period to the current time for the inquiry item to be repeated. The polling control unit 16 updates the inquiry time value of the inquiry item in the scheduling table 144 to the next inquiry time determined as described above.
[0052]
When the above processing is completed, the polling control unit 16 waits for the basic processing interval time and performs the processing of S22 again. If there is no inquiry item for which the inquiry time has arrived in S22, of course, neither inquiry to the managed device nor update of the inquiry time associated therewith is performed.
[0053]
Next, details of the processing of S22 (inquiry to the managed device) will be described with reference to FIG. In S22, the polling control unit 16 compares the inquiry time of each inquiry item registered in the scheduling table 144 with the current time, and takes out the inquiry item corresponding to any of the following three (S30). The first is that the inquiry time has come, that is, the inquiry time is equal to the current time. Secondly, the inquiry time has passed, which is the inquiry time before the current time. Thirdly, the inquiry time arrives within a possible advance time from the current time. Items corresponding to the third case can be determined by the following equation.
[0054]
[Expression 1]
(Inquiry time)-(Advance possible time) <(Current time)
("<" Indicates that the time is before)
Whether it corresponds to the third case is determined based on the inquiry time registered in the scheduling table 144 with reference to the advanceable time in the property table 142 for each inquiry item.
[0055]
Each inquiry item registered in the scheduling table 144 is sequentially examined, and if there is one that satisfies any of the above three conditions, it is registered in a list (referred to as an “execution list”).
[0056]
The above processing is repeated until there is no item corresponding to any of these three conditions (S32). When there is no corresponding item (No in S32), the managed device is inquired about each corresponding item registered in the execution list ( S34).
[0057]
For example, when the property table 142 and the scheduling table 144 are in the state shown in FIGS. 2 and 3, when the time is 12: 5: 10, the query item A is registered in the execution list as the query time has arrived. At the same time, the inquiry items B and C are registered in the execution list because the inquiry time arrives within the advanceable time (10 seconds and 10 minutes, respectively) from that time. Then, the items A, B, and C are simultaneously inquired to the managed device.
[0058]
The managed device that has received this inquiry extracts the value of each device information inquired from its own database (MIB or the like) and responds to the device management server 10. Upon receiving this response, the device management server 10 (device information collection unit 18) updates the registration information in the device information database with the value of the device information included in the response.
[0059]
As described above, while the inquiry is repeatedly received from the client 20 to the device management server 10, the device information to be inquired is periodically updated by the above process, whereby the client 20 is inquired for each inquiry. The latest value of the device information at that time is notified. However, when any client 20 stops inquiring about the device information, continuing the inquiry to the managed device for such device information places an unnecessary response load on the managed device. In order to eliminate such a wasteful load, in this embodiment, when any client 20 no longer receives an inquiry about certain device information, the device information is removed from the inquiry items of the scheduling table 144. For this process, for example, the inquiry time of each inquiry item registered in the scheduling table 144 is compared with the current time, and no inquiry is received from the client 20 even if a predetermined time elapses after the inquiry time has passed. If there is an inquiry item, a method of removing it from the scheduling table 144 can be used. For example, this processing may be performed simultaneously when the polling control unit 16 checks the scheduling table 144 at each timing when the determination result of S20 is Yes. Further, this process may be performed by the device information inquiry receiving unit 12. A dedicated processing loop for this processing may be provided. Here, it is preferable that the predetermined time for confirming that the inquiry from the client 20 is lost is set for each inquiry item. The predetermined time can be set, for example, as an integer multiple of the inquiry period of each inquiry item as a reference.
[0060]
As described above, in this embodiment, when an inquiry is made about an inquiry item whose inquiry time has arrived (corresponding to the first and second cases), an inquiry is scheduled to be made within a possible advance time from the current time at that time. Inquiry items (items that can be moved forward) are also performed at the same time. In other words, the items that can be moved forward are carried forward (that is, moved forward) from the inquiry time at which the inquiry was scheduled. Then, for an item that has been inquired ahead of time, the next inquiry time is newly determined based on the inquiry time.
[0061]
According to such a configuration, it is possible to prevent the inquiry to the managed device from being frequently repeated during a short period (that is, the advance possible time). Since the same command may be used for queries even with different query items, the ratio of the number of commands to the number of query items can be lowered by inquiring as many query items as possible in this way, and managed. The load of receiving device commands can be reduced. In addition, when many inquiry items are inquired at the same time, the load (response time, etc.) for the response of the managed device is smaller than the total load when inquiries are made separately for each item. It is customary. Therefore, in the present embodiment, by collecting as many queries as possible within the allowable range from the query schedule (that is, within a range that can be moved forward), the response burden of the managed device is reduced, and the managed device can perform the original job (printer). In this case, it is possible to increase the time during which printing) can be executed and to improve the processing efficiency of the managed device.
[0062]
In addition, it is possible to prevent delays in updating device information by processing inquiries that can be advanced in advance. In other words, if a job with a heavy load (for example, a print job with a large number of pages) is input to the managed device after the inquiry is made until the next inquiry, the managed device must wait for the job to end. , We can not respond to later inquiries. Therefore, when the interval between the previous query and the subsequent query is a short time interval that can be brought forward, the subsequent query will be considerably delayed from the original schedule. The query item with a shorter advanceable time is considered to have a shorter query cycle, so the effect of this delay is greater. On the other hand, in the present embodiment, since the inquiry item within the possible advance time is advanced and inquired, the inquiry of the device information (inquiry item) whose contents are desired to be updated quickly is prevented. It is possible to prevent a significant delay due to the job.
[0063]
In addition, since the query is integrated in this way, the interval between the first query and the next query is increased on average, so that the managed device can request a request from the client 20 for the original job (the printer's In this case, the period for receiving the print job) becomes longer. As a result, when the client 20 makes a request to the managed device, the possibility of waiting for the processing is reduced. Therefore, the response of the original operation of the managed device can be improved.
[0064]
Similarly, according to the present embodiment, since the number of inquiries is reduced, the load on the network 26 can also be reduced.
[0065]
In addition, according to the present embodiment, by setting the advance possible time for each inquiry item (device information) individually, an appropriate advance possible time is set individually considering the nature of each inquiry item. It is possible to control the advance of inquiry in detail.
[0066]
As described above, in the present embodiment, in response to a dynamic device information inquiry request from the client 20, the load on the managed device and the network is not increased as much as possible, and the device information that has been queried is as much as possible. The latest information can be returned to the client 20.
[0067]
In the above embodiment, the advanceable time is determined for each piece of device information, but this is not essential for the present invention. The case where the advance possible time is set to a constant value regardless of the type of device information is also included in the scope of the present invention. In this case, the possible advance time may be determined in consideration of the load on the managed device and the network. In this mode, detailed forward control as in the above-described embodiment cannot be performed, but the effect of reducing the load on the managed device and the network by executing the queries collectively can be sufficiently obtained.
[0068]
[Embodiment 2]
Next, a second embodiment of the present invention will be described.
[0069]
In the above embodiment, when making an inquiry to the managed device, if there are other inquiry items that can be brought forward, all of them are moved forward and inquired at the same time. However, depending on the type of inquiry item, the response load of the managed device may be very large. If an item with a large response load is brought forward in this way, the response time required for the managed device for one inquiry Becomes extremely large, and during that time, the original operation of the managed device cannot be accepted. That is, during this time, even if a job is transmitted from the client 20 to the managed device, the managed device cannot respond to the job. Therefore, the client 20 has to wait for a long time for job processing. The present embodiment is for solving such a problem.
[0070]
The configuration of the device management server 10 of the present embodiment may be the one shown in FIG. However, the registration information of the property table 142 and the processing content of S22 (see FIG. 4) of the polling control unit 16 are slightly different from those in the first embodiment.
[0071]
FIG. 6 shows the contents of the property table 142 used in the present embodiment. The difference from the property table 142 of the first embodiment is that items of priority and response load are added.
[0072]
The priority is an index serving as a reference for selection when selecting which inquiry items are to be inquired simultaneously. In the example of FIG. 6, the order in which inquiry items are to be selected with priority is set as the priority of the item. That is, an inquiry item having a smaller priority value is preferentially selected.
[0073]
The response load amount is an index representing the response load of the managed device with respect to the inquiry (such as time required for response), and the larger the value, the greater the response load. Although how much the response load is actually applied when the managed device receives an inquiry varies depending on the time and the case, an average value may be determined in advance and registered in the property table 142.
[0074]
Next, the processing content of S22 (inquiry processing) of the polling control unit 16 will be described with reference to FIG. The process (S30 and S32) of referring to the scheduling table 144 to extract the query item for which the query time has arrived and the query item for which the query time comes within the possible advance time and registering it in the execution list (S30 and S32) is described in the first embodiment. Same as the case. The feature of this embodiment is that the number of items is adjusted so that the sum of the response load amounts of inquiry items that are simultaneously inquired to managed devices does not exceed a predetermined upper limit value.
[0075]
In other words, in the present embodiment, after completion of the execution list (when the result of S32 is Yes), the sum of the response load amounts W of the query items registered in the execution list is equal to or less than a predetermined upper limit TS. It is inspected whether or not (S40). This check is performed with reference to the value of the response load amount in the property table 142. If the sum of the response load amounts exceeds the upper limit value, the property table 142 is referred to delete the item that can be moved forward with the lowest priority from the execution list (S42), and the response load amount in the execution list again. Is compared with the upper limit (S40). The above procedure is repeated, and when the sum of the response load amounts becomes equal to or less than the upper limit value, the managed device is inquired about the inquiry items registered in the execution list at once (S44).
[0076]
For example, in the example of FIG. 6, it is assumed that both the item B and the item C can be advanced when it is time to inquire about the inquiry item A. In this case, if the upper limit value of the response load amount of the managed device is set to “8”, for example, the items A, B, and C cannot be inquired at the same time. Therefore, when the item C having a low priority is deleted from the items B and C that can be brought forward, the sum of the response load amounts is “5”, which is less than the upper limit value. Therefore, the items A and B are inquired at the same time. It will be.
[0077]
As a precaution, the execution list contains a mix of query items that have reached the query time and items that can be moved forward (query items that have the query time within the time that can be moved forward). In the form, only items that can be moved forward are deleted from the execution list. The idea is to always make inquiries when the inquiry time comes, and if the response load on the managed device becomes too large, the inquiry items to be moved forward will be deleted in order from the lowest priority. It is.
[0078]
As described above, according to the present embodiment, it is possible to prevent the response load of the managed device with respect to one inquiry from becoming too large, and the response of the response when the client 20 requests an original job to the managed device. Deterioration can be suppressed.
[0079]
In the second embodiment described above, the inquiry item to be moved forward according to the priority is selected within a range in which the sum of the response load amounts satisfies the predetermined upper limit value. However, the response load amount and the priority may be set differently. By combining, it is possible to select an inquiry item to be brought forward. For example, the priority and response load of each query item are assigned to a predetermined evaluation formula, and the sum of the query item evaluation values obtained as a result is within a predetermined threshold value or less. You can select the inquiry item that you want to bring forward.
[0080]
According to this configuration, an inquiry item to be brought forward can be determined by comprehensive evaluation of the response load amount and the priority. Therefore, an inquiry item with an extremely high priority can be inquired ahead of time even if the response load is somewhat large. Therefore, it is possible to reduce the possibility that a query for a query item having a high priority is awaited by processing of the managed device by a job other than the query.
[0081]
[Embodiment 3]
Next, a third embodiment of the present invention will be described. In this embodiment, in order not to increase the load on the managed device when the sum of the response load amounts for the inquiry items to be simultaneously inquired exceeds a predetermined upper limit value, the inquiry of some inquiry items is performed. It is something that will be postponed.
[0082]
That is, depending on the combination of the query periods of each query item, the query times of a plurality of query items may match. In particular, when the inquiry period of each inquiry item is set in the form of an integer multiple of a reference period, such a match is likely to occur. Even if the inquiry times do not match, inquiries about inquiry items that could not be inquired during that time may be concentrated after the managed device processes a heavy job. The present embodiment is intended to alleviate a temporary increase in the inquiry response load of the managed device in such a case.
[0083]
The configuration of the device management server 10 of the present embodiment may be the one shown in FIG. However, the registration information of the property table 142 and the processing content of S22 (see FIG. 4) of the polling control unit 16 are different from those in the first embodiment.
[0084]
FIG. 8 is a diagram showing the contents of the property table 142 used in the present embodiment. The difference from the property table 142 of the first embodiment is that a postponement possible time is registered instead of a forward advancement possible time, and items of priority and response load amount are added. Note that the priority and response load amount have the same properties as those described in the second embodiment. In other words, the priority is an index that serves as a selection criterion when selecting which query items should be inquired at the same time, and the response load is an index that represents the response load of the managed device for the query (such as the time required for response). It is. Note that the inquiry cycle indicates a time interval of inquiry predetermined for each inquiry item, as in the first embodiment.
[0085]
The postponement possible time is an allowable limit time during which the inquiry can be delayed from the scheduled inquiry time. For example, for inquiry items that change quickly, such as the job queuing status of the managed device, the latest information can be acquired as soon as possible, so the postponement possible time is set short. Further, for items that are not desired to be postponed, it is possible not to set the postponement possible time.
[0086]
Next, the processing procedure of S22 (inquiry processing) of the polling control unit 16 in the present embodiment will be described with reference to FIG.
[0087]
First, the polling control unit 16 compares the query time of each query item registered in the scheduling table 144 with the current time, and extracts the query item whose query time has come and the query item whose query time has passed (S50). ). The retrieved inquiry item is registered in the execution list. The process of S50 is repeated until there is no item that satisfies either of the two conditions (S52).
[0088]
When all the corresponding items are extracted, it is next determined whether or not the sum of the response load amounts W of the items registered in the execution list is equal to or less than a predetermined upper limit TS (S54). This determination is made with reference to the response load value in the property table 142. Here, if the sum of the response load amounts W is less than or equal to the upper limit value TS, all inquiry items registered in the execution list are inquired at the same time (S58).
[0089]
In S54, when the sum of the response load amounts W exceeds the upper limit value TS, among the inquiry items registered in the execution list, the postponable time is set and the lowest priority item is deleted from the execution list. (S56). That is, the deleted query item is postponed by the query. How much the query of the deleted query item is postponed is calculated from the postponable time of the item. That is, for the inquiry item to be deleted, the polling control unit 16 recalculates the inquiry time, for example, by adding a possible turn time to the current time, and registers the result in the schedule table 144 (S56). In this way, deletion of query items is repeated until the sum of response load amounts falls below the upper limit value, and when the sum of response load amounts falls below the upper limit value, the query items registered in the execution list are covered at once. The management device is inquired (S58). Even if the priority is low, a query item for which a postponeable time is not set is not postponed.
[0090]
For example, when the property table 142 is set as shown in the example of FIG. 8, the inquiry time of the inquiry items A, B, and C matches. Here, if the upper limit value TS of the sum of the response load amounts is “8”, it is not possible to inquire all of them simultaneously. In this case, in the present embodiment, the inquiry of the inquiry item C having the lowest priority is postponed, for example, for a time that can be followed later (that is, 20 minutes).
[0091]
According to the present embodiment, when the inquiry times of a plurality of inquiry items match, the response load of the managed device for one inquiry is prevented from becoming too large, and the client 20 inherently sends the managed device to the managed device. It is possible to suppress the deterioration of the response when the job is requested.
[0092]
In the present embodiment, the postponement possible time is determined for each piece of device information, but this is not essential for the present invention. The case where the postponement possible time is set to a constant value regardless of the type of device information is also included in the scope of the present invention. In this case, for the postponed time, for example, the minimum value of the postponed (allowable) time for each piece of device information may be the common postponable time. Even in this aspect, it is possible to sufficiently obtain the effect of reducing the load on the managed device and the network by distributing queries that are too concentrated.
[0093]
Note that, as a modification of the present embodiment, the present embodiment may be combined with the above-described second embodiment. In this modification, both the advance possible time and the postponed possible time can be registered in the property table 142. Then, in the same manner as in the second embodiment, in addition to the query time coming, query items that can be moved forward are also registered in the execution list (S30 in FIG. 7). If the total response load amount of the query items registered in the execution list exceeds the upper limit TS, a postponable time is set and priority is set among all the query items in the execution list The lowest one is postponed.
[0094]
According to this modified example, it is possible to make an inquiry earlier with a higher priority among inquiry items concentrated within a certain period of inquiry time.
[0095]
The device management server 10 according to each embodiment described above can be realized by causing a computer system such as a personal computer or a workstation to execute a program describing each function described above. This program can be provided to the customer in a form recorded on a recording medium such as a floppy disk or a CD-ROM. When the customer installs the program recorded on the recording medium in a fixed disk device attached to the computer system owned by the customer, the device management server 10 according to each of the above embodiments is constructed. That is, the computer system performs the function of the device management server 10 by loading the installed program into the main memory and executing it by the CPU.
[0096]
In each of the above embodiments, the case where the managed device is a printer or a multifunction device has been described. However, it is obvious that the present invention can be applied to other managed devices.
[0097]
【The invention's effect】
As described above, in the present invention, when the deviation of the inquiry time between the pieces of device information is small (that is, the deviation is within an advanceable time), the device information management apparatus inquires the device information group all at once, It is possible to reduce the response load of the managed device, and to suppress a decrease in processing efficiency of the original business / processing of the managed device due to the inquiry of the device information.
[0098]
Further, according to the present invention, when the sum of the response load amounts of the device information group to be inquired at the same time becomes too large, the inquiry of a part of the device information is carried down by a predetermined delay time, so that the response of the managed device at that time A temporary increase in load can be avoided, and a reduction in the efficiency of the original processing of the managed device during that time can be prevented.
[Brief description of the drawings]
FIG. 1 is a diagram showing a system configuration example using a device management server according to the present invention.
FIG. 2 is a diagram showing the contents of a property table in the first embodiment.
FIG. 3 is a diagram showing the contents of a scheduling table.
FIG. 4 is a diagram showing a basic processing procedure of a device management server according to the present invention.
FIG. 5 is a diagram illustrating a detailed procedure of an inquiry process of a polling control unit in the device management server according to the first embodiment.
FIG. 6 is a diagram showing the contents of a property table in the second embodiment.
FIG. 7 is a diagram illustrating a detailed procedure of inquiry processing of a polling control unit in the device management server according to the second embodiment.
FIG. 8 is a diagram illustrating the contents of a property table in the third embodiment.
FIG. 9 is a diagram illustrating a detailed procedure of inquiry processing of a polling control unit in the device management server according to the third embodiment.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 10 Device management server, 12 Device information inquiry reception part, 14 Polling database, 16 Polling control part, 18 Equipment information collection part, 20 Client, 22 Printer, 24 MFP, 26 Network, 142 Property table, 144 Scheduling table.

Claims (8)

A device information management device that periodically inquires each device information that the device has to the managed device and manages the device information group acquired as a result,
For each device information, an inquiry cycle table in which the device information inquiry cycle is registered,
Based on the query cycle table, determine a query time for the query for each device information, and a scheduling means for registering in the scheduling table;
Referring to the scheduling table every predetermined time, and if there is device information for which the inquiry time has arrived, inquiry means for making an inquiry of the device information to the managed device;
A forward possible time storage means for storing, for each piece of equipment information, a possible advance time that can be advanced from the time determined according to the inquiry cycle by the inquiry means;
And when the inquiry unit makes an inquiry about the device information to the managed device, the inquiry unit includes the information on the advanceable device information whose inquiry time comes within the advanceable time corresponding to the device information from the current time. A device information management apparatus characterized by checking presence / absence by referring to the scheduling table, and inquiring forward-possible device information at the same time as device information at which an inquiry time has arrived when there is advance-possible device information. The apparatus of claim 1 , comprising:
A query response load table in which the response load amount of the managed device for the device information query is registered for each device information,
The inquiry means refers to the inquiry response load table, and when the device information is inquired to the managed device, the advanceable device information to be inquired simultaneously is summed up of the response load amount of the managed device by the inquiry. Is selected within a range that is less than or equal to a predetermined upper limit value. The apparatus of claim 2 , comprising:
A query priority table in which the query priority of the device information is registered for each device information;
The inquiry means refers to the inquiry priority table when selecting the advanceable device information to be simultaneously inquired when making device information inquiry to the managed device, and the advancement with high inquiry priority is possible. A device information management apparatus, wherein device information is preferentially selected. The apparatus of claim 1 , comprising:
A query characteristic table in which the response load amount of the managed device and the query priority of the device information are registered by querying the device information for each device information;
The inquiry means refers to the inquiry characteristic table, the advanceable device information to be simultaneously inquired when making device information inquiry to the managed device, the response load amount of each advanceable device information, and the A device information management apparatus, which is selected based on inquiry priority. A device information management device for periodically inquiring each device information of the device to the managed device and managing the device information acquired as a result,
For each device information, an inquiry cycle table in which the device information inquiry cycle is registered,
An inquiry response load table in which the response load amount of the managed device for the inquiry of the device information is registered for each device information;
Based on the query cycle table, determine a query time for the query for each device information, and a scheduling means for registering in the scheduling table;
Referring to the scheduling table every predetermined time, and if there is device information for which the inquiry time has arrived, inquiry means for making an inquiry of the device information to the managed device;
A post-rotatable time storage unit that stores a postponeable time that can be postponed from the time determined by the interrogation period according to the query cycle;
And the inquiry means refers to the inquiry response load table when there are a plurality of pieces of device information whose inquiry time has arrived when referring to the scheduling table, the response load amount for each piece of device information. Of the pieces of device information to be simultaneously queried at that time is selected within a range where the sum of the response loads is equal to or less than a predetermined upper limit, and the remaining pieces of device information are registered in the scheduling table. A device information management apparatus characterized in that the time is decremented by a postponable time corresponding to the device information. The apparatus according to claim 5 , comprising:
A query priority table in which the query priority of the device information is registered for each device information;
The inquiry means refers to the inquiry priority table when selecting the appliance information to be inquired at the same time, and selects the appliance information with the higher inquiry priority preferentially. Computer
For each device information that the managed device has, an inquiry cycle table in which the inquiry cycle of the device information is registered,
Based on the inquiry cycle table, a scheduling means for determining an inquiry time for making an inquiry for each device information and registering in the scheduling table;
Advanceable time storage means for storing, for each piece of equipment information, an advanceable time that allows the inquiry time by the inquiry means to be moved forward from a time determined according to the inquiry cycle;
Refers to the scheduling table every predetermined time, and if there is device information for which the inquiry time has arrived, inquiry means for inquiring device information to the managed device, the device to the managed device When making an inquiry about information, the presence or absence of advanceable device information whose inquiry time comes within the advanceable time corresponding to the device information from the current time is checked by referring to the scheduling table, and there is advanceable device information Inquiry means for inquiring about information on devices that can be brought forward at the same time,
A computer-readable recording medium on which a program for functioning as a computer is recorded. Computer
For each device information that the managed device has, an inquiry cycle table in which the inquiry cycle of the device information is registered,
For each device information, an inquiry characteristic table in which the response load amount of the managed device with respect to the device information inquiry and the inquiry priority of the device information are registered,
Based on the inquiry cycle table, a scheduling means for determining an inquiry time for making an inquiry for each device information and registering in the scheduling table;
A post-rotatable time storage unit that stores a postponeable time that can be postponed from a time determined according to the query cycle by the interrogation unit, for each piece of device information;
Refers to the scheduling table every predetermined time, and if there is device information for which the inquiry time has arrived, inquiry means for inquiring the device information to the managed device, and when the scheduling table is referenced, If there is a plurality of device information for which the inquiry time has arrived, refer to the inquiry response load table to determine the response load amount for each of those device information, and among those device information, what is simultaneously inquired at that time, In order from the highest query priority, the total response load amount is selected within a predetermined upper limit value, and the remaining device information corresponds to the inquiry time registered in the schedule table. Inquiry means to defer by the possible postponed time,
A computer-readable recording medium on which a program for functioning as a computer is recorded.

Images