US20040107188A1

US20040107188A1 - System and method for harvesting of data from peripheral devices

Info

Publication number: US20040107188A1
Application number: US10/308,761
Authority: US
Inventors: Michael Hardcastle
Original assignee: Hewlett Packard Development Co LP
Current assignee: Hewlett Packard Enterprise Development LP
Priority date: 2002-12-03
Filing date: 2002-12-03
Publication date: 2004-06-03
Also published as: US7483897B2

Abstract

In one embodiment there is disclosed a system and method for harvesting data from at least one device, by canvassing said devices and tracking which canvassed devices yielded harvested data and then repeating such canvassing and tracking until either data has been obtained from all of the devices, or a certain time has passed since the beginning of the canvassing period. In a further embodiment, when data has been obtained from all the devices or the time has passed, whichever comes first, the harvested data is sent to a central processing center.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to commonly-assigned U.S. patent application [Attorney Docket No. 100204478-1] entitled “SYSTEM AND METHOD FOR THE HYBRID HARVESTING OF INFORMATION FROM PERIPHERAL DEVICES”, the disclosure of which is hereby incorporated by reference herein.[0001]

FIELD OF THE INVENTION

This invention relates to the harvesting of data from remote devices and more particularly to a system and method for the efficient harvesting of such data using windows of opportunity.

DESCRIPTION OF RELATED ART

It has become common practice to electronically retrieve, or harvest, parametric information, for example, the amount of consumables, such as ink and paper from a printer, page counts, media types and usage, error conditions, current state, and the like from peripheral devices. These peripherals can be, for example, printers, plotters, scanners and the like.

The above-identified co-pending patent application is one example of a data harvesting system and method. Such systems and methods require that the peripheral device is turned on and on-line at the time the data harvesting is to occur. In many situations, the peripheral is off-line, meaning that external communication can not be achieved at that point of time. Sometimes the peripheral is simply turned off. It therefore follows that when the peripheral is not available for the harvesting of data, the effectiveness of the harvesting system is impaired.

For example, assume that one of the purposes of the data harvesting system is to monitor the ink and/or paper usage of a group of printers and to then provide additional ink, and/or other supplies for use at the various printers when required. Also assume that when the data harvesting occurs, one or more of the printers is off-line, unpowered, or otherwise unavailable. In such a situation, the ability to timely replenish the necessary supplies is diminished.

BRIEF SUMMARY OF THE INVENTION

In one embodiment there is disclosed a system and method for harvesting data from a plurality of devices, by canvassing said plurality of devices and tracking which canvassed devices yielded harvested data and then repeating such canvassing and tracking until either data has been obtained from all of the plurality of devices, or a certain time has passed since the beginning of the canvassing period. In a further embodiment, when data has been obtained from all the devices or the time has passed, whichever comes first, the harvested data is sent to a central processing center.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows one embodiment of a system using the incentive concepts; [0007]
FIG. 2 show several sub-harvest times within a interval; and; [0008]
FIG. 3 is a flow chart showing the method of operation of one embodiment of the invention.[0009]

DETAILED DESCRIPTION

Turning now to FIG. 1, there is shown [0010] system 10 in which processor 11 is shown in conjunction with database 13 adapted for harvesting data from a plurality of peripheral devices P1-PN via network 12. The harvested information from peripherals P1-PN is stored, in one embodiment, temporarily in database 13 and then communicated under control of processor 11 to processing center 14 at a location remote from the peripheral devices.
Note that using the system and method of this invention, [0011] processor 11 may gather data from one peripheral P1 or from a group of peripherals, with the gathered data being stored in database 13 for a period of time. This system could be established such that several groups or nodes, such as node 100, of peripherals can have data harvested therefrom with the data being stored in database 13. Then, at some period of time, such as when it is convenient for a user or at a scheduled time, the harvested data is transmitted from database 13 via network 12 to processing location 14. Processing location 14 can be, for example, a system which keeps track of the consumables, such as ink and paper use in printing or other peripheral devices, so that a central location can re-supply the consumables to each device as necessary. This allows for the proper operation and maintenance of peripheral devices P1-P11 from a location remote therefrom. As shown, processing location 14 can, if desired, receive data from several nodes, for example, from node 101 via network 12-1. Of course, it would be understood that network 12-1 and network 12 could be one in the same or could be separate networks if desired.
Turning now to FIG. 2, there is shown one [0012] harvest interval 200 which could occur once a day, twice a day, or as often as the system administrator decides. In operation, once the harvest interval time opens, the system attempts to harvest data from all or some portion of the peripheral devices that are in the group of devices to be harvested at that time. This is accomplished during the first sub-harvest interval 20. The data that is harvested is stored in database 13, as discussed above. Any peripheral device P1-PN at node 100 that does not respond to the request for data is annotated or stored in database 13-1. Database 13-1 is the “not found” database, meaning that the identity of the peripheral devices stored therein are devices from which data has not been harvested at this harvest interval.
At some period of time after the beginning of the first sub-harvest interval, a [0013] second sub-harvest interval 21 begins. Second sub-harvest interval 21 can overlap first sub-harvest interval 20, as shown in FIG. 2, or could begin after the end of first sub-harvest interval 20. In a preferred embodiment, the sub-harvest intervals 20, 21, 22, begin one hour apart. However, for different situations this spacing can be changed and, in fact, the different subintervals can be variably spaced such that the second harvest interval 21, for example, could start one hour after the first harvest interval 20 started, while the third sub-harvest interval 22 could start four hours after the first sub-harvest interval 20 started. These numbers are arbitrary and designed to maximize the potential for obtaining data from as many of the devices as possible during each harvest interval 200. Of course, it should be noted that while three sub-intervals are shown, any number of sub-intervals could be utilized for a particular harvest interval 200. The purpose being that the peripheral devices are turned off at some times and, thus are unavailable for the harvesting of data. The harvest interval itself is selected so as to maximize the likelihood that a maximum number of peripheral devices within the node are on at the time of the data harvesting.
Continuing in FIG. 2, at the time set for the beginning of the second sub-harvest of data from [0014] node 100 the system would determine from “not found” database 13-1 the identity of the peripherals that have not been available in prior harvesting subintervals. These previously “not found” peripherals would then be targeted for the harvesting of data. Again, during the second sub-harvest interval, information that is harvested is stored in database 13. The identity of any peripheral that responds in the second sub-interval is removed from database 13-1. This procedure is repeated for the third and any subsequent sub-harvest subintervals, until either there are no peripheral device identifiers remaining in “not found” memory 13-1 or the end of harvest interval 200 has occurred, whichever comes first. At that point, database 13, under control of processor 11, sends the information that has been harvested from peripheral devices P1-PN through network 12 to processing system 14 such that the harvested information can be processed as desired.
Turning now to FIG. 3, there is shown [0015] flowchart 30 which illustrates one embodiment of the invention. Process 301 determines if a harvest window (i.e. time for polling peripheral devices) is open. This would be the beginning of harvest interval 200, shown in FIG. 2. If it is not time, then nothing is done and the system continues to wait until it is time for the beginning of harvest interval 200 under control of process 301. When it is time for the start of harvest interval 200, process 302 starts a new sub-harvest by obtaining the not-found list via process 306 in conjunction with database 13-1. This could be a list of all the peripherals at node 100 that are to be polled at this period of time, which may be transferred to the not-found list at the beginning of each sub-harvest. This list could change based upon statistics, or based upon an operator-established number, or can be constant so that all peripherals in the node are harvested during each harvest interval.
[0016] Process 307 determines whether or not a particular peripheral has responded successfully. If it has not responded, the next peripheral identity is obtained from the not-found list via process 308. If the peripheral does respond, via process 307, then the results are stored via process 309 in database 13, and the identity of the peripheral is removed from the not-found list via process 310. Process 311 determines if a complete pass has been made through the not-found list. If a complete pass has been made, then process 312 determines if the polling is finished, which means that all of the peripherals have responded for this node and that no peripheral identifications remain in “not found” memory 13-1. If a complete pass has not been made (process 311) then the next peripheral information is obtained, via processes 308 and the system continues. If polling is finished, via process 312, then the results that have been stored in database 13 are sent to remote processing location 14, as discussed above, via process 313.
In most situations, there will be at least one peripheral device which was not available during [0017] first subinterval 20 as determined by process 312. In such a situation, the identity of such devices would remain in the not-found list. Process 314 (optional) determines if a certain time has elapsed since the previous polling. If that has not occurred, then nothing is done at this point and the system continues to wait for the proper time lapse. When it is time for a new sub-harvest, via process 314, then second sub-harvest interval 21, as shown in FIG. 2, begins via processes 303 and 302 and the system obtains the peripheral information from “not found” list 13-1 via process 306 as discussed above. The peripherals identified within that database are then polled and processes 307, 308, 309, 310, 311, 312, 314, 303 and 302 repeat as many times as are necessary until all of the peripherals identified in “not found” memory 13-1 have been polled during the second sub-harvest interval, or until process 303 determines that the harvest interval is closed.
When [0018] process 303 determines that the harvest window is closed, process 304 stops the sub-harvest and process 305 clears “not found” memory 13-1. At that point, the information in database 13 is available to be sent to processing location 14 via process 313.
[0019] Process 322 can establish the time for polling based upon user input 320 or based upon an analyst of data which has been obtained from database 13 over a period of time via process 321. This could be a statistical analysis to determine which times are most profitable for the obtaining of data and how many iterations are necessary and how long apart should they be spaced. For example, it could be determined that during weekdays certain times are optimal for harvesting and that during weekends different times should be utilized. If this were the case, then the internal harvest start times would be adjusted as would the harvest subintervals to take into account the best times and intervals to be utilized.

Claims

What is claimed is:

1. A method for harvesting data from at least one device, said method comprising:

canvassing said at least one device in order to obtain data therefrom;

tracking canvassed devices that have yielded data; and

repeating said canvassing and tracking steps until the first to occur of the following:

1) data has been obtained from all of said at least one device, or

2) a certain time has passed since the beginning of said first canvassing step.

2. The method of claim 1 further including:

communicating, at the conclusion of said repeating step, to a processing center all of said obtained data.

3. The method of claim 1 further including:

establishing, prior to said first canvassing step, a window of opportunity during which it is anticipated the devices to be canvassed will be available for such canvassing; said window of opportunity coinciding with said certain time.

4. The method of claim 3 wherein said window of opportunity is established based in part upon statistical information generated pertaining to availability of said devices.

5. The method of claim 4 wherein said devices are printers.

6. The method of claim 4 wherein said devices are printers and said data pertains, at least in part, to consumables used by said printers.

7. The method of claim 1 wherein said devices are printers.

8. The method of claim 7 wherein said devices are printers and said data pertains, at least in part, to consumables used by said printers.

9. A system for harvesting information from groups of peripheral devices, said devices arranged into at least one node, each said node having at least one device, said system comprising:

means at each said node for harvesting data during harvesting intervals from peripheral devices in communication with said node and for storing said harvested data, at least temporarily, at said node;

said harvesting means comprising:

means for keeping track of devices that are not available at a specific harvest time within said harvest interval;

means operable at intervals for reharvesting data from ones of said devices that were not available at a last harvest time within said specific harvest interval;

means for repeating said reharvesting of data until data has been harvested from all devices; and

means operable at the conclusion of each said harvest interval for ending said harvesting interval and for sending to said system all data harvested from said node during said harvest interval.

10. The system of claim 9 wherein said system further comprises:

means at said location for processing said data harvested from said nodes so as to provide services to said peripheral devices under control of said system.

11. The system of claim 10 wherein said peripheral devices are printers and wherein said provided services include keeping track of consumables at each said printer.

12. The system of claim 9 wherein said harvest interval is establish to fall within a time of high probability of the availability of said devices to have data harvested therefrom.

13. The system of claim 12 wherein said harvesting interval is derived, at least in part, by one of the following:

manual setting of start times, automatic setting of start times based on statistical analysis of past availability times, combination of start times and statistically based calculated times.

14. The system of claim 12 wherein the reharvesting times within a reharvesting interval are adjustable.

15. The system of claim 14 wherein said harvesting intervals are adjustable.

16. The system of claim 9 wherein the reharvesting times within a reharvesting interval are fixed periods.

17. The system of claim 16 wherein said harvesting intervals are adjustable.

18. A method for gathering consumable data from at least one device, said device having time constraints around which said consumable data can be gathered, said method comprising:

establishing a periodic time window for gathering said data, said time window optimized around the time constraints of said devices;

establishing within said time window a plurality of sub-time windows;

attempting, during a first one of said sub-time windows, to gather data from all of said devices; and

attempting, during each subsequent sub-time window of a periodic time window, to gather data from all devices that were not available during prior sub-time windows of said periodic time window.

19. The method of claim 18 further comprising:

transmitting said gathered data to a processing center remote from said devices when data has been gathered from all of said at least one device.

20. The method of claim 18 further comprising:

transmitting said gathered data to a processing center remote from said device at the expiration of all of said sub-time windows of a given time window.