|Publication number||US6310692 B1|
|Application number||US 09/079,362|
|Publication date||Oct 30, 2001|
|Filing date||May 15, 1998|
|Priority date||May 15, 1998|
|Publication number||079362, 09079362, US 6310692 B1, US 6310692B1, US-B1-6310692, US6310692 B1, US6310692B1|
|Inventors||Shengkuo Fan, Yasuo Nakajima, Joseph Fung, Shee-Yen Tan|
|Original Assignee||Kuji Xerox Co. Ltd., Xerox Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (5), Referenced by (102), Classifications (12), Legal Events (7)|
|External Links: USPTO, USPTO Assignment, Espacenet|
1. Field of Invention
This invention relates to the management of printer resources in a print management system. In particular, this invention is directed to dynamic, preventive monitoring of printer resources, and centralizing the supervision of printer resources.
2. Description of Related Art
Print management systems provide a method for controlling and accessing various printers, as well as managing printer resources and other related information, from both proximate and remote locations. However, in the current print management systems, problems arising with printer resources, such as paper supply, toner or ink level, and drum quality, are not resolved until after the problems arise. For example, a system administrator or user located remotely from a printer is not aware of a “low paper” level for that printer until the paper tray is entirely empty. At that point, the printer will not operate until the paper supply is replenished. Thus, any print jobs already sent to the printer will not be printed until the paper supply is replenished. This problem is quite common and causes significant inconvenience and time delay.
As shown in FIG. 1, the basic conventional print management system 10 uses a client/server architecture that includes three primary components: a client 20, a server 40, and an output device 50. The client 20 conveys print and management requests to the server 40 and receives responses from the server 40 that arise in response to the submitted requests. In general, although not shown in FIG. 1, in these conventional print management systems, a large number of clients 20 will be connected to the server 40. Similarly, although not shown in FIG. 1, a large number of output devices 50 are usually connected to the server 40 and are located at widely distributed locations. The users of the clients 20 can include system administrators, system operators, and other end users.
The server 40 receives these requests from the clients 20, performs the required actions for each request, and returns the responses to the corresponding client 20. One such request from a client 20 is a print request, i.e., a request to print one or more copies of one or more documents, with the printed pages output using one or more features. The features can include simplex or duplex printing, stapling or binding, and the like. Thus, a print request represents a collection of one or more documents to be printed, as well as instructions for printing. The server 40 organizes the documents indicated in the print request submitted by the client into a print job. The server then sends the print job and any associated job control commands to the requested one of the output devices 50.
Each of the output devices 50 is a physical device, or hardware, that is capable of rendering images of documents and producing hard copy output of the print jobs received from the server 40. Each output device 50 can then return responses to the server 40 regarding its current state or the status of the received print jobs. The output device 50 is commonly a printer.
Recently, more efficient print management systems have been developed. The efficient distribution of print jobs in a print management system is described, for example, in U.S. patent application Ser. No. 08/966,404, filed Nov. 7, 1997, and incorporated herein by reference in its entirety.
As shown in FIG. 2, the incorporated '404 application discloses a network print management system 100. The network print management system 100 includes a network server 140, a number of clients 120 and a number of printers 150, although FIG. 2 shows only one such client 120 and printer 150. The network server 140 includes a spooler 142 and a supervisor 146. The supervisor 146 present on the network server 140 can detect and report printer problems, such as a paper jam or an empty paper tray. However, as discussed above, these problems are not detected and reported until after the problem has disabled the particular printer 150. A system administrator or user would then have to respond to the printer problem. Until the problem is resolved, the disabled printer 150 is inoperable. Thus, the network print management system 100 may become backlogged with print jobs. The print jobs already submitted to the disabled printer 150 will wait in the queue 144 until the problem is resolved.
Also, as shown in FIG. 2, the network print management system 100 includes a database 160 for storing system attributes. The term “attributes” refers to the characteristics of print jobs, documents, logical printers, and physical printers. The database 160 is used to store attributes representing fixed reference values, as well as attributes representing system characteristics that are continuously updated as the print management system dynamically changes.
Thus, the attributes are collections of data that describe the entities that form the network print management system 100. In other words, the attributes define or characterize print management systems abstract entities, or objects. For example, document attributes, such as plex, margin, orientation, etc., describe how the printed material should appear. Printer attributes, such as media-ready, fonts-ready, etc., describe the available resources or features of the printer. Other printer attributes may describe the various printing features that users may use to produce high-quality documents, or they may describe status or configuration information, such as the printer's state or location. In addition to these attributes, there are a suite of attributes to facilitate end user, operator and administrator functions. In summary, the attributes are a set of data that describes the objects of the printer management system 100.
System administrators, end users, and vendors need to manage printer resources such as paper supply, toner/ink levels, and drum quality. They need to replace the paper supply, replace ink/toner cartridge, and change the drum before the supplies become completely exhausted. If one or more of these resources become completely exhausted, the printer will not operate until the problem is resolved. Presently, the only way to monitor the printer resources is to travel to the location of each printer and observe that printer and any display on that printer. Thus, monitoring the status of these printer resources is tedious in a network environment, because the printers can be located in a plurality of locations remote from the system administrator.
This invention provides a method and apparatus for dynamic, preventive monitoring of printer resources and for centralizing the supervision of printer resources.
This invention further provides a graphical user interface window that allows the system administrator to view and manage these resources for one or more output devices remotely from the various output devices.
This invention also provides a set of graphical user interface windows to notify the system administrator, and possibly end users, when the status of one of the output devices changes, and of the changed attribute.
Dynamic, preventive monitoring is accomplished by a print management system that dynamically monitors the printer resources and sends warning messages to system administrators, end users, and/or vendors when a printer resource falls below a predetermined threshold. Thus, the problem could be investigated by the administrator, user, or vendor, and resolved prior to the printer resource becoming entirely exhausted.
Additionally, the printer resources can be monitored from a single, centralized location, such as a graphical user interface window providing a control panel on a client being used by the system administrator. Graphical user interface windows providing printer resource warnings can also be electronically displayed on the clients being used by the end users, the system operators, and/or vendors.
These graphical user interface windows can provide advanced warning messages which allow the system administrator to schedule printer maintenance for required, but previously unscheduled, repairs or for standard maintenance. This avoids printer down-time and improves the overall efficiency of the print management system.
These and other features and advantages of this invention are described or are apparent from the following detailed description of the preferred embodiments.
The preferred embodiments of this invention will be described in detail, with reference to the following drawings, wherein like numerals represent like elements and wherein:
FIG. 1 is a diagram of a simple, conventional print management system;
FIG. 2 is a diagram of a more complex, conventional print management system;
FIG. 3 is a diagram of a print management system including a printer resource management system according to this invention;
FIG. 4 is a flowchart outlining one method of printer resource management according to this invention;
FIGS. 5 and 9 show control panel graphical user interface windows usable to remotely view the attributes and status of the output devices according to this invention; and
FIGS. 6-8 and 10-12 show exemplary notification message graphical user interface windows usable to notify a user or system administrator of changes in an output device's status and/or attribute according to this invention.
The following embodiments illustrate dynamic, preventive monitoring of printer resources, and centralizing of the supervision of printer resources in network printing systems. However, the use of this invention in network printing systems is only an exemplary illustration. The dynamic, preventive monitoring of printer resources, and centralizing of the supervision of printer resources may be applied to any document output system.
FIG. 3 illustrates a print management system including a printer resource management system of this invention. The print management system 200 includes a number of clients 220, a server 240, a number of printers 250, and a database 260, although FIG. 3 shows only one such client 220 and one such printer 250. Each printer 250 must be capable of dynamically supplying the printer resource levels to the print management system 200 of the particular network. Each printer 250 should communicate with the print management system 200 via a network management protocol, for example, simple network management protocol (SNMP), and must be capable of resource information recognition.
The server functions are divided between a spooler 242 and a supervisor 246. The spooler 242 also includes a queue 244 to store print jobs waiting to be output. Users of the clients 220 include users having varying levels of authority, such as system administrators, system operators, and other end users.
For each printer 250, two new printer attributes 262 and 264 are added to the database for each printer resource that needs to be monitored. The first new printer attribute 262 for each monitored printer resource corresponds to the dynamically changing printer resource level for that resource. For example, the monitored printer resource can be the printer paper level, the printer image forming device quality level, the printer ink level, the printer toner level, and the like. The second new printer attribute 264 for each monitored printer resource corresponds to the predetermined printer resource threshold for that resource. For example, monitored printer resource can be a printer paper threshold, a printer image forming device quality threshold, a printer ink threshold, a printer toner threshold, and the like.
It should be appreciated that the printer resource management system of this invention can also monitor and notify administrators, end users, and vendors of deficient physical properties of the printers 250, such as a paper jam, an open printer cover, and the like.
The threshold for any monitored printer resource set by the second new printer attribute 264 can be changed by a system administrator or other user with the necessary authority level to invoke such a change. The threshold setting policy may be determined by the system administrator. For example, higher thresholds can be set for more remote printers, as well as for higher volume printers. Thus, the thresholds for each printer can be customized according to printer location, printer capacity, printer workload, configuration of the printing environment, etc.
It should be appreciated that the thresholds can also be dynamically modified by the print management system itself, based on the actual accounting information maintained by the print management system 200.
As shown in FIG. 3, the print management system 200 having this printer resource management system thus includes a printer resource system manager 248. The printer resource system manager 248 resides on the supervisor 246 of the server 240. The printer resource system manager 248 includes a notification profile for each printer and/or for each monitored resource. Through the notification profile, the system administrator or other authorized user can designate which end users and/or vendors will receive notification of a printer resource deficiency, depending on the printer and/or the deficiency. The notification profile can also be used to designate the type of electronic communication will be used to notify the designated end users and/or vendors (i.e., e-mail, direct paging, etc.).
The operation of the printer resource system manager 248 is now described. First, the printer resource system manager 248 obtains the printer resource levels from each printer 250. Information regarding the printer resource levels can be obtained by several methods. Two such methods are a pulling model and a pushing model. In a pulling model, the supervisor 246 periodically extracts printer resource information from each printer. In a pushing model, each printer 250 periodically reports printer resource information to the supervisor 246. The primary difference between the aforementioned models is that in the pushing model, the output device 250 initiates the process of updating the printer resource levels, whereas, in the pulling model, the supervisor 246 initiates the process of updating the printer resource levels. In the pulling model, the time period for the periodical updates can be varied as desired. It can be appreciated that any model capable of performing data acquisition and reporting between printers 250 and a supervisor 246 would be acceptable.
Next, the printer resource system manager 248 updates the printer resource level attributes in the database 260 according to the printer resource information received from the printer 250. The printer resource system manager 248 then compares the attributes for the updated printer resource levels with the attributes for the printer resource thresholds. The printer resource system manager 248 notifies clients 220, designated through the notification profile, of the printer 250 and the corresponding deficient resource level or problem. It should be appreciated that the printer resource system manager 248 continually operates as long as the server 240 is operational.
FIG. 4 is a flowchart outlining one preferred operation of the printer resource management system of this invention. Beginning at step S400, control continues to step S410, where acquisition of printer resource level information is initiated. Next, in step S420, the current printer resource levels are determined. Next, in step S430, the printer resource level attributes are updated according to the current printer resource levels. Then, in step S440, the attributes for the updated printer resource levels are compared with the attributes for the printer resource thresholds.
In step S450, it is determined whether the printer resource level attributes are less than the printer resource level thresholds. If the printer resource level attributes are not less than the printer resource level thresholds, control returns to step S410 for further monitoring of printer resource levels. If the printer resource level attributes are less than the printer resource level thresholds, control proceeds to step S460.
In step S460, a notification of the deficient printer resource level is generated and transmitted. In particular, the notification is generated and transmitted based on the notification profile for the printer experiencing the noteworthy event and/or the type of event. Following step S460, control returns to step S410 for further monitoring of printer resource levels. It should be appreciated that the printer resource management system continually operates as long as the server 240 continues running.
The notification profile can be configured to notify, i.e., transmit the notification to, the system administrator, one or more end users, and/or a vendor of the particular printer resource that is below the threshold. The notification profile is also used to identify the delivery method or transmission type, i.e., e-mail, paging, etc.
Therefore, the system administrator can monitor the status of all printers from a computer console at one central location. Thus, the printer resource system manager 248 eliminates the need for a system administrator, or other network system personnel, to be at each printer to monitor its status.
FIGS. 5 and 9 show a control panel graphical user interface window 500 usable to remotely view the attributes and status of the output devices. The graphical user interface window 500 includes a text scroll box 505 for dynamically displaying system information to a system administrator or other authorized user. As shown in FIGS. 5 and 9, the displayed information may include notification of deficient printer resource levels, printer hardware problems, and changes in printer status. FIGS. 5 and 9 are essentially the same except for the contents of the text scroll box 505.
FIGS. 6-8 and 10-12 show examples of a sequence of notification message graphical user interface windows 590 usable to notify a user or system administrator of changes in an output device's status and/or attributes. As shown in FIGS. 6 and 10, a message 595 is displayed that provides notification that the status of a particular printer 250 has changed. Then, as shown in FIGS. 7 and 11, a message 595 is displayed regarding the specific state of the printer 250, for example, printer needs attention, printer is idle, etc. Next, as shown in FIGS. 8 and 12, a message 595 is displayed to provide notification of the deficiency of the printer 250, as shown in FIG. 8, or to confirm resolution of the deficiency, as shown in FIG. 12.
It should be appreciated that the printer resource system manager 248 can be configured so that once a printer resource falls below the corresponding threshold, the system administrator, end user, and/or vendor will be constantly notified of the warning and a continuous update of the printer resource level will be provided as the level continues to drop.
It should be appreciated that the printer resource system manager 248 can be implemented with multiple thresholds so that a first warning can be provided when a first threshold is reached and subsequent more obvious and/or more critical warnings are provided when each successive threshold is reached.
As shown in FIG. 4, as well as in the example outlined above, the dynamic, preventive, centralized printer resource management system of this invention, implemented by the printer resource system manager 248, is preferably implemented on a programmed general purpose computer. However, the implementation of non-persistent attributes can also be performed on a special purpose computer, a program microprocessor or microcontroller and peripheral integrated circuit elements, and ASIC or other integrated circuit, a hardwired electronic or logic circuit such as a discrete element circuit, a programmable logic device such as a PLD, PLA, FGPA or PAL or the like. In general, any device in which a finite state machine capable of implementing the flow chart shown in FIG. 4 in the example illustrated above can be used to implement the dynamic, preventive, centralized printer resource management system.
While this invention has been described with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, the preferred embodiments of this invention as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of this invention as defined in the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5220674 *||Jan 18, 1990||Jun 15, 1993||Digital Equipment Corporation||Local area print server for requesting and storing required resource data and forwarding printer status message to selected destination|
|US5699493 *||Jun 23, 1995||Dec 16, 1997||Lexmark International, Inc.||Method and apparatus for providing job accounting information to a host computer from a printer|
|US5720015 *||Apr 22, 1996||Feb 17, 1998||Lexmark International, Inc.||Method and apparatus for providing remote printer resource management|
|US5727135 *||Aug 2, 1996||Mar 10, 1998||Lexmark International, Inc.||Multiple printer status information indication|
|WO1994011804A1 *||Nov 9, 1993||May 26, 1994||Microsoft Corporation||Printer status user interface and methods relating thereto|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6672213 *||Jan 27, 2003||Jan 6, 2004||Minolta Co., Ltd.||Printing program and printing system|
|US6801935 *||Dec 14, 1999||Oct 5, 2004||Canon Kabushiki Kaisha||Secure printing using electronic mailbox|
|US6809830 *||Jun 1, 1999||Oct 26, 2004||Microsoft Corporation||Method and system for enabling a printing program to communicate with a printer|
|US6889264||Oct 9, 2002||May 3, 2005||Hewlett-Packard Development Company, L.P.||Imposing a delay for indication of a status board to provide a time for self-rectification of a service event detected from peripheral status information|
|US6947154 *||Feb 28, 2001||Sep 20, 2005||Canon Kabushiki Kaisha||Network device manager|
|US6990381 *||Dec 5, 2002||Jan 24, 2006||Sharp Kabushiki Kaisha||Electrically controlled apparatus|
|US7013482||Jul 7, 2000||Mar 14, 2006||802 Systems Llc||Methods for packet filtering including packet invalidation if packet validity determination not timely made|
|US7031267||Dec 21, 2000||Apr 18, 2006||802 Systems Llc||PLD-based packet filtering methods with PLD configuration data update of filtering rules|
|US7048273||Feb 28, 2002||May 23, 2006||Bowe Bell + Howell Company||System and method for monitoring grouped resources|
|US7127451 *||Jul 31, 2000||Oct 24, 2006||Canon Kabushiki Kaisha||Device searching method, device searching client, device, device searching server, device searching system, device searching apparatus, and storage medium|
|US7191028||Oct 27, 2005||Mar 13, 2007||Sharp Kabushiki Kaisha||Electrically controlled apparatus|
|US7259881 *||Oct 3, 2001||Aug 21, 2007||Kabushiki Kaisha Toshiba||Method of monitoring multiple controller families|
|US7305449 *||Oct 30, 2001||Dec 4, 2007||Hewlett-Packard Development Company, L.P.||Web-based imaging service providing reservation|
|US7343105||Jun 28, 2005||Mar 11, 2008||Ricoh Company, Ltd.||Image forming apparatus and control method of image forming apparatus with operation based upon down event occurrences|
|US7383474 *||Nov 13, 2003||Jun 3, 2008||Seiko Epson Corporation||System and method for monitoring the state of a plurality of machines connected via a computer network|
|US7526795 *||Mar 27, 2001||Apr 28, 2009||Micron Technology, Inc.||Data security for digital data storage|
|US7539785||Jun 30, 2005||May 26, 2009||Canon Kabushiki Kaisha||Network device manager|
|US7540018||Jun 14, 2006||May 26, 2009||Micron Technology, Inc.||Data security for digital data storage|
|US7594257||Sep 14, 2006||Sep 22, 2009||Micron Technology, Inc.||Data security for digital data storage|
|US7756985 *||Jun 16, 2004||Jul 13, 2010||Canon Kabushiki Kaisha||Shared device control method and server-client system|
|US7861094||Aug 11, 2006||Dec 28, 2010||Round Rock Research, Llc||Data security for digital data storage|
|US7861172 *||Jul 28, 2000||Dec 28, 2010||Canon Kabushiki Kaisha||Information processing apparatus, system and method|
|US7884959 *||Oct 24, 2006||Feb 8, 2011||Xerox Corporation||Printing system and method of operating same|
|US7886026 *||Feb 8, 2011||Hewlett-Packard Development Company, L.P.||Hardcopy output engine configuration apparatus and method|
|US7921175||Aug 6, 2004||Apr 5, 2011||Canon Kabushiki Kaisha||Requesting a service from a service providing apparatus by a service request apparatus|
|US7979720||Sep 20, 2006||Jul 12, 2011||Round Rock Research, Llc||Data security for digital data storage|
|US8191159||Sep 10, 2009||May 29, 2012||Micron Technology, Inc||Data security for digital data storage|
|US8301751 *||Jun 30, 2005||Oct 30, 2012||International Business Machines Corporation||Generation of a master schedule for a resource from a plurality of user created schedules for the resource|
|US8314965||Nov 20, 2012||Emerge Print Management, Llc||Patrol device field installation notification method and system|
|US8330984||Dec 11, 2012||Emerge Paint Management, LLC||Field metering patrol system and method for metering and monitoring printers|
|US8458784||Jun 4, 2013||802 Systems, Inc.||Data protection system selectively altering an end portion of packets based on incomplete determination of whether a packet is valid or invalid|
|US8477332 *||Dec 28, 2004||Jul 2, 2013||Konica Minolta Business Technologies, Inc.||System and method for user management|
|US8498017||Sep 8, 2010||Jul 30, 2013||Xerox Corporation||Method for generating a soft proof for a plurality of color printers|
|US8508764||Nov 15, 2001||Aug 13, 2013||Heidelberger Druckmachinen Ag||Method for transmitting data of a printing press and diagnostic device|
|US8533491||Jul 11, 2011||Sep 10, 2013||Round Rock Research, Llc||Data security for digital data storage|
|US8578066||Sep 17, 2004||Nov 5, 2013||Hewlett-Packard Development Company, L.P.||Supply status indicator|
|US8676957 *||Sep 22, 2003||Mar 18, 2014||Ricoh Co., Ltd.||Method and system for remote diagnostic, control, and information collection based upon a connection or connectionless communication method for sending messages to the resource manager|
|US8879427||Oct 25, 2010||Nov 4, 2014||802 Systems Inc.||Methods for updating the configuration of a programmable packet filtering device including a determination as to whether a packet is to be junked|
|US8949417||Nov 21, 2012||Feb 3, 2015||Ricoh Co., Ltd.||Method and system for remote diagnostic, control, and information collection based upon a connection or connectionless communication method for sending messages to the resource manager|
|US9003177||May 25, 2012||Apr 7, 2015||Micron Technology, Inc.||Data security for digital data storage|
|US9106522||Nov 13, 2014||Aug 11, 2015||Ricoh Company, Ltd.||Method and system for remote diagnostic, control, and information collection based upon a connection or connectionless communication method for sending messages to the resource manager|
|US9117095||Sep 9, 2013||Aug 25, 2015||Round Rock Research Llc||Data security for digital data storage|
|US9268509||Nov 12, 2014||Feb 23, 2016||Printreleaf, Inc.||Automated computer controlled system for measuring the consumption of printer resources and transacting environmental offsets|
|US20010013063 *||Jan 3, 2001||Aug 9, 2001||Hall David M.||System and method for applying printer-specific formatting|
|US20020026541 *||Aug 30, 2001||Feb 28, 2002||Ricoh Company, Ltd.||Remote control system, method and storage medium for image forming apparatus|
|US20020054321 *||Feb 28, 2001||May 9, 2002||Koji Kikuchi||Data processing apparatus, data processing method and storage medium|
|US20020057456 *||Nov 15, 2001||May 16, 2002||Lucia Dauer||Method for transmitting data of a printing press and diagnostic device|
|US20020072998 *||Dec 8, 2000||Jun 13, 2002||Haines Robert E.||Consumable order-assistance system for computer peripheral devices within a centralized network environment and method for replenishing consumable components|
|US20020080771 *||Dec 21, 2000||Jun 27, 2002||802 Systems, Inc.||Methods and systems using PLD-based network communication protocols|
|US20020080784 *||Dec 21, 2000||Jun 27, 2002||802 Systems, Inc.||Methods and systems using PLD-based network communication protocols|
|US20020083331 *||Dec 21, 2000||Jun 27, 2002||802 Systems, Inc.||Methods and systems using PLD-based network communication protocols|
|US20020105675 *||Jan 18, 2002||Aug 8, 2002||Fuji Photo Film Co., Ltd.||Imaging system and imaging method|
|US20020138558 *||Nov 13, 2001||Sep 26, 2002||Ferlitsch Andrew R.||Managing and processing print jobs in a networked computer environment|
|US20020141588 *||Mar 27, 2001||Oct 3, 2002||Rollins Doug L.||Data security for digital data storage|
|US20020184355 *||Jun 4, 2001||Dec 5, 2002||Deats Kevin A.||Method and system for reporting event data to requesting subscribers|
|US20030025937 *||Jul 30, 2002||Feb 6, 2003||Hewlett Packard Company||Media loading in printing systems|
|US20030046122 *||Aug 29, 2001||Mar 6, 2003||Seymour Richard S.||Systems and methods for managing printing device replaceable components for multiple organizations|
|US20030063310 *||Oct 3, 2001||Apr 3, 2003||Nguyen Truc D.||Method of monitoring multiple controller families|
|US20030074427 *||Oct 11, 2001||Apr 17, 2003||Haines Robert E.||Hardcopy output engine configuration apparatus and method|
|US20030084151 *||Oct 30, 2001||May 1, 2003||Simpson Shell S.||Web-based imaging service providing reservation|
|US20030126318 *||Dec 5, 2002||Jul 3, 2003||Tatsuo Nomura||Electrically controlled apparatus|
|US20030140810 *||Jan 27, 2003||Jul 31, 2003||Minolta Co., Ltd.||Printing program and printing system|
|US20030160377 *||Feb 28, 2002||Aug 28, 2003||Meckes David A.||System and method for monitoring grouped resources|
|US20030184782 *||Mar 27, 2002||Oct 2, 2003||Perkins Gregory E.||Printer driver configured to dynamically receive printer self-description|
|US20030187951 *||Dec 14, 1999||Oct 2, 2003||Ming-Teh Shen||Secure printing using electronic mailbox|
|US20040068549 *||Sep 22, 2003||Apr 8, 2004||Tetsuro Motoyama|
|US20040078694 *||Oct 21, 2002||Apr 22, 2004||Lester Samuel M.||Event detection and message transmission apparatus, systems, and methods|
|US20040098480 *||Nov 13, 2003||May 20, 2004||Hiroaki Sekizawa||System and method for monitoring the state of a plurality of machines connected via a computer network|
|US20040215468 *||Apr 23, 2003||Oct 28, 2004||Doeberl Terrence M.||System and method for managing business machine assets|
|US20040239978 *||May 29, 2003||Dec 2, 2004||Hewlett-Packard Co.||Method and apparatus for tracking a plurality of image devices in a network|
|US20040252329 *||Jun 12, 2003||Dec 16, 2004||Dustin Sorenson||Method and system for monitoring status of printers from a SOHO network client|
|US20050021795 *||Jun 16, 2004||Jan 27, 2005||Canon Kabushiki Kaisha||Shared device control method and server-client system|
|US20050024667 *||May 28, 2004||Feb 3, 2005||Seiko Epson Cororation||Information management device for image formation apparatus and information management method|
|US20050052660 *||Sep 30, 2004||Mar 10, 2005||Xerox Corporation||Method and apparatus for automatic updating of printer configuration and status data|
|US20050237543 *||Jun 30, 2005||Oct 27, 2005||Canon Kabushiki Kaisha||Network device manager|
|US20060002721 *||Jun 28, 2005||Jan 5, 2006||Katsuhiko Sasaki||Image forming apparatus and control method of image forming apparatus|
|US20060036340 *||Oct 27, 2005||Feb 16, 2006||Sharp Kabushiki Kaisha||Electrically controlled apparatus|
|US20060083521 *||Sep 17, 2004||Apr 20, 2006||Hewlett-Packard Development Company, L.P.||Supply status indicator|
|US20060092751 *||Nov 4, 2004||May 4, 2006||Hewlett-Packard Development Company, L.P.||Peripheral management|
|US20060099947 *||Dec 28, 2004||May 11, 2006||Konica Minolta Business Technologies, Inc.||System and method for user management|
|US20060161658 *||Aug 6, 2004||Jul 20, 2006||Canon Kabushiki Kaisha||Request method of service request apparatus|
|US20060182108 *||Apr 17, 2006||Aug 17, 2006||Krumel Andrew K||Methods and systems using PLD-based network communication protocols|
|US20060227363 *||Mar 29, 2005||Oct 12, 2006||Kabushiki Kaisha Toshiba||Apparatus and method for managing print jobs among a plurality of printers|
|US20070005755 *||Jun 30, 2005||Jan 4, 2007||Humphries Marshall L||Managing schedules for monitored resources|
|US20070005959 *||Jun 14, 2006||Jan 4, 2007||Rollins Doug L||Data security for digital data storage|
|US20070014412 *||Sep 14, 2006||Jan 18, 2007||Rollins Doug L||Data security for digital data storage|
|US20070016805 *||Sep 20, 2006||Jan 18, 2007||Klein Dean A||Data security for digital data storage|
|US20070024895 *||Jul 28, 2005||Feb 1, 2007||Clark Gordon R||Push forward print tasking in a computer network|
|US20070067647 *||Aug 11, 2006||Mar 22, 2007||Klein Dean A||Data security for digital data storage|
|US20080013109 *||Jul 11, 2006||Jan 17, 2008||Yen-Fu Chen||Method for Selecting Printers Based On Paper Availability Or Paper Congestion|
|US20080144080 *||Oct 24, 2006||Jun 19, 2008||Xerox Corporation||Printing system and method of operating same|
|US20080309965 *||Jun 14, 2007||Dec 18, 2008||Dex Imaging||Apparatus and method for discovering printers within an enterprise|
|US20100005287 *||Jan 7, 2010||Micron Technology, Inc.||Data security for digital data storage|
|US20110197273 *||Aug 11, 2011||Krumel Andrew K||Real time firewall/data protection systems and methods|
|US20110228314 *||Mar 18, 2010||Sep 22, 2011||Dex Imaging, Inc.||Field Metering Patrol System and Method for Metering and Monitoring Printers|
|US20110228332 *||Sep 22, 2011||Emerge Print Management, Llc||Patrol Device Field Installation Notification Method and System|
|US20120062911 *||Sep 13, 2010||Mar 15, 2012||Xerox Corporation||Method for scheduling color print jobs on a network of configurable color printers|
|EP1612053A2 *||Jun 30, 2005||Jan 4, 2006||Ricoh Company, Ltd.||Image forming apparatus, a control method of image forming apparatus, a computer program and a computer readable storage medium|
|EP1654124A1 *||Aug 6, 2004||May 10, 2006||Canon Kabushiki Kaisha||Request method of service request apparatus|
|EP1654124A4 *||Aug 6, 2004||Apr 15, 2009||Canon Kk||Request method of service request apparatus|
|EP2393052A1 *||Jun 1, 2010||Dec 7, 2011||Promark Sp. z o.o.||System and method for preventive maintenance of marking devices|
|EP2393054A1||Jun 1, 2011||Dec 7, 2011||Promark Sp. z o.o.||System and method for preventive maintenance of marking devices|
|U.S. Classification||358/1.14, 358/1.15|
|International Classification||G06F3/12, G06K15/00, B41J29/38, B41J29/46|
|Cooperative Classification||G06F3/1235, G06F3/1288, G06F3/1204, G06F3/121, G06F3/1211|
|Sep 1, 1998||AS||Assignment|
Owner name: FUJI XEROX CO., LTD., JAPAN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FAN, SHENGKUO;NAKAJIMA, YASUO;FUNG, JOSEPH;AND OTHERS;REEL/FRAME:009435/0799;SIGNING DATES FROM 19980715 TO 19980723
Owner name: XEROX CORPORATION, CONNECTICUT
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FAN, SHENGKUO;NAKAJIMA, YASUO;FUNG, JOSEPH;AND OTHERS;REEL/FRAME:009435/0799;SIGNING DATES FROM 19980715 TO 19980723
|Jun 28, 2002||AS||Assignment|
Owner name: BANK ONE, NA, AS ADMINISTRATIVE AGENT, ILLINOIS
Free format text: SECURITY INTEREST;ASSIGNOR:XEROX CORPORATION;REEL/FRAME:013153/0001
Effective date: 20020621
|Jul 30, 2002||CC||Certificate of correction|
|Oct 31, 2003||AS||Assignment|
Owner name: JPMORGAN CHASE BANK, AS COLLATERAL AGENT, TEXAS
Free format text: SECURITY AGREEMENT;ASSIGNOR:XEROX CORPORATION;REEL/FRAME:015134/0476
Effective date: 20030625
Owner name: JPMORGAN CHASE BANK, AS COLLATERAL AGENT,TEXAS
Free format text: SECURITY AGREEMENT;ASSIGNOR:XEROX CORPORATION;REEL/FRAME:015134/0476
Effective date: 20030625
|Feb 15, 2005||FPAY||Fee payment|
Year of fee payment: 4
|Feb 10, 2009||FPAY||Fee payment|
Year of fee payment: 8
|Mar 8, 2013||FPAY||Fee payment|
Year of fee payment: 12