Cloud computing continues to evolve and develop. One of the activities that users of cloud computing may want to engage in is printing. However, there may be a reluctance to do so because of concerns over privacy, security, or otherwise losing sensitive data sent over the cloud for printing.
The following detailed description references the drawings, wherein:
Many consumers, businesses, and enterprises use or want to expand their use of cloud computing resources. One of these resources is cloud-based printing. There is a risk, however, of sending sensitive documents or other information over the cloud for printing, as they can be stored and/or misused. This reluctance to send personal, sensitive, and/or confidential data over the cloud, results in reduced usage of cloud-based printing.
Another difficulty associated with cloud-based printing is that some fonts or characters used in connection with a particular document or other information may not be rendered correctly or at all on a cloud-based printer. This can result in unacceptable printed output from a cloud-based printer, further reducing the usage of cloud-based printing.
An example of a system for secure printing 10 that is directed to addressing these challenges is illustrated in
As used herein, the term “non-volatile storage medium” is defined as including, but not necessarily limited to, any media that can contain, store, retain, or maintain programs, code, scripts, information, and/or data. A non-volatile storage medium may include any one of many physical media such as, for example, electronic, magnetic, optical, electromagnetic, or semiconductor media. More specific examples of suitable non-volatile storage media include, but are not limited to, a magnetic computer diskette such as floppy diskettes or hard drives, magnetic tape, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash drive, a compact disc (CD), a digital video disk (DVD), or a memristor.
As used herein, the term “processor” is defined as including, but not necessarily limited to, an instruction execution system such as a computer/processor based system, an Application Specific Integrated Circuit (ASIC), a computing device, or a hardware and/or software system that can fetch or obtain the logic from a non-volatile storage medium and execute the instructions contained therein. “Processor” can also include any controller, state-machine, microprocessor, cloud-based utility, service or feature, or any other analogue, digital and/or mechanical implementation thereof.
As used herein, the term “server” is defined as including, but not necessarily limited to, a computing device, program, or combination thereof that processes requests, delivers data or other information, or provides one or more services over the cloud and/or a local network. As used herein, the term “client” is defined as including, but not necessarily limited to, hardware, software, or a combination thereof that access a server. Examples include, but are not limited to, a computing device, phone, tablet, personal digital assistant, or server.
As used herein, the term “printer” is defined as including, but not necessarily limited to, a peripheral that produces a representation of a document on one or both sides of media such as paper, transparency, fabric, etc. A printer can be single function or multi-function (e.g., including scanning, faxing, or other functionality). A printer can use any of a variety of different types of marking technologies such as laser, inkjet, dye-sublimation, off-set printing, thermal printing, impact, etc. As used herein, the terms “render” and “rendering” are defined as including, but not necessarily limited to, taking print data such as text, images, graphics, etc. and converting them into a format that is compatible with a destination printer.
Referring again to
In this example of system 10, if available, cloud-connected primer 14 transmits the identifier to client 12 via the secure connection established by server 16. Client 12 confirms that the identifier received from available cloud-connected printer 14 via the secure connection established by server 16 is the same as the identifier transmitted by client 12. Upon verification of the identifier, client 12 transmits the rendered print data to available cloud-connected printer 14 via the secure connection established by server 16.
An example of a flow diagram 20 for system 10 is shown in
If cloud-connected printer 14 is off-online or unavailable, as generally indicated by reference numeral 30, then XMPP server 26 relays this information to signaling server 22, as indicated by arrow 32. Signaling server 22 in turn conveys this information to client 12, as indicated by arrow 34, and the secure print request is terminated.
If cloud-connected printer 14 is online and available, then signaling server 22 sends the secure print request to XMPP server 26, as indicated by arrow 36. XMPP server 26 in turn relays the secure print request to cloud-connected printer 14, as indicated by arrow 38. Cloud connected printer 14 in turn establishes a secure extensible messaging and presence protocol (XMPP) connection with client 12, as indicated by arrow 40, and provides the identifier back to client 12. Client 12 confirms or verifies that the identifier received from cloud-connected printer 14 is the same as the one originally sent to signaling server 22. Client 12 then sends or transfers rendered print data for the print request to cloud-connected printer 14 via the secure connection, as indicated by arrow 42, if the identifier from cloud-connected printer 14 is verified or confirmed. If the identifier received from cloud-connected printer 14 is not confirmed or verified by client 12, then no rendered print data is transferred. Upon completion of the print job (i.e., printing of the print data by cloud-connected printer 14), the XMPP connection between client 12 and cloud-connected printer 14 is terminated, as indicated by reference numeral 44.
Client 12 does not send or transmit print data over cloud 18. Rather, rendered print data is sent or transmitted by client 12 directly to printer via a separately established secure connection. This helps to address the above-described concerns associated with sending sensitive documents or other information over the cloud for printing. An additional advantage is that fonts and characters used in connection with a particular document or other information are generally rendered properly so that the output of printer 14 matches the content viewed on client 12.
An example of a method of secure printing 46 is shown in
The secure connection established between the client and the cloud-connected printer may include a peer-to-peer network. The print request initiated from the client to the cloud-connected printer and/or the verification of the availability of the cloud-connected printer in response to the initiated print request may be conducted oven an unsecure network via the cloud. The secure connection established between the client and the cloud-connected printer may be terminated upon completion of printing of the print data by the cloud-connected printer.
An example of additional possible elements of the method of secure printing 46 is shown in
An example of a non-volatile storage medium 72 including instructions executable by a processor 73 coupled to non-volatile storage medium 72, as generally indicated by double-headed arrow 75, is shown in
The secure connection established between the client and the cloud-connected printer may include a peer-to-peer network. The print request initiated from the client to the cloud-connected printer and/or the verification of the availability of the cloud-connected printer in response to the initiated print request may be conducted oven an unsecure network via the cloud. The secure connection established between the client and the cloud-connected printer may be terminated upon completion of printing of the print data by the cloud-connected printer. Processor 73 may reside in the client and at least one internet-based server (e.g., XMPP server 26) to which the cloud-connected printer is coupled.
An example of additional possible instructions on non-volatile storage medium 72 is shown in
Although several examples have been described and illustrated in detail, it is to be clearly understood that the same are intended by way of illustration and example only. These examples are not intended to be exhaustive or to limit the invention to the precise form or to the exemplary embodiments disclosed. Modifications and variations may well be apparent to those of ordinary skill in the art.
Additionally, reference to an element in the singular is not intended to mean one and only one, unless explicitly so stated, but rather means one or more. Moreover, no element or component is intended to be dedicated to the public regardless whether the element or component is explicitly recited in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
6721286 | Williams et al. | Apr 2004 | B1 |
7254400 | Sakakura | Aug 2007 | B1 |
7352485 | Kinoshita | Apr 2008 | B2 |
7573904 | Pichna et al. | Aug 2009 | B2 |
8027049 | Kinoshita et al. | Sep 2011 | B2 |
8060018 | Davis et al. | Nov 2011 | B2 |
8346903 | Shepherd | Jan 2013 | B2 |
20020051178 | Nakayasu et al. | May 2002 | A1 |
20030011810 | Strobel et al. | Jan 2003 | A1 |
20030210420 | Yamauchi | Nov 2003 | A1 |
20030235174 | Pichna et al. | Dec 2003 | A1 |
20040137855 | Wiley et al. | Jul 2004 | A1 |
20050149755 | Shima et al. | Jul 2005 | A1 |
20050170845 | Moran | Aug 2005 | A1 |
20060039349 | Samuel et al. | Feb 2006 | A1 |
20060087682 | Lee | Apr 2006 | A1 |
20070124436 | Shepherd | May 2007 | A1 |
20070217382 | Minamizawa | Sep 2007 | A1 |
20070265003 | Kezys et al. | Nov 2007 | A1 |
20080004075 | Horton | Jan 2008 | A1 |
20080096486 | Whitten | Apr 2008 | A1 |
20090287806 | Hamilton et al. | Nov 2009 | A1 |
20090310570 | Smith | Dec 2009 | A1 |
20090323659 | Zhang | Dec 2009 | A1 |
20100185858 | Nishimi et al. | Jul 2010 | A1 |
20100309510 | Hansen | Dec 2010 | A1 |
20110099264 | Chapin et al. | Apr 2011 | A1 |
20110242576 | Allen et al. | Oct 2011 | A1 |
20120057193 | Jazayeri et al. | Mar 2012 | A1 |
20120084364 | Sivavakeesar | Apr 2012 | A1 |
20120084771 | Hashimoto et al. | Apr 2012 | A1 |
20120218589 | Watanabe et al. | Aug 2012 | A1 |
20120229844 | Yada et al. | Sep 2012 | A1 |
20120268777 | Fry | Oct 2012 | A1 |
20120307298 | Ishige et al. | Dec 2012 | A1 |
20120324076 | Zerr et al. | Dec 2012 | A1 |
20130016392 | Lee | Jan 2013 | A1 |
20130128306 | Takahashi | May 2013 | A1 |
20130163580 | Vass | Jun 2013 | A1 |
20130194623 | Tecu et al. | Aug 2013 | A1 |
20130250330 | Chigusa | Sep 2013 | A1 |
20130250358 | Suzuki | Sep 2013 | A1 |
20130286425 | Nakamura et al. | Oct 2013 | A1 |
20140134999 | Scheessele et al. | May 2014 | A1 |
Number | Date | Country |
---|---|---|
2002026895 | Jan 2002 | JP |
WO-2007082244 | Jul 2007 | WO |
Entry |
---|
Fernandes, et al. The Mobile Printer Enterprise. Feb. 2012. Quocirca Ltd. |
Apple Inc., “Messages,” iOS, (web page), Oct. 29, 2012, <http://web.archive.org/web/20121029212402/http://www.apple.com/ios/messages/>. |
Apple, “Features that go further,” iOS 5, Sep. 10, 2012, <http://web.archive.org/web/20120910202047/http://www.apple.com/ios/features.html>. |
I. Gruber, et al, “Ad Hoc Routing for Cellular Coverage Extension”, Apr. 22-25, 2003, http://ieeexplore.ieee.org/xpls/abs—all.jsp?arnumber=1207137 > on pp. 1816-1820; vol. 3. |
TechTarget, “out-of-band signaling,” SearchNetworking, Jan. 20, 2012, <http://web.archive.org/web/20120120154228/http://searchnetworking.techtarget.com/definition/out-of-band-signaling>. |
Wikipedia, “Out-of-band management,” Oct. 24, 2012, <http://en.wikipedia.org/w/index.php?title=Out-of-band—management&oldid=519500148>. |
Wikipedia, “Wi-Fi Direct,” Oct. 16, 2012, <http://en.wikipedia.org/w/index.php?title=Wi-Fi—Direct&oldid=518220509>. |
Wikipedia, “Wi-Fi,” Oct. 31, 2012, <http://en.wikipedia.org/w/index.php?title=Wi-Fi&oldid=520677838>. |
Hewlett-Packard Development Company, L.P., “Cloud printing in the enterprise: Liberating the mobile print experience from cables, operating systems and physical boundaries,” Mar. 2010, <http://www.hubtechnical.com/Collateral/Documents/English-US/HP/11-CloudPrintingintheEnterprise.pdf>. |
Hewlett-Packard Development Company, L.P., “HP Access Control Secure Pull Printing,” Nov. 2008, <http://h71028.www7.hp.com/enterprise/downloads/HP-Access-Control-Secure-Pull-Printing.pdf>. |
Grayson, Wayne; “Google Announces Web App for Printing from Mobile Device”, <http://grayson.blogs.tuscaloosanews.com/11308/google-announces-web-app-for-printing-from-mobile-device/> ; Apr. 16, 2010. |
Hewlett-Packard Development Company, L.P., “HP ePrint Enterprise mobile printing solution,” Mar. 2010, <http://www.hp.com/hpinfo/newsroom/press—kits/2010/MPSSpring2010/pdf/HP—ePrint.pdf>. |
Hewlett-Packard Development Company, L.P., “HP ePrint Enterprise mobile printing solution,” Sep. 2010, <http://www.hp.com/hpinfo/newsroom/press—kits/2010/InnovationSummit/HP—ePrint—Enterprise—Solution.pdf>. |
Number | Date | Country | |
---|---|---|---|
20140293324 A1 | Oct 2014 | US |