METHODS AND SYSTEMS FOR SOFT FAILURE DETECTION FOR NETWORKED PRINTERS

• US 20080246987A1
• Filed: 04/04/2007
• Published: 10/09/2008
• Est. Priority Date: 04/04/2007
• Status: Active Grant

• Current Assignee: Xerox Corporation (Xerox Holdings Corp.)
• Original Assignee: Xerox Corporation (Xerox Holdings Corp.)
• Inventors: Scrafford, Matthew, Bouchard, Guillaume, Pothos, Kirk, Ciriza, Victor, Kammerdiener, Shawn, Valobra, Pascal, Marquie, Bruno
• Granted Patent: US 8,902,450 B2
• Time in Patent Office: Days
• US Class Current: 358/1.15
• CPC Class Codes: G03G 15/5075 Remote control machines, e.g. by a host
• CPC Class Codes: G03G 15/5079 for maintenance
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 11/0733 in a data processing system embedded in an image processing device, e.g. printer, facsimile, scanner
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 3/121 Facilitating exception or error detection and recovery, e.g. fault, media or consumables depleted
• CPC Class Codes: G06F 3/1259 Print job monitoring, e.g. job status
• CPC Class Codes: G06F 3/1273 Print job history, e.g. logging, accounting, tracking
• CPC Class Codes: G06F 3/1288 in client-server-printer device configuration
• CPC Class Codes: G06F 3/1294 Status or feedback related to information exchange

Abstract

Methods and systems are presented for identifying potential printer failures in a networked printing enterprise, in which job tracking data is gathered for print jobs in the network, affinity data is derived from the job tracking data indicating associations between printer devices and user devices, and potential printer failures are identified based on changes in the affinity data.

Claims

1. A method for identifying potential printer failures in a networked printing system, the method comprising:

gathering job tracking data for print jobs in a network; and

identifying potential printer failures based at least partially on the job tracking data.

2. The method of claim 1, wherein identifying potential printer failures comprises:

determining affinity data indicating associations between printer devices and user devices based on the job tracking data;

determining changes in the affinity data; and

identifying potential printer failures based at least partially on the changes in the affinity data.

3. The method of claim 2, wherein identifying potential printer failures based at least partially on the changes in the affinity data comprises identifying a first printer device as having a potential failure if the affinity data indicates a change in user preference away from the first printer device.

4. The method of claim 2, wherein identifying potential printer failures comprises identifying a potential failure in a first printer device if a change in the affinity data associated with the first printer device exceeds a threshold value.

5. The method of claim 1, wherein identifying potential printer failures comprises identifying a first printer device as having a potential failure if the job tracking data indicates a change in user preference away from the first printer device.

6. The method of claim 1, wherein identifying potential printer failures comprises identifying a first printer device as having a potential failure if the job tracking data indicates that at least one user has substantially stopped printing to the first printer device in favor of another printer.

7. A method of detecting a change in pattern of use of networked printers, comprising:

gathering job tracking data for print jobs in a network;

determining affinity data indicating associations between printer devices and user devices based on the job tracking data;

determining changes in the affinity data; and

detecting a change in pattern of use of a first printer device based on a change in the affinity data associated with the first printer device.

8. The method of claim 7, further comprising identifying a potential failure in the first printer device if the detected change in the pattern of use of the first printer device exceeds a threshold value.

9. The method of claim 7, further comprising identifying a first printer device as having a potential failure if the detected change in the pattern of use of the first printer device indicates a change in user preference away from the first printer device.

10. The method of claim 7, further comprising identifying a first printer device as having a potential failure if the detected change in the pattern of use of the first printer device indicates that at least one user has substantially stopped printing to the first printer device in favor of another printer device.

11. A system for identifying potential printer failures in a networked printing system, comprising:

an affinity component operative to gather job tracking data for print jobs in the network; and

a failure detection component operative to identifying potential printer failures based at least partially on the job tracking data.

12. The system of claim 11, wherein the affinity component is operative to determine affinity data indicating associations between printer devices and user devices based on the job tracking data, and wherein the failure detection component determines changes in the affinity data, and identifies potential printer failures based at least partially on the changes in the affinity data.

13. The system of claim 12, wherein the failure detection component identifies a first printer device as having a potential failure if changes in the affinity data indicate a change in user preference away from the first printer device.

14. The system of claim 13, wherein the affinity component and the failure detection component are implemented in at least one software program running on a network server.

15. The system of claim 12, wherein the failure detection component identifies a potential failure in a first printer device if a change in the affinity data associated with the first printer device exceeds a threshold value.

16. The system of claim 12, wherein the affinity component and the failure detection component are implemented in at least one software program running on a network server.

17. The system of claim 11, wherein the failure detection component identifies a first printer device as having a potential failure if the job tracking data indicates a change in user preference away from the first printer device.

18. The system of claim 11, wherein the failure detection component identifies a first printer device as having a potential failure if the job tracking data indicates that at least one user has substantially stopped printing to the first printer device in favor of another printer device.

19. The system of claim 11, wherein the affinity component and the failure detection component are implemented in at least one software program running on a network server.