Embodiments of the present subject matter relate to a supply status indicator.
A peripheral device, such as a laser printer or an inkjet printer, often includes consumables, such as a toner cartridge or an inkjet cartridge, respectively. When the consumable has a certain status, such as being low on ink or toner, the peripheral device may indicate the status of the consumable. A client may prematurely replace the consumable in response to the status indication.
The following description includes terms, such as “up”, “down”, “upper”, “lower”, “first”, “second”, etc. that are used for descriptive purposes only and are not to be construed as limiting. The embodiments of a device or article of the present invention described herein can be manufactured, used, or shipped in a number of positions and orientations.
Embodiments of the present subject matter relate to a supply status indicator of a consumable device component of a managed peripheral device.
Within the exemplary system 100, the host computer 102 can be implemented as a variety of general purpose computing devices including, for example, a personal computer (PC), a server, a Web server, and other devices configured to communicate respectively with managed device 104. The host computer processes computer-executable instructions in the form of program modules that include routines, programs, objects, components, data structures and the like.
The host computer 102 provides a user with the ability to manipulate or otherwise prepare in electronic form, an image or document to be rendered as an image that is printed or otherwise formed onto a print medium by the managed device 104. The host computer 102 creates a print job containing a customized document and sends the print job to the managed device 104 for printing. The print job is configured in a page description language, such as printer control language (PCL®) of Hewlett Packard Company® or PostScript® of Adobe®, for example, depending on the managed device 104. The managed printing device 104 may receive the print job and may print the customized document.
When the host computer 102 is appropriately activated, a data transfer process is initiated between the managed device 104 and the host computer 102 over the communication link, such as the network 108. The process begins with a query from the host computer 102 to the managed device 104 requesting identification information. The query is made in a device management language, or management protocol application, such as PML (printer or peripheral management-information-base language) or XML (Extensible Markup Language). PML is a subset language of SNMP (simple network management protocol) that defines printer device objects with decimal-separated strings that are used in command queries, for example, to obtain object values. Further details with regard to XML may be found at http://www.w3.org/XML/.PML and XML are management protocol applications for monitoring and controlling printer devices and their functions. Upon receiving a PML or XML query for identification information, the managed device 104 responds by sending its model number or some other device identifier to the host computer 102. In an embodiment, the management protocol application is password protected.
Based on the identification information received from the managed device 104, the host computer 102 requests (e.g., through a PML or XML query) various information/data from the device 104 related to usage of the device 104. The usage information is typically cumulative data, but it may also be data gathered over a specified time period, such as the previous month. The usage information typically includes data detailing the number of pages that have been printed, the types of pages that have been printed and so on. For example, a particular type of managed device 104 may be able to print various-sized documents such as letter-sized, legal-sized and A4-sized documents. The managed device 104 responds to the request by transferring the usage information/data 318 over the communication interface 112 to the host computer 102.
The one or more host computers 102 include a first host computer 102A, or client host computer that provides a client or end-user with the ability to print an image from the managed device 104, and include a second host computer 102B, which may also be a managing host computer. The second host computer 102B provides an administrator with the ability to maintain, and monitor the maintenance of the coupled managed devices 104. The managed devices 104 illustrated represent a fleet of peripheral devices maintained by the administrator.
In an additional embodiment, the one or more host computers 102 may include a virtual computer where one or more computers, such as a central computer, virtually act as a real computer to different end-users and/or administrators. The administrator and user may use the same virtual computer through dumb terminals, or light terminals. The host computers 102A and 102B referred to herein include dumb terminals or light terminals, in an embodiment. Access to applications on the central computer depends upon who is accessing, as determined by security features.
The system 104B includes a control panel 140. The control panel 140 may have at least one audible indicator and/or at least one visual indicator, which are supply status indicators to inform the user of an error or a warning associated with printing. In an embodiment further illustrated in
In this embodiment, the host computers 102A, 102B each have a display 350. In an embodiment, the display 350 of the computer 102A includes a supply status indicator 385, and the display 350 of the computer 102B includes a supply status indicator 380, as described in more detail below.
The host computer 102A may also have a client software application 355 directed to an end-user of a device, in an embodiment. For example, the client software application is Toolbox. In an embodiment, the client software application 355 includes a supply status page 356.
The host computer 102B also has an administrative software application 360 including a supply status page 370. In an embodiment, the supply status page 370 of the administrative software application has more information and control with regard to the device 104, as compared with the supply status page 356 of the client software application 355. In an embodiment, the administrative software application 360 is an enterprise application such as HP Web Jetadmin, which provides a device maintainer with the ability to remotely install, configure, manage, and troubleshoot TCP/IP and IPX connected devices on an intranet.
In an embodiment, the supplies status page 370 provides information about the consumable device component, or consumable, allowing maintainers to view this information for maintenance purposes. In an embodiment, the supplies status page includes information regarding a consumable life expectancy and status of other consumables associated with one or more devices 140. The cartridge information is the main focus of the supplies status page 370, in an embodiment. The supplies status page provides the most detailed supplies status information available such as the remaining life of the cartridge, the estimated pages remaining, and the number of pages printed. In an embodiment, the supplies status page 370 allows a maintainer to hide or suppress the supply status indicator, such as hiding the status indicator 150 on the control panel 140, as described below.
In an embodiment, the managed device 104 includes an embedded web server (EWS) 390. The EWS 390 is firmware that resides in the device 104. After assigning an IP address to a printer, a user with security clearance connected to the network 108 can browse to the printer 104 and modify its configuration remotely. In an embodiment, access to the EWS is password protected.
Through the EWS, maintainers from a remote location can view (and print using the web browser facilities) substantially the same supplies status page 370 as one viewed (and printed) via the device control panel 140. The EWS is accessible from most browsers and administrator's computers.
When a user accesses the EWS, the device status page is opened in an embodiment. In an additional embodiment, users or administrators can open the supplies status page (356, 370) to access the detailed information from the EWS. In an embodiment, the supplies status page and the device status page are substantially exclusively accessible by the administrator.
In summary, in embodiments, the supply status information (e.g. supply status, authentication, supply status suppression) may be found on the supplies status page 356 and/or the supplies status page 370, which may be accessible from the embedded web server, the client software (e.g. Toolbox), and/or the enterprise administrative software (e.g. Web JetAdmin), in an embodiment. The supply status information may also be found on the control panel 140 of the device 104, through pop-up alerts, and email notifications.
As illustrated in embodiments of
The suppression option page 400 includes a supply status indicator switch 410, 420, 430 or 440 to switch between a suppressed state of the supply status indicator and an activated state of the first supply status indicator. The switch 410 of
In an embodiment, when the supply status indicator is suppressed, it is suppressed with respect to the end-user. For example, the supply status indicator 150 on the device control panel 140 is suppressed. Also, the supply status indicator 385 on the display 350 of the end-user host computer 102A is suppressed. As discussed in more detail below, in an additional embodiment, the supply status indicator 385 may be in the form of a pop up alert, or email notification of a supply status condition or event.
In an embodiment, even when the supply status indicator(s) is suppressed, the supply status indicator is not suppressed with respect to the administrator, or device maintainer. In this embodiment, the administrator may still receive email notifications of a supply status condition or event, and/or may receive pop up alerts, and/or may access status information with respect to the particular supply on the supply status page 370 accessible through the application 360, or the EWS 390, for example.
If box 520 is “Yes”, such that the supply status is displayed, then box 540 “Display Supply Status Indicator” is next in the process. The supply status is displayed, in at least one or more of the following embodiments, such as described in boxes 550, 560, 570, and/or 580.
In the embodiment of
In the embodiment of box 560, there is an electronic mail notification of the supply status, such as sending an email of the supply status to an email address. In an embodiment, the email notification is sent to one or more email addresses, such as to the administrator and/or to the user as designated in the suppression option web pages 400, for example. In an embodiment, e-mail alerts are sent to administrators who are responsible for a large number of devices connected to the network.
In the embodiment of box 570, there is a display of the supply status indicator 150 on the device control panel 140, as previously discussed and illustrated in
In the embodiment of box 580, there is a web site posting display of the supply status indicator. In an embodiment, the web site may have a list of maintained devices 104, and their respective associated status. In an additional embodiment, the web site may have a security feature, such as being password protected. In an additional embodiment, the web site is accessible through the supply status page 370, for example.
In an embodiment, the supply event is at least one event including when the consumable is invalid, from an unknown source, missing, low, empty, unreadable, unauthorized, installed, an incorrect consumable, not engaged properly, with a memory error, genuine, and authorized. The supply event may be an error message or a warning message. An error message is one which is displayed when the device is not in service. A warning message is displayed to alert the user to an impending condition, but which does not prevent immediate printing. When a warning message is displayed, the user may mistakenly believe that the supply is not in service, for example. In that case, the user may prematurely replace the supply, for example or prematurely request that the administrator replace the supply, for example. In order to utilize the supplies to their full capacity and effectiveness, the first supply status indicator is not accessible (or is suppressed) to the end-user. However, the second supply status indicator is to be received by the administrator in this embodiment.
At box 618, a supply event is identified, for example, by the device 104. At box 620, notification associated with the second supply status indicator is sent to the administrator. At box 622 is a query of whether the second supply status indicator was successfully sent to the administrator, such as via the pop up alert, or email notification. If the answer to the query is yes, then the process is concluded, or “done” at box 626. In an embodiment, the first supply status indicator remains suppressed when the second supply status indicator is successfully received by an administrator. If the answer to the query is no, then the process moves to restore or activate the first suppressed supply status indicator in an activated state, such as displaying the supply status indicator 150 at the device control panel 140, and/or sending a pop up alert to the end-user host computer 102A, and/or to any web page accessible by the end-user, in embodiments. The process then moves to box 630 and is done. In an embodiment, when the notification at box 620 is unsuccessful indicated at box 622, the first supply status indicator for the end-user is activated or restored, and the administrator may reset the suppression of the first supply status indicator accordingly.
The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. The accompanying drawings that form a part hereof show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced.
Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. The elements, materials, geometries, dimensions, and sequence of operations can all be varied to suit particular packaging requirements.
Embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
The Abstract is provided to comply with 37 C.F.R. §1.72(b) to allow the reader to quickly ascertain the nature and gist of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.
In the foregoing Detailed Description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments have more features than are expressly recited in each claim. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
It will be readily understood to those skilled in the art that various other changes in the details, material, and arrangements of the parts and method stages which have been described and illustrated in order to explain the nature of embodiments herein may be made without departing from the principles and scope of embodiments as expressed in the subjoined claims.
Number | Name | Date | Kind |
---|---|---|---|
5655174 | Hirst | Aug 1997 | A |
5727135 | Webb et al. | Mar 1998 | A |
5731824 | Kneezel et al. | Mar 1998 | A |
5997141 | Heacock | Dec 1999 | A |
6028674 | Tognazzini | Feb 2000 | A |
6234603 | Altfather et al. | May 2001 | B1 |
6310692 | Fan et al. | Oct 2001 | B1 |
6409302 | Altfather et al. | Jun 2002 | B2 |
6520612 | Merz et al. | Feb 2003 | B1 |
6622266 | Goddard et al. | Sep 2003 | B1 |
6641312 | Chang et al. | Nov 2003 | B1 |
20010034713 | Nakai et al. | Oct 2001 | A1 |
20020152430 | Akasaka et al. | Oct 2002 | A1 |
Number | Date | Country |
---|---|---|
779156 | Jun 1997 | EP |
WO-0231741 | Apr 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20060083521 A1 | Apr 2006 | US |