U.S. patent application number 13/276065 was filed with the patent office on 2012-04-19 for managing printer feedback in a distributed printing environment.
This patent application is currently assigned to Aventura HQ, Inc.. Invention is credited to Joe Jaudon, David Lowrey, Adam Williams.
Application Number | 20120092722 13/276065 |
Document ID | / |
Family ID | 45933926 |
Filed Date | 2012-04-19 |
United States Patent
Application |
20120092722 |
Kind Code |
A1 |
Jaudon; Joe ; et
al. |
April 19, 2012 |
MANAGING PRINTER FEEDBACK IN A DISTRIBUTED PRINTING ENVIRONMENT
Abstract
Methods, systems, and devices are described for dynamic print
server generation in a distributed printing environment. In these
methods, systems, and devices, a print router may receive a print
job from a print source over a unidirectional print data path. The
print router may transmit the print job to a print job destination
associated with a printer of a number of printers in communication
with the print router. The print router may receive a message from
the printer and transmit the message from the printer to the print
job source over a network path separate from the unidirectional
print data path.
Inventors: |
Jaudon; Joe; (Sedalia,
CO) ; Lowrey; David; (Denver, CO) ; Williams;
Adam; (Aurora, CO) |
Assignee: |
Aventura HQ, Inc.
Denver
CO
|
Family ID: |
45933926 |
Appl. No.: |
13/276065 |
Filed: |
October 18, 2011 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61394264 |
Oct 18, 2010 |
|
|
|
Current U.S.
Class: |
358/1.15 |
Current CPC
Class: |
G06F 3/1204 20130101;
G06F 3/1288 20130101; G06F 3/12 20130101; G06F 3/126 20130101; G06F
3/1225 20130101; G06F 3/122 20130101 |
Class at
Publication: |
358/1.15 |
International
Class: |
G06F 3/12 20060101
G06F003/12 |
Claims
1. A distributed printing system, comprising: a plurality of
printers; a print job source configured to generate a print job; a
backend in communication with the print job source, the backend
configured to: receive the print job from the print job source; and
transmit the print job over a unidirectional print data path to a
print router; and the print router in communication with a
plurality of print job destinations associated with the plurality
of printers, wherein the print router is configured to: receive the
print job from the backend over the unidirectional print data path
of the backend; transmit the print job to a print job destination
associated with a printer of the plurality of printers; receive a
message from the printer; and transmit the message from the printer
to the print job source over a network path separate from the
unidirectional print data path.
2. The system of claim 1, wherein the print router is further
configured to: append a network address associated with the print
job source to the message from the printer.
3. The system of claim 1, wherein the print router is further
configured to: communicate with a central data store to retrieve a
shared library associated with the printer.
4. The system of claim 3, wherein the print router is further
configured to: call at least one function in the shared library for
transmitting the message from the printer to the print job
source.
5. The system of claim 3, wherein the print router is further
configured to: call at least one function in the shared library to
generate a dialogue box associated with the message; and provide
the dialogue box to the print job source.
6. A method of printing in a distributed printing environment,
comprising: receiving a print job at a print router from a print
job source over a unidirectional print data path; transmitting the
print job from the print router to a print job destination
associated with a printer of a plurality of printers in
communication with the print router; receiving a message from the
printer; and transmitting the message received from the printer to
the print job source over a network path separate from the
unidirectional print data path.
7. The method of claim 6, further comprising: appending a network
address associated with the print job source to the message from
the printer.
8. The method of claim 7, further comprising: encapsulating the
message within at least one packet directed to the network address
associated with the print job source.
9. The method of claim 7, further comprising: identifying the
network address associated with the print job source based on at
least one attribute of the print job.
10. The method of claim 6, further comprising: communicating with a
central data store to retrieve a shared library associated with the
printer.
11. The method of claim 10, further comprising: calling at least
one function of the shared library for transmitting the message
from the printer to the print job source.
12. The method of claim 10, further comprising: calling at least
one function of the shared library to generate a dialogue box
associated with the message; and providing the dialogue box to the
print job source.
13. The method of claim 6, further comprising: determining that the
message from the printer is associated with the print job; and
associating the message from the printer with the print job source
based on an association of the print job source with the print
job.
14. The method of claim 6, wherein the network path separate from
the unidirectional print data path comprises a direct network
connection between the print router and the print job source.
15. The method of claim 6, wherein a central server computer system
comprises the print router.
16. The method of claim 6, wherein the unidirectional print data
path comprises a unidirectional print queue of a backend.
17. The method of claim 6, wherein the print job destination
comprises at least one of the printer or a printer server in
communication with the printer.
18. A print router apparatus, comprising: a print data receiving
module configured to receive a print job from a print job source
over a unidirectional print data path; a print data forwarding
module, communicatively coupled with the print data receiving
module, and configured to transmit the print job from the print
router to a print job destination associated with the printer; a
message receiving module configured to receive a message from the
printer; and a message forwarding module, communicatively coupled
with the message receiving module, and configured to transmit the
message from the printer to the print job source over a network
path separate from the unidirectional print data path.
19. The print router apparatus of claim 18, wherein the message
forwarding module is further configured to: append a network
address associated with the print job source to the message from
the printer.
20. The print router apparatus of claim 18, wherein the message
forwarding module is further configured to: retrieve a shared
library associated with the printer from a central data store; and
call at least one function of the shared library for transmitting
the message from the printer to the print source.
Description
CROSS REFERENCES
[0001] The present application claims priority from U.S.
Provisional Patent Application Ser. No. 61/394,264, which is
incorporated herein by reference in its entirety for all it
discloses.
BACKGROUND
[0002] Embodiments of the invention relate to computer network
communication, and more particularly, printing in a dynamic roaming
environment. Organizations often use a variety of computing
devices. Various computer systems may use a thin-client or a
virtual desktop display in conjunction with a centralized server or
mainframe, and also use traditional workstations and handheld
devices.
[0003] A thin-client may be a computing device that includes
hardware, software, or both in a client-server architecture
network. However, such a network may use a central server for
processing and may transmit and receive input and output over a
network or other communication medium established between the
device and the remote server. In some examples, a thin-client
device may run web browsers or remote desktop software, such that
significant processing may occur on the server.
[0004] Printing in such environments may present a number of
significant challenges. Traditionally, print drivers are stored and
maintained on each device, and this can cause administrative
overhead and maintenance issues. The problem may be exacerbated
with mobile thin-clients and other mobile devices, as the number of
drivers that may need to be stored can increase substantially as
more printers become available.
[0005] There are also challenges related to communicating with
printers in a dynamic environment. For example, in a distributed
printing system, it may be a challenge to receive printer status
updates in a dynamic environment using a unidirectional backend
architecture. Thus, there may be a need in the art for novel system
architectures to address one or more of these issues.
SUMMARY
[0006] Methods, systems, and devices are described for managing
printer feedback in a distributed printing environment.
[0007] In one set of embodiments, a distributed printing system
includes a number of printers, a print job source, a backend in
communication with the print job source, and a print router in
communication with the backend and a number of print job
destinations associated with a number of printers. The backend
receives a print job from the print job source and transmits the
print job over a unidirectional print data path to a print router.
The print router receives the print job from the backend over the
unidirectional print data path of the backend, transmits the print
job to a print job destination associated with one of the printers,
receives a message from the printer, and transmits the message from
the printer to the print job source over a network path separate
from the unidirectional print data path.
[0008] In another set of embodiments, a method of printing in a
distributed printing environment includes receiving a print job at
a print router from a print job source over a unidirectional data
path. The print job is transmitted from the print router to a print
job destination associated with a printer of a plurality of
printers in communication with the print router. A message is
received from the printer, and the message is transmitted to the
print job source over a network path separate from the
unidirectional print data path.
[0009] In another set of embodiments, a print router apparatus
includes a print data receiving module, a print data forwarding
module, a message receiving module, and a message forwarding
module. The print data receiving module is configured to receive a
print job from a print job source over a unidirectional print data
path. The print data forwarding module is communicatively coupled
with the print data receiving module and configured to transmit the
print job from the print router to a print job destination
associated with the printer. The message receiving module is
configured to receive a message from the printer. The message
forwarding module is communicatively coupled with the message
receiving module and configured to transmit the message from the
printer to the print job source over a network path separate from
the unidirectional print data path.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] A further understanding of the nature and advantages of the
present invention may be realized by reference to the following
drawings. In the appended figures, similar components or features
may have the same reference label. Further, various components of
the same type may be distinguished by following the reference label
by a dash and a second label that distinguishes among the similar
components. If only the first reference label is used in the
specification, the description is applicable to any one of the
similar components having the same first reference label
irrespective of the second reference label.
[0011] FIG. 1 is a block diagram illustrating a system for
distributed printing in a dynamic roaming and traditional static
environments, according to various embodiments of the
invention.
[0012] FIG. 2 is a block diagram illustrating a central server
computer system in a system for distributed printing in a dynamic
roaming and traditional static environments, according to various
embodiments of the invention.
[0013] FIG. 3 is a block diagram illustrating a data store in a
system for distributed printing in a dynamic roaming and
traditional static environments, according to various embodiments
of the invention.
[0014] FIG. 4 is a block diagram illustrating a backend in a system
for distributed printing in a dynamic roaming and traditional
static environments, according to various embodiments of the
invention.
[0015] FIG. 5 is a block diagram illustrating a logical path taken
by print data in a system for distributed printing in a dynamic
roaming and traditional static environments, according to various
embodiments of the invention.
[0016] FIG. 6 is a diagram illustrating an example of a system for
managing printer feedback in a distributed printing environment,
according to various embodiments of the invention.
[0017] FIG. 7 is a block diagram illustrating a logical path taken
by a printer feedback message in a system for managing printer
feedback in a distributed printing environment, according to
various embodiments of the invention.
[0018] FIG. 8 is a block diagram illustrating an example of a print
router, according to various embodiments of the invention.
[0019] FIG. 9 is a diagram illustrating an example of a system for
managing printer feedback in a distributed printing environment,
according to various embodiments of the invention.
[0020] FIG. 10 is a flowchart diagram illustrating an example of a
method of printing in a distributed printing environment, according
to various embodiments of the invention.
[0021] FIG. 11 is a flowchart diagram illustrating an example of a
method of printing in a distributed printing environment, according
to various embodiments of the invention.
[0022] FIG. 12 is a flowchart diagram illustrating an example of a
method of printing in a distributed printing environment, according
to various embodiments of the invention.
[0023] FIG. 13 is a schematic diagram that illustrates a
representative device structure that may be used in various
embodiments of the present invention
DETAILED DESCRIPTION OF THE INVENTION
[0024] The present description sets forth examples of systems,
methods, and devices for managing printer feedback in a distributed
printing environment. In these systems, methods, and devices, a
print router receives a print job from a print job source over a
unidirectional print data path. The print router forwards the print
job to a print job destination associated with a printer, and
receives a message from the printer. The message is transmitted to
the print job source over a network path other than the
unidirectional print data path.
[0025] This description provides examples, and is not intended to
limit the scope, applicability or configuration of the invention.
Rather, the ensuing description will provide those skilled in the
art with an enabling description for implementing embodiments of
the invention. Various changes may be made in the function and
arrangement of elements.
[0026] Thus, various embodiments may omit, substitute, or add
various procedures or components as appropriate. For instance, it
should be appreciated that the methods may be performed in an order
different than that described, and that various steps may be added,
omitted or combined. Also, aspects and elements described with
respect to certain embodiments may be combined in various other
embodiments. It should also be appreciated that the following
systems, methods, devices, and software may individually or
collectively be components of a larger system, wherein other
procedures may take precedence over or otherwise modify their
application.
[0027] Systems, devices, methods, and software are described for
managing printer feedback within a distributed printing
environment. In one set of embodiments, shown in FIG. 1, system 100
includes a central server computer system 105, a data store 110,
print servers 145, and printers 150. Each of these components may
be in communication with each other, directly or indirectly.
[0028] The central server computer system 105 may include a rules
engine 130, a session manager 135, and a print router 140. The
central server computer system 105 may be made up of one or more
server computers, workstations, web servers, or other suitable
computing devices. The central server computer system 105 may be
fully located within a single facility or distributed
geographically, in which case a network may be used to integrate
different components.
[0029] The central server computer system 105 may receive a print
job. The print job may be received from a windows session 125.
Alternatively, the print job may be received from an application
session 115 via a backend 120. The print job may also or
alternatively be received from an application session 115 via a
cloud computing environment (not specifically shown). The print job
may be received from thin-clients (e.g., SUN RAY clients available
from Oracle Corporation, WYSE clients available from Wyse
Technology, etc.), thick clients (e.g., desktops, laptops), mobile
devices, tablets, etc., although these devices are not specifically
shown in the diagram Moreover, the print job may be received from
any type of desktop or virtual desktop environment. Examples of
suitable desktop environments from which the print job may be
received include, but are not limited to, LINUX environments based
on the open-source Linux kernel; WINDOWS environments based on
software available from Microsoft, Inc.; OS/X environments based on
software available from Apple, Inc.; VMWARE virtual environments
based on software available from VMware, Inc.; CITRIX virtual
environments based on software available from Citrix Systems, Inc.;
Windows Terminal Services/Remote Desktop virtual environments based
on software available from Microsoft, Inc.; ANDROID environments
based on software available from Google, Inc.; IOS environments
based on software available from Apple, Inc.; WEBOS environments
based on software available from Hewlett Packard Company;
combinations thereof; and the like. In some embodiments, the
central server computer system 105 may receive notice or
identification for a print job, and perform the functionality
described herein based on such notice or identification only.
[0030] A set of drivers may be stored at data store 110. Data store
110 may be a single database, or may be made up of any number of
separate and distinct databases. The data store 110 may include
one, or more, relational databases or components of relational
databases (e.g., tables), object databases, or components of object
databases, spreadsheets, text files, internal software lists, or
any other type of data structure suitable for storing data. Thus,
it should be appreciated that a data store 110 may each be multiple
data storages (of the same or different type), or may share a
common data storage with other data stores. Although in some
embodiments the data store 110 may be distinct from a central
server computer system 105, in other embodiments it may be
integrated therein to varying degrees.
[0031] As noted above, notification of a requested print job may be
received at the central server computer system 105. A session
manager 135 may receive the notification, and may assign a terminal
identifier (TID) to a device requesting the job. The central server
computer system 105 may identify information about the print job
(e.g., identification and location of the applicable print server
145 and printer 150, and identification of the proper driver).
Drivers for the print job may be transmitted to the appropriate
print server 145 and to the client device requesting the job. The
drivers may be installed, and the device and print server 145 may
execute the print job with the installed drivers. Thus, the central
server computer system 105 may access the data store 110 to
distribute drivers to the print server 145 or the device, and thus
in some embodiments the drivers do not need to be maintained on
each device or print server 145. The drivers may be taken down or
uninstalled after each job, set of jobs, or period with no use.
[0032] It should be understood that the print servers 145 may be
any real or virtual machine or environment that hosts a print
driver for controlling a printer 150. Thus, in certain examples a
print server 145 may be implemented by circuitry, logic, and/or
software within the printer 150. Additionally or alternatively, a
print server 145 may include a real or virtual network server
and/or a personal computing device in communication with a printer
150.
[0033] In some embodiments, the central server computer system 105
may use the information about a print job to identify an
appropriate operating system (OS) and print driver for the print
server for a given print job. The central server computer system
105 may access the data store 110 to retrieve the operating system
and print driver, and build an operating system in real-time in
response to receiving a print job. The central server computer
system 105 may install the appropriate driver, thus creating a
virtual print server (which may, but need not be, print server
145). The virtual print server executes the print job. After the
print job is complete, the driver and operating system may be taken
down.
[0034] In some embodiments, a printer 150 is selected (e.g.,
automatically or by a user). The print router 140 at the central
server computer system 105 may receive the selection. At the print
router 140, the selected printer may be mapped to a 1) driver of a
table of drivers, and 2) a print server 145 of a table of print
servers. In certain examples, this mapping may be performed based
on static relationships between printers, drivers, and print
servers. For example, these static relationships may be stored as
tables within the data store 110.
[0035] Additionally or alternatively, a rules engine 130 at the
central server computer system 105 may be used in the selection of
the printer. The rules engine 130 may be configured to dynamically
map a print job to a print server 145 and printer 150 for the print
job. By way of example, upon notification or receipt of the print
job, the rules engine 130 may access a set of rules to determine
the correct print server 145 and printer 150 for the print job. The
rules may dynamically make this determination based on the location
of the device. The type of device, attributes of the print job, and
other factors may be used by the rules engine 130 to determine the
correct type and location for the print server 145 and printer 150.
This rules engine 130 functionality may not be necessary in all
embodiments of the invention to identify an appropriate printer
150, print server 145, or driver for a print job. Accordingly, the
rules engine 130 may be eliminated from certain embodiments.
[0036] In some embodiments, feedback from a printer 150 is received
at the print server 145, and then forwarded on to a print router
140. The print router 140 may route the feedback (e.g., job failed,
out of ink, out of paper, etc.) to the client device. This report
may be in the form of a dialogue box. The feedback may be routed to
avoid the backend 120, even when the print job is initially routed
through the backend 120. In response to feedback from a print
router 140, a client device may direct or route a print job. This
routing may be to a new printer, or may call up alternative
functionality (e.g., a new tray) for a printer that is already in
use. Thus, instead of unidirectional printing, print jobs (e.g.,
sent through a backend 120) may be controlled by two-way
communication between the print router 140 and the device.
[0037] The components of the system 100 may be directly connected,
or may be connected via a network (not shown), which may be any
combination of the following: the Internet, an IP network, an
intranet, a wide-area network ("WAN"), a local-area network
("LAN"), a virtual private network, the Public Switched Telephone
Network ("PSTN"), or any other type of network supporting data
communication between devices described herein, in different
embodiments. A network may include both wired and wireless
connections, including optical links. Many other examples are
possible and apparent to those skilled in the art in light of this
disclosure. In the discussion herein, a network may or may not be
noted specifically. If no specific means of connection is noted, it
may be assumed that the link, communication, or other connection
between devices may be via a network.
[0038] Session manager 135 may include an API architecture which
serves as the communication control point, managing virtual desktop
sessions and brokering sessions for clients to backend 120 virtual
desktop and application sessions. The session manager 135 may
broker and pass through mechanisms for client devices to active
virtual sessions. The central server computer system 105 may
include a centralized management console (not shown), which may be
a web-based management console for configuration, real time
monitoring, and reporting. There may be management capabilities for
the entire virtual desktop/application environment.
[0039] FIG. 2 shows a block diagram of a central server computer
system 105-a. The central server computer system 105-a may be one
example of the central server computer system 105 in FIG. 1. The
central server computer system 105-a shown in FIG. 2 includes a
rules engine 130, a session manager 135, a print router 140-a, and
a print server manager 205. The rules engine 130 and the session
manager 135 shown in FIG. 2 may be substantially the same as the
rules engine 130 and the session manager 135 shown in FIG. 1. The
print router 140-a may be one example of the print router 140 shown
in FIG. 1.
[0040] The print router 140-a may match print jobs received from
external sessions 115, 125 to one or more destination printers 150
and/or print servers 145. To accomplish these tasks, the print
router 140-a may include at least a print data receiving module
210, a print source identification module 215, a print parameters
identification module 220, a printer destination identification
module 225, and a printer feedback routing module 230.
[0041] The print data receiving module 210 may be configured to
receive print data corresponding to a print job from an external
session 115, 125 via a communication channel established by the
session manager 135. In certain embodiments, the print data
received from the external session 115, 125 may be in the form of
one or more page description languages (PDLs). Examples of page
description languages that may be received at the receiving module
210 include, but are not limited to, PostScript, Portable Document
Format (PDF), Printer Command Language (PCL), Scalable Vector
Graphics (SVG), Open XML Paper Specification (XPS), and any other
page description language that may suit a particular implementation
of the principles described herein.
[0042] In other embodiments, the print data received from the
external session 115, 125 may be in the form of text or images for
use with a standard template stored by a print server 145 or a
printer 150. For example, the print data may be used to print a
personalized bracelet worn by a patient in a medical facility. In
this example, the print data may include text corresponding to the
name of the patient, and the name of the patient's doctor. This
text, when received by a print server 145 or a printer 150, may be
applied to a standard bracelet template to print a bracelet having
the name of the patient and the name of the patient's doctor.
[0043] In additional or alternative embodiments, the print data
received by the print data receiving module 210 may be in the form
of an image that has already been rasterized by the external
session 115, 125 in preparation for delivery to a printer 150.
[0044] The print data receiving module 210 may be configured to
cache the received print data at a designated storage area. In
certain examples, the designated storage area may be in a data
store 110. The cached print data may be accessible to the rules
engine 130 or any other module or process.
[0045] The print source identification module 215 may be configured
to analyze the received print data to determine certain attributes
or characteristics of the received print data. These attributes or
characteristics may also be stored for use by the other modules or
processes. For example, the print source identification module 215
may associate the received print data with a format in the data
store 110. This format information may be available to the rules
engine 130 for use in enforcing one or more rule sets.
[0046] In certain examples, the print source identification module
215 may analyze the print data received by the print data receiving
module 210 to determine a source of the print data. By way of
example, the source may be determined using information from the
session manager 135, information acquired by the print data
receiving module 210, and/or information attached to the print data
itself by the source. Once the print source has been identified,
the identity of the print source may be associated with the
received print data. For example, the identity of the print source
may be stored in the data store 110.
[0047] The print parameters identification module 220 may identify
certain print parameters for the received print data. These print
parameters may be included with the received print data and/or
determined by logical deduction (e.g., using the rules engine 130).
For instance, a user of an external session 115, 125 may specify a
particular print parameter which may be transmitted to the central
server computer system 105-a with the print data or logically
deduced from the received print data. Additionally or
alternatively, certain default print parameters may be determined
for the print data based on the identity of the source of the print
data and/or another attribute associated with the print data.
[0048] Examples of print parameters that may be identified by the
print parameters identification module 220 include, but are not
limited to, a selected type of printing media, a selected size of
printing media, a selected source of printing media, an ink or
toner color setting, a collation setting, a staple setting, a
duplex setting, a scaling setting, combinations thereof, and the
like.
[0049] The printer destination identification module 225 may be
configured to identify an appropriate destination printer 150
and/or print server 145 for print data received at the print data
receiving module 210. The printer destination identification module
225 may identify the appropriate destination printer 150 based on
one or more attributes of the print data. In certain examples, the
printer destination identification module 225 may pass certain
attributes of the print data (e.g., the identity and/or location of
the source of the print data determined by the print source
identification module 215, the print parameters determined by the
print parameters identification module 220, etc.) to the rules
engine 130.
[0050] The rules engine 130 may apply a certain set of
predetermined or dynamically updated rules to the input it receives
from the printer destination identification module 225 to determine
the destination printer 150 and/or print server 145 for the print
data. The destination printer 150 and/or print server 145
determined by the rules engine 130 may then be returned to the
printer destination identification module 225.
[0051] Alternatively, instead of using a rules engine 130, the
printer destination identification module 225 may identify the
appropriate destination printer 150 based on static associations
between certain attributes and certain destination printers
150.
[0052] Once the destination printer 150 and/or print server 145 has
been identified for the print data, the print data forwarding
module 230 may be configured to forward the print data on to the
identified printer 150 and/or print server 145. The print data may
be forwarded over a local connection and/or over a network or
logical connection. Additionally, in certain examples, the print
data forwarding module 230 may be configured to receive feedback
from a printer 150 and/or a print server 145 about a specific print
job and process the feedback and/or forward the feedback to a third
party, such as the source of that particular print job.
[0053] The print server manager 205 of the central server computer
system 105-a may handle certain aspects related to the distribution
of drivers for printers to the print servers 145 and the general
maintenance of the print servers 145. Accordingly, the print server
manager 205 may include a driver identification module 235, a
driver deployment module 240, an operating system identification
module 245, and a print server instantiation module 250.
[0054] The driver identification module 235 may, in response to a
set of print data being assigned to a particular printer 150,
determine an appropriate driver for that printer 150. As described
above with regard to FIG. 1, the appropriate driver may be selected
from a central repository of drivers stored, for example, at data
store 110. The driver identification module 235 may be further
configured to determine whether an appropriate driver for the
selected printer 150 is already installed on a print server 145
chosen to send the print data to the selected printer 150. In
certain examples, the driver identification module 235 may compare
a version of the driver stored by the chosen print server 145 with
a version of the driver stored at the central repository to
determine whether the driver stored by the chosen print server 145
is current.
[0055] In the event that a determination is made that the chosen
print server 145 does not have the appropriate driver or a correct
version of the appropriate driver, the driver deployment module 240
may install the appropriate driver on the print server 145. In
certain examples, the driver deployment module 240 may access and
write to storage associated with the print server 145 via a local
connection, network connection, and/or a logical connection to
install the appropriate driver to the print server 145.
[0056] The operating system identification module 245 may be
configured to identify an appropriate operating system associated
with an appropriate driver for the selected printer 150. In the
event that a print server 145 running the appropriate operating
system and in communication with the selected printer 150 does not
exist or is unavailable, the print server instantiation module 250
may instantiate a new print server 145. The newly instantiated
print server 145 may be created on a dedicated or virtual machine
by loading the appropriate operating system to the dedicated or
virtual machine. In certain examples, an operating system image
having the appropriate driver preinstalled may be used to
instantiate the new print server 145.
[0057] FIG. 3 is a block diagram of one example of a data store
110-a that may be associated with a central server computer system
105. The data store 110-a shown in FIG. 3 may be an example of data
store 110 shown in FIG. 1. As shown in FIG. 3, data store 110-a may
store drivers 305, libraries 310, device configurations 315, tables
320, rules 325, and operating system images 330.
[0058] Data store 110-a may maintain a repository of drivers 305
for various printers 150 supported by a distributed printing system
100. In accordance with the description of FIGS. 1-2, as a print
job is received at the central server computer system 105, the
central server computer system 105 may associate the print job with
a specific printer 150, dynamically access the data store 110 to
retrieve a driver 305 appropriate for the specific printer, and
provide the retrieved driver 305 to a print server 145 associated
with the specific printer.
[0059] Because the drivers 305 are stored centrally at data store
110-a, individual machines implementing sessions 115, 125 and
individual print servers 145 need not store a local print driver
for each printer supported by the system 100. Moreover, as updated
versions of drivers 305 become available, a network administrator
may make the updated versions available to each print server 145 in
the system by simply updating the repository of drivers 305 stored
at the data store 110-a, thereby avoiding the need to roll out
driver updates to each print server 145 separately.
[0060] The data store 110-a may also store software libraries 310.
For example, the data store 110-a may store libraries 310
associated with the drivers 305. In certain embodiments, the
libraries 310 may include Dynamic-Link Library (DLL) or Dynamic
Shared Object (DSO) files that allow the print servers 145 to
dynamically communicate with the sessions 115, 125 which generate
the print jobs sent to printers 150. Thus, where the central server
computer system 105 provides a driver 305 to a print server 145 for
a specific printer 150, the central server computer system 105 may
include with the driver 305 one or more DLL files for that printer
150. The DLL(s) files may allow the print server 145 to provide
feedback to a session 125 from which a print job originates in a
way that is understandable to the session 125. For instance, if a
user of the session 125 generates the print job using a print
Graphical User Interface (GUI), the DLL transmitted to the print
server 145 may allow the print server 145 to provide feedback to
the user of the session 125 through the print GUI.
[0061] By way of example and not limitation, consider the case
where a print job generated by a session 125 has been sent to a
print server 145 for printing by a specific printer 150, and that
the printer 150 is out of paper. The printer 150 may send a
feedback message to the print server 145 indicating that the
printer 150 is out of paper, and the print server 145 may provide
this feedback message to a print dialog window in the session 125
using a DLL received from the central server computer system 105.
This process may allow for a more seamless printing experience for
a user of session 125, despite the fact that the session 125 may
not locally store a print driver or DLL for communicating with the
printer 150.
[0062] In certain examples, the data store 110-a may also store
device configurations 315, such as settings configurations for
printers 150. Thus, when the central server computer system 105
transmits a print job to a print server 145 associated with a
specific printer 150, the central server computer system 105 may
also include in the transmission a configuration 315 retrieved from
the data store 110-a for that printer 150. The configuration 315
may specify, for example, settings such as printer margin settings,
duplex settings, paper tray settings, ink color settings, collation
settings, and the like. The configuration 315 transmitted to the
print server 145 by the central server computer system 105 may be
specific to the printer 150, the session 115, 125 generating the
print job, and/or the character or content of the print job
itself.
[0063] Additionally, the data store 110-a may store and maintain
various tables 320. The tables 320 may reflect certain
relationships present in the system 100. For example, the tables
320 may include one or more tables 320 associating specific
sessions 115, 125 with terminal identifiers or node identifiers,
one or more tables 320 associating specific sessions 115, 125 with
physical locations, one or more tables 320 associating specific
printers 150 or print servers 145 with physical locations, one or
more tables 320 associating specific sessions 115, 125 with default
printers 150, and/or one or more tables 320 tracking any other
association in the system 100 that may suit a particular
implementation of the principles described herein.
[0064] In certain examples, two or more of the tables 320 stored by
the data store 110-a may be interrelated in such a way that allows
for logical deductions in routing print jobs to print servers 145
or other useful purposes. For instance, the data store 110-a may
include: a) a first table 320 associating each terminal identifier
at a port with a particular session 115, 125 at a specific physical
location; and b) a second table 320 associating each physical
location for a session 115, 125 with a default printer 150. In this
case, the information in the first table 320 and the second table
320 may be used by the central server computer system 105 to
associate a print job received at a port with a specific default
printer 150.
[0065] The data store 110-a may also include one or more rules 325
for use by the central server computer system 105 in routing
received print jobs to print servers 145 and printers 150. As noted
above in the description of FIGS. 1-2, the rules engine 130 of the
central server computer system 105 may be configured to dynamically
map a print job to a print server 145 and printer 150 for the print
job by accessing the set of rules 325 stored in the data store
110-a. The rules 325 may take into account factors such as the
location of the device generating the print job, the type of device
generating the print job, attributes of the print job, and other
factors. Some of these factors may be stored in the tables 320.
[0066] Additionally, the data store 110-a may include one or more
operating system images 330. The operating system images 330 may be
used, for example, in the dynamic creation of print servers 145. As
described above, certain drivers 305 may not be compatible with the
standard operating systems executed by typical print servers 145 in
the system 100. Accordingly, when a print job is indicated for a
printer 150 using one of these drivers 305, the central server
computer system 105 may retrieve a compatible operating system
image 330 from the data store 110-a and instantiate a new print
server 145 by loading the operating system image 330 onto a real or
virtual machine. The newly instantiated print server 145 may then
receive the print job from the central server computer system 105
and control the indicated printer 150 using the appropriate driver
305 to complete the print job.
[0067] Turning now to FIG. 4, a block diagram is shown of an
illustrative backend 120-a for use in a distributed printing system
100. The backend 120-a shown in FIG. 3 may be an example of the
backend 120 shown in FIG. 1. The backend 120-a may be configured to
forward print data 405 to a next destination in the printing
pipeline, such as a central server computer system 105, a print
server 145, or a printer 150, as described in more detail below. To
accomplish this functionality, the backend 120 may include a
receiving module 410 to receive the print data 405 from an
application session 115, a backend routing module 415 for
determining the next destination of the print data 405, and a
transmission module 425 to transmit the print data 405 to the
determined next destination. In some examples, the backend 120-a
may also include a rasterization module 420 for rasterizing the
print data 405 prior to transmitting the print data 405 to the
central server computer system 105.
[0068] The receiving module 410 of the backend 120-a may be
configured to receive the print data 405 over a channel of
communication with the application session 115. In some examples,
the channel of communication may include one or more local
connections (e.g., serial ports, parallel ports, etc.) between the
backend 120-a and a device implementing the application session
115. Additionally or alternatively, the channel of communication
may include one or more network connections (e.g., Ethernet, WiFi,
etc.) and/or logical connections (e.g., where the receiving module
410 of the backend 120-a and the application session 115 are
implemented by the same physical machine).
[0069] In addition to receiving the print data 405, the receiving
module 410 may also identify the application session 115 providing
the print data 405. For example, the receiving module 410 may
monitor a number of ports associated with various application
sessions 115. Each of the application sessions 115 may be assigned
a terminal identifier or a node identifier. Thus, when print data
405 is received, the receiving module 410 may take note of the
terminal identifier, the node identifier, and/or the port on which
the print data is received to associate the print data 405 with a
known application session.
[0070] The backend routing module 415 may determine the next
destination of the print data 405 based on the application session
115 from which the print data 405 was received. To this end, the
destination identification module 415 may maintain a table
associating specific application sessions 115 with specific
destinations. In certain examples, such as in the system 100 of
FIG. 1, all print data 405 received at the backend 120-a,
regardless of source, may be transmitted by the backend 120-a to a
single central server computer system 105.
[0071] In alternative examples, the backend 120-a may be
communicatively coupled to a number of separate central server
computer systems 105 such that print data 405 from different
application sessions 115 is transmitted by the backend to different
central server computer systems 105. In additional or alternative
examples, the backend 120-a may be communicatively coupled to one
or more central server computer systems 105 in addition to one or
more print servers 145 such that print data 405 from some
application sessions 115 is transmitted to a central server
computer system 105 and print data 405 from other application
sessions 115 is transmitted directly to a print server 145. In
these examples, the backend routing module 415 may determine the
next destination of each instance of print data 405 based on the
application session 115 from which the print data 405 was
received.
[0072] In certain examples, the backend routing module 415 may
further include logic for dynamically determining in real-time how
a print job is to be routed. For example, based on certain
characteristics of the print data 405, the backend routing module
415 may determine that it would be more appropriate to forward the
print data 405 to a central server computer system 105 than to a
print server 145 or printer 150. Additionally or alternatively, in
examples where the backend 120-a is communicatively coupled to
multiple alternative central server computer systems 105, the
backend routing module 415 may perform load balancing in its
distribution of different print jobs between the separate central
server computer systems 105.
[0073] As mentioned above, in certain embodiments the backend 120-a
may include a rasterization module 420. The rasterization module
420 may convert the received print data 405 into a raster image
that can be understood by a printer. In other embodiments, the
print data 405 may already have been rasterized by the application
session 115 from which the print data 405 was received. In still
other embodiments, the print data 405 may be rasterized at a print
server 145 prior to printing.
[0074] The transmission module 425 of the backend 120-a may
transmit the received print data 405 to the destination determined
by the next destination identification module 415. This
transmission may occur over one or more local connections (e.g.,
serial ports, parallel ports), one or more network connections
(e.g., Ethernet, WiFi), and/or one or more logical connections
(e.g., where the backend 120 and the next destination are
implemented by the same physical machine). In certain examples, the
transmission module 425 of the backend 120-a may transmit the print
data to the next destination over a unidirectional print data path
(e.g., using one or more unidirectional print data queues).
[0075] FIG. 5 illustrates a diagram of one illustrative path 500 of
print data 405 through a distributed printing system. The print
data 405 may first be generated and transmitted to a central server
computer system 105-b by a session 125. The central server computer
system 105-b may be an example of the central server computer
system 105 of FIG. 1 or FIG. 2. The session 125 may include an
application executed by a host device. In certain examples, a user
of the application issues a command to print data generated or
hosted by the application.
[0076] In certain embodiments, the session 125 may transmit the
print data 405 directly to the central sever computer system 105-b.
Alternatively, the session 125 may utilize a backend 120 to
transmit the print data 405 to the central server computer system
105. The central server computer system 105-b may perform session
identification 510 to determine the source of the print data 405.
For example, the central server computer system 105-b may look up a
terminal identifier and/or a port associated with the print data
405 in a table to identify a device from which the print data 405
originated.
[0077] Once the source of the print data 405 is known, the central
server computer system 105-b may perform print routing 515 on the
print data 405 to select an appropriate printer 150-a for the print
data 405. The printer 150-a may be an example of one of the
printers 150 shown in FIG. 1. The print routing 515 may include
applying a set of rules to one or more parameters associated with
the print data 405 and/or the identified session 125. Additionally,
the central server computer system 105-b may retrieve 520 an
appropriate driver 305-a for the identified printer 150-a from a
data store 110. The driver 305-a may be transmitted, together with
the print data 405, from the central server computer system 105-b
to a print server 145-a associated with the identified printer
150-a. The print server 145-a may be an example of the print server
145 shown in FIG. 1. In certain examples, as described above, the
print server 145-a may be dynamically instantiated in response to a
particular printer 150-a being selected for the print data 405.
[0078] The print server 145-a may install 530 the driver 305-a
received from the central server computer system 105-b to enable
the print server 145-a to communicate with the selected printer
150-a. Additionally, the print server may perform spooling 535
operations to receive and collect the print data 405, scheduling
540 operations to schedule the print data 405 for printing by the
printer 150-a, and one or more conversion 545 operations to
transform the print data into a format understood by the printer
150-a. In certain examples, the conversion 545 operations may
include rasterization of the print data 405. The print server 145-a
may then transmit the print data 405 to the selected printer 150-a
over a local connection, a network connection, and/or a logical
connection for printing.
[0079] It is worth noting that while an entire distributed printing
system 100 has been described as a whole for the sake of context,
the present specification is directed to methods, systems, and
apparatus that may be used with, but are not tied to the system 100
of FIGS. 1-5. Individual aspects of the present specification may
be broken out and used exclusive of other aspects of the foregoing
description. This will be described in more detail, below.
[0080] In one set of embodiments, systems, devices, methods, and
software are described for managing printer feedback in a
distributed printing environment. The examples below illustrate
novel messaging techniques to route printer feedback related to a
print job back to a user, session, or device that generated the
print job. FIG. 6 illustrates an example system 600 for receiving
printer feedback. The system 600 includes a print job source 605, a
backend 120-b, a print router 140-b, and a print job destination
620 associated with a printer 150-b. Each of these components may
be in communication with each other, directly or indirectly. This
system 600 may be an example of the system 100 described above with
reference to FIG. 1, the print router 140-b may be an example of
the print router 140 described above with reference to FIG. 1, 2,
or 5, and the printer 150-b may be an example of the printer 150
described above with reference to FIG. 1 or 5.
[0081] Print job source 605 may transmit 610-a print data for a
print job to backend 120-b (the print data may be directed to a
particular port number). The print job source 605 may be a user or
application session (e.g., sessions 115, 125 of FIG. 1) and/or a
specific device that generates the print data for the print job.
The backend 120-b may include one or more servers, and may be a
Unix or Unix-like environment with a number of unidirectional print
queues. For example, the backend 120-b may include a Unix Transport
Control Protocol/Internet Protocol (TCP/IP) backend that supports
unidirectional print queues based on the Line Printer Daemon/Line
Printer Remote protocol.
[0082] From the backend 120-b, the print data may be transmitted
610-b (again including the port number) along a unidirectional
print path to the print router 140-b. The unidirectional print path
may include one or more unidirectional print queues. The print
router 140-b may receive the print data and associated port, and
may identify the printer to be used based on the port number
(although a number of other print routing techniques may be used in
different embodiments). The print router 140-b may transmit or
otherwise provide the print data 610-c to the print job destination
620. The print job destination 620 is associated with the printer
150-b.
[0083] In certain examples, the print job destination 620 may be a
print server, such as the print server 145 described above with
reference to FIG. 1 or 5. Note, however, that the print job
destination 620 may be a virtual print server, and thus in some
embodiments both the print router 140-b and print job destination
620 may be part of the central server computer system 105 of FIG. 1
or 3. In other examples, the print job destination 620 may be the
printer 150-b itself and/or circuitry or logic within the printer
150-b for receiving the print data for the print job. In examples
where the print job destination 620 is a print server 145, the
print job destination 620 processes the print data, and transmits
610-d the print data to printer 150-b for printing. In examples
where the print job destination is the printer 150-b, the print job
destination 620 may receive and print the print data for the print
job. In still other examples, one or more print job destinations
620 may be associated with different types of printing
functionality (tray selection, ink/toner selection, media
selection, other settings, etc.) for a printer 150. For example, a
single printer 150 may implement one print job destination 620
associated with printing from a first tray and another print job
destination 620 associated with printing from a second tray.
[0084] The printer 150-b may be one of a number of printers 150-b
in communication with the print router 140-b. The printer 150-b may
generate a feedback message or other print related information. For
example, the information may be directly related to the print job
(e.g., job failed, job succeeded, out of paper for targeted tray,
etc.), or more general status information (out of ink, low on
paper, maintenance required, etc.). The feedback message may be
transmitted 615-a through the print job destination 620, and
forwarded 615-b to the print router 140-b. The print router 140-b
may intercept or otherwise receive the feedback. The feedback
message may (directly or indirectly) identify the originating print
job source 605. Alternatively, the print router 140-b may use a
variety of lookup tables or other identifiers to identify the
originating print job source 605.
[0085] Additionally or alternatively, the print router 140-b may
directly or indirectly associate the feedback message with a
particular print job and identify the print job source 605 based on
at least one attribute of the print job. For example, the print
router 140-b may identify the print job source 605 based on the
port with which the print data was originally associated, an
identifier of the print job source 605 or the printer 150-b
included in the print data, a location of the print job source 605
or the printer 150-b, one or more time stamps associated with the
print data, security information included with the print data,
and/or any other possible print job attribute that may suit a
particular implementation of the principles of this
description.
[0086] The print router 140-b routes 615-c the feedback message to
the originating print job source 605. In certain examples, the
print router 140-b may append a network address associated with the
print job source 605 to the feedback message and transmit the
feedback message to the print job source 605 over a network. For
instance, the print router 140-b may encapsulate the feedback
message into one or more layer-2 (e.g., Internet Protocol (IP))
packets and transmit the layer-2 packet(s) over the network to a
layer-2 address associated with the print job source 605.
[0087] The feedback message from the printer 150-b may be in the
form of a dialogue box. For example, dialogue box may be for
display to a user at the print job source 605. The feedback message
may be routed to avoid the unidirectional print data path of the
backend 120-b, even when the print job was initially routed through
the unidirectional print data path of the backend 120-b. The
unidirectional print data of the backend 120-b may be avoided by
transmitting the feedback message to the print job source 605 over
a network path that does not include the backend 120-b or a network
path that uses a different portion of the backend 120-b
network.
[0088] While a backend 120-b was used in FIG. 6 for purposes of
example, the principles set forth above for the backend 120-b would
apply to cloud computing as well. For example, in some embodiments
print data for a print job may be initially transmitted to the
print router 140-b through a unidirectional print data path in a
network cloud, and feedback message from the printer 150-b may be
transmitted from the print router 140-b to the print job source 605
using a path in the network cloud that is separate from the
unidirectional print data path.
[0089] In certain examples, the print job source 605 may transmit a
response to the feedback message to the printer 150-b and/or the
print job destination 620 over the network path separate from the
unidirectional print data path. This response may be first received
by the print router 140-b, and then forwarded on to the print job
destination 620 and/or the printer 150-b. For example, the feedback
message from the printer 150-b may indicate that a targeted tray is
out of paper. After transmitting the feedback message, the printer
150-b may suspend operations and wait for a message from the print
job source 605 indicating that more paper has been placed in the
targeted tray before recommencing printing operations.
[0090] Referring next to FIG. 7, an example of a path 700 for a
feedback message 705 from a printer 150-c to a device 735 is shown.
The path 700 may include a print server 145-b, a print router
140-c, and a network 730. The printer 150-c may be an example of
the printer 150 described above with reference to FIG. 1, 5, or 6
and/or the print job destination 620 described above with reference
to FIG. 6. The print server 145-b may be an example of the print
server 145 described above with reference to FIG. 1 or 5 and/or the
print job destination 620 described above with reference to FIG. 6.
The print router 140-c may be an example of the print router 140
described above with reference to FIG. 1, 2, 5, or 6. The print
router 140-c may be associated with a data store 110-b, which may
be an example of the data store 110 described above with reference
to FIG. 1 or 3. The device 735 may be an example of the print job
source 605 described above with reference to FIG. 6. Additionally,
the device 735 may implement one or more of the sessions 115, 125
described above with reference to FIG. 1.
[0091] The feedback message 705 generated by the printer 150-c may
be transmitted from the printer 150-c to the print server 145-b in
a format understood by the print server 145-b and/or the print
router 140-c. The print server 145-b may forward the feedback
message 705 to the print router 140-c. The print router 140-c may
identify the device 735 as the source (e.g., print job source 605
of FIG. 6) of a print job related to or associated with the
feedback message 705 from the printer 150-c. As described above,
this identification may occur based on a direct or indirect
indication within the feedback message 705 or the print job.
[0092] The print router 140-c may communicate with the data store
110-c to access a dynamic link library (DLL) file 710 from a
repository of shared libraries 310-b stored by the data store
110-c. The DLL file 710 may be associated with the device 735
identified as the print job source, the printer 150-c, and/or the
print server 145-b. In certain examples, the print router 140-c may
query the data store 110-b for the DLL file 710 using at least one
attribute of the device 735, the printer 150-b, or the print server
145-b. The DLL file 710 may provide one or more functions that
allow the print router 140-c to interact with the device 735 such
that the device 735 processes the feedback message 705 in a
particular manner. For example, the print router 140-c may call a
function in the DLL file 711, or cause the device 735 to call a
function in the DLL file 711, that formats the feedback message 705
as a dialogue box for display by the device 735 to a user.
Additionally or alternatively, the print router 140-c may call one
or more functions in the DLL file 711 to communicate the feedback
message 735 to an application running on the device 735.
[0093] In other examples, the printer router 140-c may retrieve a
different type of shared library file for transmitting the message
705 to the device 735. For instance, the print router 140-c may
retrieve a dynamic shared object (DSO) file instead of a DLL file
710 if the device 735 runs Unix or a Unix-like operating system
(e.g., OS/X, Linux).
[0094] The print router 140-c may encapsulate the feedback message
705, as modified or formatted using the DLL file 710, into one or
more IP packets 720 for transmission to the device 735 over the
network 730. The packet(s) 720 may include an IP address 725 for
the device 735. The packet(s) 720 may be transmitted to the device
735 over a network path that is separate from a unidirectional
print data path used by the device 735 to initially transmit the
print job to the print router 140-c. Upon receiving the packet(s)
720 over the network 730, the device 735 may process the feedback
message 705. For example, the device 735 may display the feedback
message 705 to a user in a dialogue window generated with the DLL
file 710.
[0095] Referring next to FIG. 8, a block diagram is shown
illustrating an example of print router 140-d for managing printer
feedback in a distributed printing environment. The print router
140-d may be an example of the print router 140 described above
with reference to FIG. 1, 2, 5, 6, or 7 above. The print router
140-d of the present example includes a print data receiving module
210-a, a print data forwarding module 230-a, a message receiving
module 805, and a message forwarding module 810. Each of these
components may be in communication, directly or indirectly. The
print data receiving module 210-a and the print data forwarding
module 230-a may be examples of the print data receiving module 210
and print data forwarding module 230 described above with reference
to FIG. 2.
[0096] The print data receiving module 210-a may be configured to
receive a print job from a print job source (e.g., print job source
605 of FIG. 6) over a unidirectional print data path. The print job
source may include, for example, an application session or a device
that generates print data. The unidirectional print data path may
include, for example, a unidirectional print queue of a backend
(e.g., backend 120 of FIG. 1, 4, or 6). The print data receiving
module 210-a may receive the print job by receiving print data
generated by the print job source.
[0097] The print data forwarding module 230-a may be configured to
forward the print job to a print job destination (e.g., print job
destination 620 of FIG. 6). The print job destination may be
associated with a printer (e.g., printer 150 of FIG. 1, 5, 6, or 7)
from a plurality of printers in communication with the print router
140-d. As described above, in certain examples the print job
destination may be the printer itself or a print server (e.g.,
print server 145 of FIG. 1, 5, or 7) associated with the
printer.
[0098] The message receiving module 805 may be configured to
receive a message from the printer. The message may be a status or
other printer feedback message. The message may relate to a
specific print job and/or be intended for a specific print job
source. The message receiving module 805 may determine the print
job and/or print job source to which the message relates. In
certain examples, the message received from the printer may
directly or indirectly identify the specific print job and/or print
job source to which the message relates. Additionally or
alternatively, the message receiving module 805 may identify the
print job source based on at least one attribute of the print job
determined from the content of the message or from a locally stored
copy of the print job. Thus, the message receiving module 805 may
determine that the message is associated with a specific print job
and associate the message with a print job source based on a stored
or implied association of the print job source with the print
job.
[0099] The message forwarding module 810 may be configured to
transmit the message received at the message receiving module 805
from the printer to the identified print job source. The message
forwarding module 810 may transmit the message to the print job
source over a network path that is separate from a unidirectional
print data path over which the print job was originally received
from the print job source. In certain examples, transmitting the
message over the network path may include appending a network
address of the print job source to the message and/or encapsulating
the message into one or more network packets directed to the
network address of the print job source. The network address of the
print job source may be dynamically or statically identified based
on at least one attribute of the print job or a mapping table.
[0100] In certain examples, the message forwarding module 810 may
communicate with a central data store (e.g., data store 110 of FIG.
1, 3, or 7) to retrieve a shared library (e.g., libraries 310 of
FIG. 3 or 7, or DLL file 710 of FIG. 7) associated with the
printer. The message forwarding module 810 may call, or instruct
the print job source to call, at least one function in the shared
library for transmitting the message from the printer to the print
job source. For example, the message forwarding module 810 may
call, or instruct the print job source to call, at least one
function in the shared library to generate a dialogue box
displaying the message from the printer at the print job
source.
[0101] Referring next to FIG. 9, a block diagram is shown of an
example of a distributed printing system 900. The system 900 of
this example includes a device 735-a, a backend 120-c, a central
server computer system 105-c, a data store 110-c, and a plurality
of printers 150. Each of these components may be in communication,
directly or indirectly.
[0102] The system 900 may be an example of the systems 100, 600
described above with respect to FIG. 1 or 6. The device 735-a may
be an example of the print job source 605 described above with
respect to FIG. 6. Additionally or alternatively, the device 735-a
may be an example of the device 735 described above with respect to
FIG. 7. The backend 120-c may be an example of the backend 120
described above with respect to FIG. 1, 4 or 6. The central server
computer system 105-c may be an example of the central server
computer system 105 described above with reference to FIG. 1, 2, or
5. The data store 110-c may be an example of the data store 110
described above with reference to FIG. 1, 2, or 7. The printers 150
may be an example of the printers 150 described above with
reference to FIG. 1, 5, 6, or 7 and/or the print job destination
610 described above with respect to FIG. 6.
[0103] As shown in FIG. 9, the central server computer system 105-c
of the present example implements a print router 140-e and a number
of print servers 145. The print router 140-e may be an example of
the print router 140 described above with reference to FIG. 1, 2,
6, 7, or 8, and the print servers 145 may be examples of the print
servers 145 described above with reference to FIGS. 1, 5, and 7,
and/or the print job destination 610 described above with respect
to FIG. 6. In certain examples, the central server computer system
105-c may also implement the data store 110-c.
[0104] The device 735-a may transmit print data for a print job to
the central server computer system 105-c over a unidirectional
print data path 905 associated with the backend 120-c. For example,
the unidirectional data path 905 may include one or more
unidirectional print queues. The print router 140-e implemented by
the central server computer system 105-c may receive the print job,
select one of the print servers 145 as a print job destination, and
transmit the print job to the selected print server 145. The
selected print server 145 may process the print job and transmit
the print job to one of the printers 150 associated with the
selected print server 145 for printing.
[0105] Before, during, or after printing the print job, the printer
150 may provide a status or other feedback message to the
associated print server 145. The associated print server 145 may in
turn forward the message to the print router 140-e. The print
router 140-e may identify the device 735-a as a recipient of the
message from the printer 150, and transmit the message to the
device 735-a over a network path 910 that is separate from the
unidirectional print data path 905. The print router 140-e may
retrieve one or more shared libraries or other auxiliary files from
the data store 110-c for use in transmitting the message to the
device 735-a, as described above.
[0106] Referring next to FIG. 10, a flow chart is shown
illustrating an example of a method 1000 for printing in a
distributed printing environment according to various embodiments
of the invention. This method 1000 may, for example, be performed
in whole or in part by the central server computer system 105 of
FIG. 1, 2, 5, or 9, and/or the print router 145 of FIG. 1, 2, 6, 7,
8, or 9.
[0107] At block 1005, a print job is received at a print router
from a print job source over a unidirectional print data path. In
certain examples, the print job source may be a device or a user or
application session. At block 1010, the print job is transmitted
from the print router to a print job destination associated with a
printer of a plurality of printers in communication with the print
router. In certain examples, the print job destination may be a
printer or a print server. At block 1015, a message is received
from the printer. At block 1020, the message is transmitted from
the printer to the print job source over a network path separate
from the unidirectional print data path.
[0108] Referring next to FIG. 11, a flow chart is shown
illustrating an example of a method 1100 for printing in a
distributed printing environment according to various embodiments
of the invention. This method 1100 may, for example, be performed
in whole or in part by the central server computer system 105 of
FIG. 1, 2, 5, or 9, and/or the print router 145 of FIG. 1, of FIG.
1, 2, 6, 7, 8, or 9.
[0109] At block 1105, a print job is received at a print router
from a print job source over a print data path that includes a
unidirectional network print queue. At block 1110, a printer is
selected from a plurality of printers in communication with the
print router for the print job. At block 1115, the print job is
transmitted from the print job router to a print server associated
with the printer. In certain examples, the print server may be
selected or considered as a print job destination for the print
job, as described above with respect to FIG. 6, 7, 8, or 9. At
block 1120, a printer status message is received from the print
server. At block 1125, the printer status message is transmitted to
the print job source using a network path that is separate from the
unidirectional print queue.
[0110] Referring next to FIG. 12, a flow chart is shown
illustrating an example of a method 1200 for printing in a
distributed printing environment according to various embodiments
of the invention. This method 1200 may, for example, be performed
in whole or in part by the central server computer system 105 of
FIG. 1, 2, 5, or 9, and/or the print router 145 of FIG. 1, of FIG.
1, 2, 6, 7, 8, or 9.
[0111] At block 1205, a print job is received at a print router
over a first path including a unidirectional network print queue.
At block 1210, the print job is transmitted from the print router
to a print server associated with a printer of a plurality of
printers in communication with the print router. At block 1215, a
printer status message is received from the print server. At block
1220, the print job source is identified from at least one
attribute of the print job. At block 1225, a network address
associated with the print job source is identified. At block 1230,
the printer status message is transmitted to the network address
associated with the print job source over a second separate from
the first path.
[0112] A device structure 1300 that may be used for one or more
components of the central server computer system 105 of FIG. 1, 2,
5, or 9, the print router 140 of FIG. 1, 2, 5, 6, 7, 8, or 9, the
print job source 605 of FIG. 6, the print job destination 615 of
FIG. 6, the device 735 of FIG. 7 or 9, the backend 120 of FIG. 1,
4, 6, or 9, the print server 145 of FIG. 1, 2, 5, 7, or 9, or for
other computing devices or printers described herein, is
illustrated with the schematic diagram of FIG. 13.
[0113] This drawing broadly illustrates how individual system
elements of each of the aforementioned devices may be implemented,
whether in a separated or more integrated manner. Thus, any or all
of the various components of one of the aforementioned devices may
be combined in a single unit or separately maintained and can
further be distributed in multiple groupings or physical units or
across multiple locations. The example structure shown is made up
of hardware elements that are electrically coupled via bus 1305,
including processor(s) 1310 (which may further comprise a digital
signal processor (DSP) or special-purpose processor), storage
device(s) 1315, input device(s) 1320, and output device(s) 1325.
The storage device(s) 1315 may be a machine-readable storage media
reader connected to any machine-readable storage medium, the
combination comprehensively representing remote, local, fixed, or
removable storage devices or storage media for temporarily or more
permanently containing computer-readable information. The
communications system(s) interface 1345 may interface to a wired,
wireless, or other type of interfacing connection that permits data
to be exchanged with other devices. The communications system(s)
interface 1345 may permit data to be exchanged with a network.
[0114] The structure 1300 may also include additional software
elements, shown as being currently located within working memory
1330, including an operating system 1335 and other code 1340, such
as programs or applications designed to implement methods of the
invention. It will be apparent to those skilled in the art that
substantial variations may be used in accordance with specific
requirements. For example, customized hardware might also be used,
or particular elements might be implemented in hardware, software
(including portable software, such as applets), or both.
[0115] It should be noted that the methods, systems and devices
discussed above are intended merely to be examples. It must be
stressed that various embodiments may omit, substitute, or add
various procedures or components as appropriate. For instance, it
should be appreciated that, in alternative embodiments, the methods
may be performed in an order different from that described, and
that various steps may be added, omitted or combined. Also,
features described with respect to certain embodiments may be
combined in various other embodiments. Different aspects and
elements of the embodiments may be combined in a similar manner.
Also, it should be emphasized that technology evolves and, thus,
many of the elements are exemplary in nature and should not be
interpreted to limit the scope of the invention.
[0116] Specific details are given in the description to provide a
thorough understanding of the embodiments. However, it will be
understood by one of ordinary skill in the art that the embodiments
may be practiced without these specific details. For example,
well-known circuits, processes, algorithms, structures, and
techniques have been shown without unnecessary detail in order to
avoid obscuring the embodiments.
[0117] Also, it is noted that the embodiments may be described as a
process which is depicted as a flow diagram or block diagram.
Although each may describe the operations as a sequential process,
many of the operations can be performed in parallel or
concurrently. In addition, the order of the operations may be
rearranged. A process may have additional steps not included in the
figure.
[0118] Moreover, as disclosed herein, the term "memory" or "memory
unit" may represent one or more devices for storing data, including
read-only memory (ROM), random access memory (RAM), magnetic RAM,
core memory, magnetic disk storage mediums, optical storage
mediums, flash memory devices or other computer-readable mediums
for storing information. The term "computer-readable medium"
includes, but is not limited to, portable or fixed storage devices,
optical storage devices, wireless channels, a sim card, other smart
cards, and various other mediums capable of storing, containing or
carrying instructions or data.
[0119] Furthermore, embodiments may be implemented by hardware,
software, firmware, middleware, microcode, hardware description
languages, or any combination thereof. When implemented in
software, firmware, middleware or microcode, the program code or
code segments to perform the necessary tasks may be stored in a
computer-readable medium such as a storage medium. Processors may
perform the necessary tasks.
[0120] Having described several embodiments, it will be recognized
by those of skill in the art that various modifications,
alternative constructions, and equivalents may be used without
departing from the spirit of the invention. For example, the above
elements may merely be a component of a larger system, wherein
other rules may take precedence over or otherwise modify the
application of the invention. Also, a number of steps may be
undertaken before, during, or after the above elements are
considered. Accordingly, the above description should not be taken
as limiting the scope of the invention.
* * * * *