Network printers heretofore may be associated with an identifier, such as a unique email address, that may act as a recipient for print content. This print content may then be routed to the printer. Access to printing via the identifier may be restricted using a white listing approach. In this instance, only certain pre-approved users can print via the identifier.
As noted above, a network printing device may be associated with an identifier that allows trustworthy sources to transmit print requests thereto. Web enabled network printers have increased the demand for mechanisms that restrict access to such printers. However, users may still be interested in printing content contained in sources considered to be untrustworthy. For example, some public content generated from RSS/ATOM feeds, social networking groups, or forums may be of interest. Nevertheless, a subscriber may be weary of providing these public sources unfettered access to their printing device. If left unchecked, there may be instances of misuse or exploitation. For example, an unscrupulous member of these public sources may send a high volume of content to overload the printing device. Moreover, countless online marketers may send advertisements to the printer as part of their marketing strategy.
A method is disclosed comprising associating, using at least one processor, an identifier with a printing device; associating, using the at least one processor, the identifier with a configuration comprising instructions for the printing device when handling a print request associated with the configuration; determining, using the at least one processor, whether a received print request originates from a trustworthy source; and if the print request originates from an untrustworthy source, associating, using the at least one processor, the received print request with the configuration such that the printing device handles the received print request in accordance with the configuration.
In view of the foregoing, disclosed herein are a system, non-transitory computer readable medium, and method to manage printing requests from untrustworthy sources. In one example, a configuration may be associated with a printing device. In another example, if a print request is received from an untrustworthy source, the print request may also be associated with the configuration such that the request is handled in accordance therewith. Thus, the owner of a printing device may use the configuration to limit access to a printing device. This allows a user to print content from untrustworthy sources that may be of interest without worrying about the potential for misuse or exploitation. The aspects, features and advantages of the present disclosure will be appreciated when considered with reference to the following description of examples and accompanying figures. The following description does not limit the application; rather, the scope of the disclosure is defined by the appended claims and equivalents.
The computer apparatus 100 may also contain a processor 110, which may be any number of well known processors, such as processors from Intel® Corporation. In another example, processor 110 may be an application specific integrated circuit (“ASIC”). Non-transitory computer readable medium (“CRM”) 112 may store instructions that may be retrieved and executed by processor 110. As will be discussed in more detail below, the instructions may include a generator 114, a settings module 116, and a job coordinator 118. In one example, non-transitory CRM 112 may be used by or in connection with any instruction execution system that can fetch or obtain the logic from non-transitory CRM 112 and execute the instructions contained therein.
Non-transitory computer readable media may comprise any one of many physical media such as, for example, electronic, magnetic, optical, electromagnetic, or semiconductor media. More specific examples of suitable non-transitory computer-readable media include, but are not limited to, a portable magnetic computer diskette such as floppy diskettes or hard drives, a read-only memory (“ROM”), an erasable programmable read-only memory, a portable compact disc or other storage devices that may be coupled to computer apparatus 100 directly or indirectly. Alternatively, non-transitory CRM 112 may be a random access memory (“RAM”) device or may be divided into multiple memory segments organized as dual in-line memory modules (“DIMMs”). The non-transitory CRM 112 may also include any combination of one or more of the foregoing and/or other devices as well. While only one processor and one non-transitory CRM are shown in
The instructions residing in non-transitory CRM 112 may comprise any set of instructions to be executed directly (such as machine code) or indirectly (such as scripts) by processor 110. In this regard, the terms “instructions,” “scripts,” and “applications” may be used interchangeably herein. The computer executable instructions may be stored in any computer language or format, such as in object code or modules of source code. Furthermore, it is understood that the instructions may be implemented in the form of hardware, software, or a combination of hardware and software and that the examples herein are merely illustrative.
The instructions of the generator 114 may instruct processor 110 to generate an identifier and to associate the identifier with the printing device. In one example, the identifier may be an e-mail address. In another example, a plurality of identifiers may be generated and associated with the same printing device such that each identifier has its own unique configuration. These identifiers may act as aliases for the printing device.
Settings module 116 may instruct processor 110 to further associate the identifier with a printing configuration that specifies how the printing device handles a print request. As noted above, multiple identifiers may be generated by generator 114 such that each identifier may be associated with its own configuration. A configuration may limit the number of pages being printed, the amount of ink to utilize per print request, or may specify a time window during which a print request may be received. Thus, the configuration may allow a user to control what, when, and how content is printed.
Job coordinator 118 may instruct processor 110 to determine whether a received print request originates from a trustworthy source; if it is determined that the source is not trustworthy, job coordinator 118 may instruct processor 110 to associate the received print request with the identifier. Job coordinator 118 may further instruct processor 110 to determine whether the received print request satisfies a condition indicated in the configuration and to print the content contained therein, if it is determined that the received print request satisfies the condition.
Working examples of the system, method, and non-transitory computer-readable medium are shown in
As shown in block 202 of
Referring now to
Referring back to
Referring back to
Advantageously, the foregoing system, method, and non-transitory computer readable medium provide users of network or web enabled printers to control what, when, and how content is printed. Furthermore, the techniques disclosed herein allow users to customize configurations for each source deemed untrustworthy. In this regard, rather than banning all content from certain sources, users may print content from sources they may find interesting while protecting the printer from misuse or exploitation.
Although the disclosure herein has been described with reference to particular examples, it is to be understood that these examples are merely illustrative of the principles of the disclosure. It is therefore to be understood that numerous modifications may be made to the examples and that other arrangements may be devised without departing from the spirit and scope of the disclosure as defined by the appended claims. Furthermore, while particular processes are shown in a specific order in the appended drawings, such processes are not limited to any particular order unless such order is expressly set forth herein; rather, processes may be performed in a different order or concurrently and steps may be added or omitted.
This application is a Continuation of U.S. patent application Ser. No. 13/754,945, filed Jan. 31, 2013, entitled “PRINTING FROM UNTRUSTWORTHY SOURCE”—hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5611050 | Theimer et al. | Mar 1997 | A |
6958824 | Whitmarsh | Oct 2005 | B2 |
6975419 | Staas et al. | Dec 2005 | B2 |
7075409 | Guba | Jul 2006 | B2 |
7298511 | Lay et al. | Nov 2007 | B2 |
7321437 | Parry | Jan 2008 | B2 |
7375838 | Moneypenny et al. | May 2008 | B2 |
7474423 | Garcia et al. | Jan 2009 | B2 |
7729001 | Perronnin | Jun 2010 | B2 |
7814116 | Hauser | Oct 2010 | B2 |
9146953 | Hernacki | Sep 2015 | B1 |
20030067625 | Kim | Apr 2003 | A1 |
20040167974 | Bunn et al. | Aug 2004 | A1 |
20050198572 | Quiller et al. | Sep 2005 | A1 |
20070229886 | Sakurai | Oct 2007 | A1 |
20070271347 | Logue et al. | Nov 2007 | A1 |
20080007759 | Furuyama et al. | Jan 2008 | A1 |
20080307059 | Ono | Dec 2008 | A1 |
20090327502 | Brewer et al. | Dec 2009 | A1 |
20100014110 | Munetomo | Jan 2010 | A1 |
20100141993 | Dowling | Jun 2010 | A1 |
20110085196 | Liu et al. | Apr 2011 | A1 |
20110090529 | Hertling | Apr 2011 | A1 |
20110157630 | Otaka | Jun 2011 | A1 |
20110292439 | Nagata et al. | Dec 2011 | A1 |
20120084365 | McCann, Jr. | Apr 2012 | A1 |
20120147199 | Lorsch | Jun 2012 | A1 |
20120194850 | K. | Aug 2012 | A1 |
20120250076 | Kumar et al. | Oct 2012 | A1 |
20120297026 | Polis et al. | Nov 2012 | A1 |
20120300251 | St. Laurent | Nov 2012 | A1 |
20120307268 | Miller et al. | Dec 2012 | A1 |
20130021643 | Nuggehalli | Jan 2013 | A1 |
20130063774 | Nuggehalli et al. | Mar 2013 | A1 |
20130185364 | Bhatia | Jul 2013 | A1 |
20130308165 | Venkatesh et al. | Nov 2013 | A1 |
20140022585 | Cogan | Jan 2014 | A1 |
Number | Date | Country |
---|---|---|
1020050063208 | Jun 2005 | KR |
WO-20000076204 | Dec 2000 | WO |
Entry |
---|
Accunet, Inc., “Alias Account Information,” SiteBuilder User's Guide, (Web Page), available Dec. 20, 2010, <http://www.sbusers.com/1/sbusers/using_aliases.asp>. |
Accunet, Inc., “Alias Account Information,” SiteBuilder User's Guide, (Web Page), available Feb 8, 2013, <http://web.archive.org/web/20130208122841/http://www.sbusers.com/1/sbusers/using_aliases.asp>. |
Citrix, “Controlling Printing Settings and User Preferences,” XenApp Product Documentation, available as of Jan. 6, 2014, <http://citrix.edocspdf.com/media/output/en.xenapp6-w2k8-admin.ps-controlling-print-settings-v2.pdf>. |
E. Gardner, New Business Models, Interview 2.0, “Peecho uses the cloud to turn your digital publication into print,” Lean Back 2.0, May 17, 2012, pp. 1-5, The Economist Newspaper Limited 2013, Available at: <economistgroup.com/leanback/new-business-models/peecho-uses-the-cloud-to-turn-your-digital-pub. |
Everyoneprint, “Installation and Configuration Guide,” (Research Paper), Feb. 24, 2014, 140 pages, available at http://www.everyoneprint.com/files/EveryonePrintInstallGuide-EN.pdf. |
Google Cloud Print, 2013, pp. 1-10, Available at: <support.google.com/cloudprint/?hl=en>. |
Improbulus, “How to use Gmail aliases to organise emails and handle spam,” Apr. 6, 2005, A Consuming Experience, (Web Page), <http://www.consumingexperience.com/2005/04/how-to-use-gmail-aliases-to-organise.html>. |
Microsoft, “Filtering mails to email aliases with inbox rules?” (Web Page), Microsoft Office 365 Community, posts dated Dec. 9, 2011-Jun. 20, 2013, 5 pages, available at http://community.office365.com/en-us/forums/158/t/11534.aspx. |
Mozilla Foundation, “Configuring Email Aliases,” Mozilla Support, Thunderbird, (Web Page), available Jun. 21, 2012, <https://support.mozilla.org/en-US/kb/configuring-email-aliases>. |
Mozilla Thunderbird, “Configuring Email Aliases,” (Web Page), Jan. 31, 2013, 1 page, available at http://web.archive.org/web/20130131063620/https://support.mozillamessaging.com/en-US/kb/configuring-email-aliases. |
openuse.org, “SDB:Using Your Own Filters to Print with CUPS,” accessible online Nov. 2, 2013, <http://en.opensuse.org/SDB:Using_Your_Own_Filters_to_Print_with_CUPS>. |
Patterson, P., “Digging Deeper into OAuth 2.0 on Force.com,” developerforce, 2012, pp. 1-20, Salesforce.com, available at: http://wiki.developerforce.com/page/Digging_Deeper_into_OAuth_2.0_on_Force.com. |
Printeron, “PrinterOn Mobile Printing for Airports,” 2012, pp. 1-4, available at: http://printeron.com/industry/airports.html. |
Printeron, “Downloads, PDS—Print Delivery Station,” Oct. 21, 2012, 2 pages, available at http://web.archive.org/web/20121021095721/http://www.printeron.com/support/downloads.html. |
Spiceworks, “Exchange rule to filter emails sent to specific alias,” (Web Page), posts dated Jun. 3, 2010-Jun. 28, 2010, 3 pages, available at http://community.spiceworks.com/topic/100741-exchange-rule-to-filter-emails-sent-to-specific-alias. |
Wikipedia, “Controlled payment number,” Aug. 29, 2012, <http://web.archive.org/web/20120829155930/http://en.wikipedia.org/wiki/Controlled_payment_number>. |
Number | Date | Country | |
---|---|---|---|
20150254033 A1 | Sep 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13754945 | Jan 2013 | US |
Child | 14718602 | US |