Patent Application
20050094193
1. Field of the Invention
This invention generally relates to digital document processing and, more particularly, to a system and method for providing print job notification, using a print driver.
2. Description of the Related Art
In a large organization, a printing task may be distributed between multiple parties. For example, a first person may send a document to a printer for printing, but it may be the responsibility of a different person to deliver the printed documents. As another example, the first person may send a print job to a printer in a remote location, and rely upon another party to collect the documents from the printer. Internet printing protocol (IPP) presently addresses this issue with the use of a subscription object. A subscription object can be attached to a job object, to deliver notification upon job completion, or errors to an IPP client running on a host. The notification may also include additional text with instructions. IPP has the following problems:
1. An IPP printer object needs to be implemented in the product, and an IPP client needs to be installed on a host that is to receive the notifications. Developing an IPP printer object for a multifunctional peripheral (MFP) is not a small task. It cannot be done quickly, often times not within the time limits of a product's development cycle. IPP requires an asserted effort that is costly in man-hours, with further time spent in integration.
2. IPP requires a HTTP 1.1 compliant transport that can listen to port 631 on the MFP and the client host computer. In other words, another protocol needs to be implemented, which in turn, implements the IPP.
3. Further, the recipient of the notification must be running an IPP client to receive the notification. It is not sent via email.
It would be advantageous if there were a simple process to send print job notifications that avoided the above-mentioned problems associated with IPP.
The present invention solves the print job notification problem on a per job basis. Notification of errors and job completion are sent via email to an individual, instructing the individual in what is needed to complete any auxiliary tasks associated with a print job. The invention permits an email to be used to communicate any message pertinent to the completion of the print job.
Accordingly, a print driver method is provided for print job notification. The method comprises: accepting a document at a print driver; presenting a user interface (UI) for accepting print job commands, such as the selection of a printer; presenting a UI for receiving notification commands, such as a text message of email address; sending the document for printing in response to the print job commands; and, sending a print job notification to an email address, in response to sending the document for printing. The print job notification can be for the purpose of reporting errors, a completed print job, the identity of the selected printer, or instructions to be carried out regarding the completed print job.
Presenting a UI for receiving notification commands may include presenting: a graphical UI (GUI) tab to enable the notification feature; an address box for entry of an email address; and/or, a text box for entry of a text message. Further, the UI may present selection tabs for features such as staple, hole punch, document delivery time, and document delivery location.
In some aspects, the email notification may be relayed through the printer performing the print job, with the substeps of: sending the notification to a printer, bundled with the document to be printed; and, sending the notification as an email from the printer, to a destination. In this aspect, the notification may be bundled with the document and selected job attributes and sent a print subsystem associated with a print driver.
Additional details of the above-described method, and a print driver system for print job notification are provided below.
The print subsystem 106 has an interface on line 110 to accept a document (electronically formatted) and an interface on line 108 to accept the notification-enabled print driver commands. The print subsystem 106 has an interface on line 112 to supply the document for printing, bundled with a print job email notification. In one example, the print subsystem 106 supplies the email notification embedded in printer job language (PJL) statements. However, the invention is not limited to any particular print language or format.
A printer 114 includes a print controller 116 having an interface on line 112 to accept the bundled document for printing from the client print subsystem 106. The print controller 116 has an interface on line 118 to supply the document printed on a paper media, and an interface on line 120 to supply the print job email notification. The printer 114 also includes a browser 122 having an interface on line 120 to accept the print job email notification and a network-connected interface on line 124 to supply the print job notification to a specified email address. Note, the figure implies that the printer 114 is locally connected to the client 102. However, the client 102 and printer 114 may also be network connected, through an intervening server (not shown) for example. In one aspect, line 112 is a local area network (LAN). In another aspect, lines 112 and 124 represent a common (the same) network.
In another aspect (not shown), the print driver UI presents a menu for the selection of a printer and supplies the selected printer identity with the print job notification in the notification-enabled print driver commands. One example of such an interface would be the print submenu, that is accessible using the “File” tab of a Microsoft Word document processing application.
Returning to
The present invention provides a more convenient and time-efficient method of conferring with other individuals, and permits print job tasks to be managed on a per job basis. This invention is novel in that it uses the print driver, instead of a protocol (such as IPP) to solve the problem. The invention has the following advantages:
1. Print drivers are proprietary, and the notification feature can be leveraged as an advantage over a competitor's product.
2. It does not require the implementation and long development cycle of a complicated protocol like IPP. Rather, it can be implemented in the development cycle of a single product.
3. It sends notifications via email, so the recipient's host computer does not need to run an IPP client.
4. Conventionally, notification must be attached to an existing IPP print job. The invention has the notification accompany the print job. That is, the notification is part of the job submission.
The print driver presents the required notification information to the printer, in response to receiving the information from the user. The print driver may provide a tab (see
1. An enable box may be checked to enable the notification feature for the current print job.
2. A line is presented for entry of an email address.
3. A text box is presented for the entry of message/instructions pertinent to the print job.
The driver may employ any number of additional features. As an example, the print driver can add a PJL directive that enables the notification feature for the job, and provides the email address and text. In this example, the PJL would cause a routine to be called within the MFP to execute the feature upon error and/or job completion. Note, in some aspects of the invention, an email client must be resident in the MFP or printer.
The driver might supply the following PJL command:
The Notification information is stored with the other job attributes and is passed through the printer.
Step 502 accepts a document at a print driver. Step 504 presents a user interface (UI) for accepting print job commands. Step 506 presents a UI for receiving notification commands. Step 508 sends the document for printing in response to the print job commands. Step 510 sends a print job notification to an email address, in response to sending the document for printing.
In some aspects, sending a print job notification to an email address in Step 510 includes sending a notification for the purpose of reporting errors and/or completed print jobs. In other aspects, Step 510 sends instructions to be carried out regarding the completed print job. In another aspect, Step 510 sends an error message in the event of a printing error.
In one aspect, presenting a UI for receiving notification commands in Step 506 includes substeps. Step 506b receives a text message. Step 506c receives the email address to which the text message is to be sent. More specifically, Step 506a may present a GUI tab to enable the notification feature. Then, Step 506b may present a text box for entry of a text message and 506c may present an address box for entry of an email address.
In other aspects, Step 506 receives instructions for the disposition of the printed documents, and sending a print job notification to an email address (Step 510) includes sending the printed document disposition instructions. In another aspect, Step 506 receives the email address to which to the notification is to be sent, and Step 510 sends the notification to the email address specified in the notification commands.
In one aspect, presenting a UI for receiving notification commands (Step 506) includes presenting selection tabs for job attributes such as stapling, hole punching, document delivery time, and document delivery location.
In one aspect, presenting a UI for receiving print job commands in Step 504 includes presenting a menu for the selection of a printer. Then, sending a notification to an email address (Step 510) may include sending the identity of the selected printer.
In one aspect, sending a print job notification to an email address in Step 510 includes relaying the notification through the printer performing the print job. In this aspect, Steps 508 and 510 overlap. Then, Step 510 may include substeps. Step 510a sends the notification to a printer, bundled with the document to be printed. Step 510b sends the notification as an email from the printer, to a destination. In some aspects, presenting a UI for accepting print job commands in Step 504 includes presenting a menu for selecting a printer, job attributes, and an email address. Then, Step 510a sends the notification bundled with the document and selected job attributes, to the specified printer. Step 510b sends the notification from the specified printer to the destination with the specified email address.
In other aspects, sending the notification bundled with the document and selected job attributes in Step 510a includes sending the notification through a print subsystem associated with the print driver. For example, the notification can be sent through the print subsystem embedded in printer job language (PJL) statements.
A system and method have been provided for print driver print job notification. Examples have been given of notification messages and menu formats, but the invention is not limited to these examples. Although the invention has generally been explained in the context of a Microsoft Windows operating system, the invention can also be practiced with an Apple MacIntosh Operating System, Linux Operating System, System V Unix Operating Systems, BSD Unix Operating Systems, OSF Unix Operating Systems, Sun Solaris Operating Systems, HP/UX Operating Systems, or IBM Mainframe MVS and AS/400 Operating System, to name a limited list of other possibilities. Other variations and embodiments of the invention will occur to those skilled in the art.
