The present application is a national stage filing under 35 U.S.C 371 of PCT application number PCT/IN2011/000423, having an international filing date of Jun. 23, 2011, which claims priority to Indian patent application 1490/CHE/2011, filed on Apr. 29, 2011, the disclosures of which are hereby incorporated by reference in its entirety.
In an office, a user typically sends a print job directly to a printer connected to his computer or to a networked printer over the office LAN. A recent development is the introduction of ‘e-print enabled’ printers which have an email address and which can receive and process a print job sent to their email address.
Some examples are described below with reference to the following figures in which:
In the context of this specification, a “print job” is an instruction to print text and/or an image. It applies to any text or images which can be printed, including but not limited to word processed documents, pdf files, graphics, photographs, spreadsheets, text documents, presentations, payslips, faxes etc. A “printer” is an electronic device that performs printing and/or copying functions. It includes devices which are dedicated to printing, but also includes devices, such as scanners, copiers, machines with facsimile operations, and/or multi-functional devices that perform several functions such as printing, scanning, copying, and faxing.
In a typical office a user selects a specific printer to which a print job is to be sent using an application or operating system on his computer. The print job is then addressed to that specific printer and sent over the LAN either directly to the printer or to a print server which then directs the print job to the specific printer identified by the user in the print instruction. In e-print systems a user can send a print job to a specific ‘e-print enabled’ printer by emailing the print job to an email address of that specific printer. The email is typically received by an email server and then downloaded from the server by the printer having that email address.
However, as workers become increasing mobile they may no longer work from only a single office and may travel to different locations. Further, long work hours and ‘flexible’ working arrangements mean that some employees will work from both the office and their home.
The server 10 is able to communicate with several printers including a home printer 30 at the user's home, a black and white office printer 40 at the user's main office, a hotel printer 50 and a graphics printer 60 at the user's main office. Each printer has its own address. In this example each printer is an e-print enabled printer having its own email address, but in other examples some or all of the printers may not be email enabled printers, but rather conventional printers with a network address accessible via a LAN.
The server 10 has a memory 14 containing machine readable instructions 15 and a processor 12 for executing said instructions. The instructions act as a virtual print identity manager. By executing the machine readable instructions, the server is capable of selecting which printer to print the print job on based on one or more parameters of the virtual print identity (VPI). The one or more parameters may be stored on the memory 14 of the server, or in an external memory accessible by the server. In the example of
The one or more parameters may comprise user location and/or one or more rules or user preferences for determining where the print job is printed. In one example, the virtual print identity indicates the location of the user and this user location information can be thought of as a ‘parameter’ relating to where the print job should be printed. If the user is travelling and the virtual print identity indicates that the user is currently staying at a hotel, then the print job may be sent to the hotel printer 50 for instance. Other parameters relating to where the print job should be printed may comprise print job type or time based rules. For example, if the print job contains graphics, it is sent to the graphics printer 60, or if the print job does not contain graphics it is sent to the office printer from 8 am to 6 pm and the home printer from 6.01 pm until 7.59 am.
As the virtual print identity is not tied to any specific user device or any specific physical printer, it is very simple to send a print job to a printer preferred by the user. The print job can simply be addressed to the virtual print identity associated with the user and the server will select the appropriate printer. In this way the selected printer is independent of the actual device which sent the print job and determined instead by one or more parameters of the virtual print identity to which the print job was addressed.
While in the above example the print job was sent by the first user, in other examples the print job could be sent by a third party (e.g. a second user such as a secretary). So, for example, a second user working in Bangalore, could send a print job to a virtual print identity associated with a first user who is currently located in Hong Kong. The server then selects a printer close to the first user in Hong Kong. In another example, the third party could be a subscription service, e.g. a service for regularly sending a newspaper, or other periodical, as a print job to the first user. The third party may send the print job by email or by another network protocol, e.g. by a print application on a user device of a second user or an application belonging to the subscription service provider.
The server 10 has a processor 12 and a memory 14. The memory 14 stores a list 220 of virtual print identities managed by the server and a virtual print identity manager 230. The virtual print identity manager 230 may be implemented by a set of machine readable instructions which are executable by the processor. Upon receiving a print job addressed to a virtual print identity handled by the server, the virtual print identity manager 230 selects a printer, based on one or more parameters of the virtual print identity, and makes the print job available to that printer as described above in
In the example shown in
The print permissions database 700 comprises a list of virtual print identities and print permissions associated with the virtual print identities. When the server receives a print job of a type which is restricted (e.g. only available to certain people or paying subscribers), the VPI manager 230 consults the print permissions database 700 to check that the virtual print identity has permission to print the print job. If the virtual print identity has permission then the VPI manager proceeds to select an appropriate printer as described in
The print metering database 800 comprises usage data for a plurality of virtual print identities. It communicates with the VPI manager and meters the print usage of each virtual print identity. This information may be used for billing purposes or to impose print quotas for example.
The print identity management portal 500 and printer database 600 will be described later, but first the virtual print identity database 300 will be described in more detail.
There are various ways of organizing information into a record in the virtual print identity database and various types of data may be included.
The record 400 may further comprise an entry for each printer associated with the virtual print identity (in the illustrated example entries 465, 470 and 475 each relate to a respective printer). Each such printer entry comprises information relating to the printer, for instance the printer address (which in this example is an email address, but may alternatively be a network address, IP address or other information enabling communication with the printer), the printer's location, the type of printer etc. By inspecting the printer location information and comparing to the user location information, the virtual print identity manager can select the closest printer to the user.
The information in the virtual print identity record may be filled and updated by various methods. One way is for the user to enter some, or all, of the data through a print identity management portal 500 shown in
An example of an ePrint Centre is shown in more detail in
In the illustrated example, the memory 510 of the ePrint Centre stores the virtual print identity accounts 540. Each virtual print identity account may comprise a table listing printers currently associated with that virtual print identity and rules indicating which printers are to be used to print a print job sent to said virtual print identity. The information in the user account may be sent to the virtual print identity database 300 and/or server 10 proactively (e.g. periodically or each time the account is updated) or on request. In an alternative arrangement the virtual print identity accounts may not be stored locally on the ePrint Centre, but the ePrint Centre may instead simply transmit data to and retrieve data from the virtual print identity database 300.
Another way to update the information in a virtual print identity record is for a user's device to dynamically update the user location by sending updates to the virtual print identity database. For example, the user location may be synched periodically or when a print job is instructed. The user location may for example be detected by GPS, from the IP or network address of the user device, or by location information derived from the telecommunications network used by the user device. In another example the user location may be determined from a diary of the user stored on the user device or a diary stored elsewhere in a computer network.
If it is detected that a user has moved to a significantly different location (e.g. to another city), then the virtual print identity manager, ePrint Centre or user device may search for printers in the new location to be associated with the virtual print identity. The virtual print identity record may then be updated. In one example the user is given a list of printers in the new location and asked to select one or more to associate with the virtual print identity. Where user input is required this may be handled by an application on the user device. Printers in the new location may found by referring to a printer database 600 such as that shown in
At 900 the virtual print identity manager receives a print job addressed to a virtual print identity handled by the server. At 910 the VPI manager checks if it has up to date information relating to the virtual print identity, if not then information (e.g. the VPI record) is retrieved from the virtual print identity database 300. At 920 the VPI manager checks the location of the user associated with the virtual print identity, e.g. it may retrieve the location data from the VPI record, retrieve information by GPS or the telecommunications network or query the user device.
At 930 the VPI manager determines the type of print job, e.g. whether the print job is a work or personal print job (which may be relevant for billing purposes), or whether the print job is primarily composed of graphics or text (which may be relevant for selecting which printer to use). This may be done automatically by examining the content or title of the print job or by querying the user for example.
At 940 the VPI manager checks if the print job is a print job which requires a print permission. If it is a print job which requires a print permission then the VPI manager contacts the print permission database to check whether the virtual print identity has permission to print the print job. If the VPI has permission then the process continues to 950, otherwise the person who sent the print job is informed that the virtual print identity does not have permission to print the print job.
At 950 the VPI manager selects a printer on which to print the print job based on parameters of the virtual print identity. One example of a process for selecting a printer is given in
At 960 the VPI manager makes the print job available to the selected printer. This may for instance be done by actively sending the print job to the selected printer, sending the print job to a memory accessible to the selected printer, or by notifying the selected printer of the location of the print job (e.g. a location in a memory of the server) so that the printer can read the contents of the print job at its own pace.
At 970 the VPI manager sends usage information to the print metering database 800. The usage account of the virtual print identity is thus updated. For example the VPI manager may count the number of pages printed and send this information to the usage database together with information indicating whether the print job was a personal print job or work print job. The print location and any other relevant information may also be logged. The print metering database may later be used to generate billing information for billing the user associated with the virtual print identity.
At 980 the user who owns the virtual print identity is notified that the print job has been printed. The notification may also inform the user which printer the print job was printed on. The notification may for example be sent by email to an email address of the user. The email address of the user will in most cases be distinct from any email address belonging to the virtual print identity. E.g. if the user is Rajesh then the virtual print identity email address may be rajesh@eprint.com and Rajesh's email address may be rajesh@hp.com.
The modules and machine readable instructions described above are typically embodied as a set of executable instructions which are effected on a machine (e.g. a computer, server or microchip) which is programmed with and controlled by said executable instructions. Such instructions may be loaded for execution on a processor (such as one or more CPUs). The term ‘processor’ includes microprocessors, microcontrollers, processor modules or subsystems (including one or more microprocessors or microcontrollers), or other control or computing devices. A “processor” can refer to a single component or to plural components
In some examples, the methods illustrated herein and data and instructions associated therewith are stored in respective storage devices, which are implemented as one or more non-transitory computer-readable or computer-usable storage media or mediums. The storage media may include different forms of memory including semiconductor memory devices such as DRAM, or SRAM, Erasable and Programmable Read-Only Memories (EPROMs), Electrically Erasable and Programmable Read-Only Memories (EEPROMs) and flash memories; magnetic disks such as fixed, floppy and removable disks; other magnetic media including tape; and optical media such as Compact Disks (CDs) or Digital Versatile Disks (DVDs). Note that the machine readable instructions discussed above can be provided on one non-transitory computer-readable or computer-usable storage medium, or alternatively, can be provided on multiple non-transitory computer-readable or computer-usable storage media distributed in a large system having possibly plural nodes. Such non-transitory computer-readable or computer-usable storage medium or media is (are) considered to be part of an article (or article of manufacture). An article or article of manufacture can refer to any manufactured single component or multiple components.
While certain specific examples have been given above it is understood that variations could be made by a person skilled in the art while keeping within the general spirit and purpose of the above examples. For example rather than having a rule to determine printer selection directly by time of day, the virtual print identity manager could refer to a diary associated with the virtual print identity and the diary could indicate the user location at particular times of day. A printer could then be selected on a location basis. Further while
Number | Date | Country | Kind |
---|---|---|---|
1490/CHE/2011 | Apr 2011 | IN | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/IN2011/000423 | 6/23/2011 | WO | 00 | 10/29/2013 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2012/147089 | 11/1/2012 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6337745 | Aiello, Jr. et al. | Jan 2002 | B1 |
6552813 | Yacoub | Apr 2003 | B2 |
6909518 | Miller et al. | Jun 2005 | B2 |
6975419 | Staas et al. | Dec 2005 | B2 |
6993562 | Treptow | Jan 2006 | B2 |
7019861 | Aagesen | Mar 2006 | B2 |
7079276 | Kimura | Jul 2006 | B2 |
7084997 | Clough | Aug 2006 | B2 |
7088462 | Bhogal et al. | Aug 2006 | B2 |
7096265 | Simpson et al. | Aug 2006 | B2 |
7167264 | Takamiya | Jan 2007 | B2 |
7187462 | Oakeson et al. | Mar 2007 | B2 |
7321437 | Parry | Jan 2008 | B2 |
7441003 | Takeda et al. | Oct 2008 | B1 |
7474423 | Garcia et al. | Jan 2009 | B2 |
7503636 | Ferguson et al. | Mar 2009 | B2 |
7656547 | Kuo et al. | Feb 2010 | B2 |
7746496 | Henry | Jun 2010 | B2 |
7760385 | Yamaguchi | Jul 2010 | B2 |
7791747 | Roksz | Sep 2010 | B2 |
8179549 | Evans | May 2012 | B1 |
8195540 | Henry | Jun 2012 | B2 |
8275100 | Henry | Sep 2012 | B2 |
8621549 | Lim | Dec 2013 | B2 |
8773698 | Oshima | Jul 2014 | B2 |
8914450 | Buchheit | Dec 2014 | B1 |
20020051180 | Shimbori et al. | May 2002 | A1 |
20020057449 | Chapman et al. | May 2002 | A1 |
20030011801 | Simpson et al. | Jan 2003 | A1 |
20030063309 | Parry | Apr 2003 | A1 |
20030107762 | Kinoshita et al. | Jun 2003 | A1 |
20030160977 | Nishikawa et al. | Aug 2003 | A1 |
20040073574 | Shimizu et al. | Apr 2004 | A1 |
20040126165 | Carroll | Jul 2004 | A1 |
20040218201 | Lermant et al. | Nov 2004 | A1 |
20040218213 | Shimizu | Nov 2004 | A1 |
20050270569 | Hayashi | Dec 2005 | A1 |
20050275876 | McLean et al. | Dec 2005 | A1 |
20060158681 | Yorimoto et al. | Jul 2006 | A1 |
20060250631 | Igarashi | Nov 2006 | A1 |
20060250638 | Wang et al. | Nov 2006 | A1 |
20060265473 | Muto | Nov 2006 | A1 |
20070086038 | Matsuzaki | Apr 2007 | A1 |
20070146763 | Yokoyama | Jun 2007 | A1 |
20080062883 | Shima | Mar 2008 | A1 |
20080204793 | Shaw | Aug 2008 | A1 |
20090009802 | Shaw et al. | Jan 2009 | A1 |
20090027700 | Kim et al. | Jan 2009 | A1 |
20090172143 | Ishimoto | Jul 2009 | A1 |
20090219570 | Fujisawa | Sep 2009 | A1 |
20090248632 | Subramanian | Oct 2009 | A1 |
20090273810 | Gupta et al. | Nov 2009 | A1 |
20100020349 | Carroll | Jan 2010 | A1 |
20100309510 | Hansen | Dec 2010 | A1 |
20100328707 | Miyake | Dec 2010 | A1 |
20110007347 | Kamath et al. | Jan 2011 | A1 |
20110013219 | Nuggehalli et al. | Jan 2011 | A1 |
20110063668 | Shirai | Mar 2011 | A1 |
20110096354 | Liu | Apr 2011 | A1 |
20110145351 | Lee et al. | Jun 2011 | A1 |
20110231473 | Narayanan et al. | Sep 2011 | A1 |
20120057204 | Mizoguchi et al. | Mar 2012 | A1 |
20120102413 | Gnanamoorthy | Apr 2012 | A1 |
20120206765 | Nakajo | Aug 2012 | A1 |
20120250074 | Kamppari et al. | Oct 2012 | A1 |
20120250076 | Kumar | Oct 2012 | A1 |
20120272339 | Kumaravel et al. | Oct 2012 | A1 |
20130107312 | Venkatesh | May 2013 | A1 |
20130182281 | Suzuki | Jul 2013 | A1 |
20130308165 | Venkatesh | Nov 2013 | A1 |
20130321855 | Bhatia | Dec 2013 | A1 |
Number | Date | Country |
---|---|---|
101004668 | Jul 2007 | CN |
101237424 | Aug 2008 | CN |
101520829 | Sep 2009 | CN |
2007133817 | May 2007 | JP |
20060109699 | Jun 2007 | KR |
WO-0041064 | Jul 2000 | WO |
WO-2012112159 | Aug 2012 | WO |
WO-2012147089 | Nov 2012 | WO |
Entry |
---|
“Automatic Print Email”, Namtuk, 2011; http://www.automatic-print-email.com/. |
“Cloud printing in the enterprise: Liberating the mobile print experience from cables, operating systems and physical boundaries”, Hewlett-Packard Development Company, L.P., Mar. 2010. |
International Search Report and Written Opinion dated Feb. 9, 2012 issued on PCT Patent Application No. PCT/IN2011/000423 filed on Jun. 23, 2011, The State Intellectual Property Office, the P.R. China. |
Aranda, D.M., “Architectures for Cloud Providers Federation—Authorization of Diffusion,” (Research Paper), Sep. 2011, http://eprints.ucm.es/13513/1/DanielMolina—master.pdf. |
EQUITRAC, “Rules & Routing,” 2010, 2 pages found at http://www.equitrac.com/downloads/5379-Rules-Routing—7-10.pdf. |
Experts Exchange, “Setting up multiple printers using same IP address with different ports,” Apr. 29, 2010, http://www.experts-exchange.com/OS/Microsoft—Operating—Systems/Server/2003—Server/Q—26107790.html. |
Extended European Search Report received in EP Application No. 11864184, Sep. 8, 2014, 9 pages. |
Google, “Printing Overview,” (Web Page), 3 pages, 2012, found at http://support.google.com/chromeos/a/bin/answer.py?hl=en&topic=1329532&p=mkt—enterprise&answer=1329533. |
Hewlett-Packard Company, “Print where business happens,” (Research Paper), Jul. 5, 2012. |
Hewlett-Packard Development Company, L.P., “HP Universal Print Driver,” Solution and Feature Guide, 2009, 24 pp., http://h20331.www2.hp.com/Hpsub/downloads/UPD5—guide—final,%20web.pdf. |
International Preliminary Report on Patentability received in PCT Application No. PCT/IN2011/000423, Nov. 7, 2013, 6 pages. |
International Preliminary Report on Patentability received in PCT Application No. PCT/US2011/025293, Aug. 29, 2013, 6 pages. |
International Search Report & Written Opinion received in PCT Application No. PCT/US2011/025293, Sep. 29, 2011, 9 pages. |
PRINTECH, “Intelligent Print Job Routing,” (Web Page), 2009, found at http://www.printech.com/intelligent—print—job—routing.htm. |
RICOH, “doc-Q-manager, The Enterprise-wide Network Solution for Effective Print Job Management,” Printing Solutions for Aficio Series, available Oct. 3, 2006 at http://www.ricoh-photocopiers.co.uk/Print—Managment/DocQManagerBro. |
Schwartz, J. et al., “IBM Launches Enterprise Cloud Services,” Jun. 16, 2009, 3 pages. |
Silveria, L., “Itinerary not displaying in account,” TripIt Help Center, Nov. 9, 2009, 2 pages, found at https://tripit.zendesk.com/entries/77324-Itinerary-not-displaying-in-account. |
Trapani, G., “TripIt Organizes Your Travel Itinerary Automatically via Email,” Lifehacker, Sep. 18, 2007, 3 pages, found at http://lifehacker.com/300833/tripit-organizes-your-travel-itinerary-automatically-via-email. |
Wikipedia, “HP ePrint,” Oct. 16, 2011, found at <https://web.archive.org/web/20111016081246/http://en.wikipedia.org/wiki/HP—ePrint>. |
Wikipedia, “Posterous,” Dec. 10, 2010, 3 pages, found at http://en.wikipedia.org/w/index.php?title=Posterous&oldid=401625056. |
Wolber, A., “Print anywhere: Chrome, Google Apps and Cloud Print,” (Web Page), Oct. 9, 2012, found at http://www.techrepublic.com/blog/google-in-the-enterprise/print-anywhere-chrome-google-apps-and-cloud-print/. |
XEROX®, “Xerox® Mobile Print,” (Web Page), 2011, found at http://www.office.xerox.com/software-solutions/xerox-mobile-print-solution/enus.html. |
Number | Date | Country | |
---|---|---|---|
20140063553 A1 | Mar 2014 | US |