CENTRALIZED PRINT JOB ROUTING IN A DISTRIBUTED PRINTING ENVIRONMENT

BACKGROUND

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.

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.

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.

There are also challenges related to selecting the right printer and print server in a dynamic environment. For example, with a mobile device or a roaming user, it may be a challenge to identify the appropriate printers because of the legacy architecture for printing networks. Also, because of the traditional ways printer networks communicate, feedback for print jobs and identifying available printers can present challenges, as well. Thus, there may be a need in the art for novel system architectures to address one or more of these issues.

SUMMARY

Methods, systems, and devices are described for centralized print job routing in a distributed printing environment.

In one set of embodiments, a distributed printing system includes multiple print servers, a data store, and a print router. The data store may include a first table of identifiers for printers, a second table of identifiers for print servers, and a third table of identifiers for multiple drivers. The data store may further store an association between identifiers of the first, second, and third tables. The print router may determine a printer selected for a print job, map a first identifier for a print server to the identified printer, and map a second identifier for a driver to the print server.

In another set of embodiments, a method of printing in a distributed environment includes determining a printer selected for a print job, mapping the selected printer to a print server in communication with the selected printer, and mapping a driver associated with the selected printer to the print server.

In another set of embodiments, a method of printing in a distributed environment includes storing multiple driver in a centralized data store, receiving a print job over a network, and identifying a printer selected for the print job. The selected printer is mapped to a print server in communication with the printer, and a driver in the centralized data store is mapped to the print server. The print job is then transmitted to the print server over the network.

BRIEF DESCRIPTION OF THE DRAWINGS

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.

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.

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.

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.

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.

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.

FIG. 6 is a block diagram illustrating a system for centralized print job routing in a distributed printing environment, according to various embodiments of the invention.

FIG. 7 is a block diagram illustrating a system for centralized print job routing in a distributed printing environment, according to various embodiments of the invention.

FIGS. 8A, 8B, 8C, 8D, and 8E are diagrams illustrating tables which may be stored in a centralized data store of a distributed printing environment, according to various embodiments of the invention.

FIG. 9 is a block diagram of a print router in a distributed printing environment, according to various embodiments of the invention.

FIG. 10 is a block diagram of a central server computer system in a distributed printing environment, according to various embodiments of the invention.

FIG. 11 is a flowchart diagram of an illustrative method of centralized print job routing in distributed printing environment, according to various embodiments of the invention.

FIG. 12 is a flowchart diagram of an illustrative method of centralized print job routing in distributed printing environment, according to various embodiments of the invention.

FIG. 13 is a flowchart diagram of an illustrative method of centralized print job routing in distributed printing environment, according to various embodiments of the invention.

FIG. 14 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

The present description sets forth examples of systems, methods, and devices for centralized print job routing in a distributed printing environment. In these systems, methods, and devices, identifiers for a number of printers, print servers, and drivers may be stored in first, second, and third tables of a data store, respectively. When a printer is selected for a print job, a print router maps the printer to a print server according to an association between an identifier for the selected printer and an identifier for the print server. The print router also maps the print server to a driver based on an association between the identifier for the print server and an identifier for the driver.

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.

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.

Systems, devices, methods, and software are described for centralized print job routing 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.

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.

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.

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.

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.

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 OS and print driver, and load an OS 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 OS may be taken down. In alternative embodiments, print servers may not be dynamically generated in response to individual print jobs or even at all. For example, the central server computer system 105 may distribute incoming print jobs among a fixed set of physical or virtual print servers 145.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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. 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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.

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.

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.

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).

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.

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.

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.

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.

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.

In one set of embodiments, systems, devices, methods, and software are described for print routing. FIG. 6 illustrates an example of a system 600 for print routing according to various embodiments of the invention. The system 600 includes a device 605, a print router 140-b, print servers 145, and printers 150. 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 and/or the system 300 described above with reference to FIG. 3, and the print router 140-b may be a part of the central server computer system 105 of FIG. 1 or 3.

A user of device 605 may select a printer 150 from a table or drop down menu (or the printer may be selected automatically). The device 605 may transmit print data 405-a for a print job. The print data 405-a may include the image data for the print job and metadata. For example, the metadata associated with the print job may include, but is not limited to, at least one of a type associated with the device 605, a network identifier (e.g., a port, network address, or name) associated with the device 605, the printer selection, a network identifier associated with a selected printer 150, a location associated with the device 605, a location associated with a selected printer 150, or any other data that may suit a particular implementation of the principles described herein.

In other embodiments, the print data 405-a may come from sources other than the device 605. For example, a user of the device 605 may control the printing of data stored elsewhere, thereby controlling the generation of print data 405-a. The print data 405-a may otherwise be linked to a selected printer of a number of printers 150 in the system 600. In one example, the print data 405-a may be directed to a particular port number, and the port number may be associated with a selected printer 150. In examples, the print data 405-a may be transmitted from or to a particular port number associated with a selected printer 150. In other embodiments, the print data 405-a may be associated with other types of addressing or identifiers to indicate a selected or default printer 150 (e.g., a network address for the printer, or a location identifier to be used by a rules engine for printer selection).

The print data 405-a may be transmitted through a backend (e.g., the backend 120 of FIG. 1) or through a cloud computing environment to the print router 140-b. Alternatively, the print data 405-a may be transmitted directly (or through a network) to the print router 140-b (e.g., in a windows environment). In one embodiment, the print router 140-b may receive the print data 405-a including a port number or other network identifier, and may identify the printer 150 to be used based on the port number or other network identifier. In other embodiments, the print router 140-b may process other received information included or associated with the print data 405-a to identify the printer 150. Thus, the print router 140-b may receive information identifying a printer 150, or may process a portion of the print data 405-a to identify the printer 150.

With the information identifying the selected printer 150, the print router 140-b may identify a particular print server 145 and driver(s) associated with the selected printer 150 (e.g., if printer 150-b is selected, the print router 140-b may identify print server 145-b, and drivers to be used for the print server 145-b and device 605). The drivers may be retrieved and distributed to the print server 145 (e.g., by the print router 140-b or another server, such as the central server computer system 105 of FIG. 1 or 3), and the drivers may be installed.

The print router 140-b may transmit or otherwise provide the print data 405-a to an identified print server 145. A print server 145 may process and format the print data, and transmit the processed data to a printer 150 for printing.

In certain examples, the print server 145 may be a virtual print server, and thus both the print router 140-b and print server 145 may be part of the central server computer system 105 of FIG. 1, 2, or 5.

FIG. 7 illustrates another example of a system 700 for print routing according to various embodiments of the invention. The system 700 includes a device 605-a, a print router 140-c, a data store 110-b, and print servers 145-e and 145-f. Each of these components may be in communication with each other, directly or indirectly. Data store 110-b includes printer table 705, print server table 710, and driver table 715. The data store 110-b may be an example of the data store 100, 110-a described with reference to FIG. 1 or 3. As such, the data store 110-b may be a component of the print router 140-c and/or a central server computer system 105. This system 700 may be the system 100 described with reference to FIG. 1, and the print router 140-b may be a part of the central server computer system 105 of FIG. 1 or 5. This system 700 may also be an example of the system 600 described with reference to FIG. 6.

Device 605-a may transmit print data 405-b for a print job to print router 140-c. The print data 405-b in this example includes metadata. The metadata may include, but is not limited to, at least one of: a device 605-a type or identification, printer identifiers or links, network addresses, device and printer location, other types of network identifiers, or other data. The print data 405-b may include identification of (or include links to) a selected printer. In one example, the print data 405-b may be directed to or transmitted from a particular port number, and the port number may be associated with a selected printer. In other embodiments, the print data 405-b may be associated with other types of addressing or network identifiers to indicate a selected or default printer.

In this example, the data store 110-b includes a printer table 705, print server table 710, a driver table 715, and a mapping association 720 that includes mappings between individual entries in the printer table 705, the print server table 710, and the driver table 715. The printer table 705 may include identifiers for multiple printers (e.g., printer 150 of FIG. 1, 5, or 6) in the system 700. Similarly, the print server table 710 may include identifiers for multiple print servers (e.g., print servers 145 of FIG. 1, 5, or 6), and the driver table 715 may include identifiers for multiple drivers (e.g., drivers 305 of FIG. 3 or 5) used by the system.

The mapping association 720 may store associations between identifiers of the printer table 705, the print server table 710, and the driver table 715. In certain examples, for each printer in printer table 705, there may be an association with one (or more) print servers 145 listed in print server table 710. For each printer 150, there may be a hierarchy or varied favorability for different print servers 145. Also, for each printer 150 in printer table 705, there may be an association with one (or more) print drivers (e.g., drivers 305 of FIG. 3) from driver table 715. The driver table 715 may have drivers 305 for the device 605-a and for print servers 145. For each printer, there may be a hierarchy or varied favorability for different print drivers. Thus, the print router 140-c may receive an identification of a printer 150, and associate a print server 145 and drivers with the identified printer 145 based on links between tables 605, 610, and 615. The print router 140-b or other components of system 700 may distribute the drivers and forward the print data 405-b accordingly.

FIGS. 8A, 8B, 8C, 8D, and 8E show examples of tables that may be stored by a data store 110-b to track the association between identifiers in a printer table 705, a print server table 710, and a driver table 715. The tables of FIGS. 8A and 8B may be stored, for example in the data store 110-b of FIG. 7.

In the table shown in FIG. 8A, there are columns for printers, print servers, and drivers, respectively. For each printer identifier in the table, there is an associated print server identifier and a driver identifier. For example, as shown in FIG. 8A, printer C is associated with print server 2 and with driver C₁. Thus, where printer C is identified for a print job, the print job may be mapped to print server 2 based on the association in the table between the identifier “C” in the printer column with the identifier “2” in the print server column. Similarly, the driver C₁may be mapped to print server 2 based on the association in the table between the identifier “C₁” in the driver column and the identifier “2” in the print server column. In this way, the print job may be sent to print server 2, which may cause printer C to print the job using driver C₁.

As shown in the table of FIG. 8B, additional identifiers, such as a location identifier and a print job type identifier, may also factor into the association of a printer 150 with a print server 145 and a driver 305.

As printers 150 with redundant capabilities may be situated at different locations, separate print jobs of the same type may be sent to different printers 150 based on a location from which each print job originates or a desired printing location for each print job. Thus, in the present example, print jobs of type 1 may be associated with printer A for location I, with printer D for location II, and with printer E for locations III and IV.

Additionally, different types of jobs within the same or different regions may be associated with different printers 150. To illustrate this point, consider the example of a medical facility where printer A is a general purpose black and white printer, printer B is a color ink jet printer, and printer C is a special-purpose printer of patient identification bracelets. In location I, black and white print jobs (e.g., type 1) may be associated with printer A, color print jobs (e.g., type 2) may be associated with printer B, and patient bracelet print jobs (e.g., type 3) may be associated with printer C.

Furthermore, different types of print jobs may be sent to the same printer 150 using different drivers. Thus, as shown in FIG. 8B, a print job of type 1 sent to printer D by print server 2 may use driver D₁, whereas a print job of type 2 sent to printer D by the same print server may use driver D₂. By way of illustration, consider the example of a medical facility in which a multi-purpose printer may be configured to print both patient identification bracelets and identification cards. With this type of printer, it may be desirable to have two lightweight job-specific drivers in a system with centralized driver distribution rather than a single large driver. As such, an identification card-specific driver (e.g., driver D₁) may be mapped to the print server (e.g., print server 2) for an identification card print job (e.g., a print job of type 1), and a bracelet-specific driver (e.g., driver D₂) may be mapped to the print server (e.g., print server 2) for a bracelet print job (e.g., a print job of type 2).

In certain examples, static data from separate tables may be logically combined into inferred tables for print routing. To illustrate this point, consider the tables shown in 8C, 8D, and 8E.

The table of FIG. 8C tracks a known association between a terminal ID and port number for received data with a session and a location of a device implementing the session. Thus, if print data for a print job is received at port 9100 from terminal ID L184001, it can be determined in this example that the print data is from session M at location 2 based on the table. Similarly, if print data for a print job is received at port 9101 from a session, it can be determined in this example that the print data is from session N at location 3 based on the table.

The table of FIG. 8D tracks a default printer for different sessions at different locations. Thus, in the present example, if print data is received from session M at location 2, the default printer for that print data is printer A according to the table. Similarly, if print data is received from session N at location 3, the default printer for that print data is printer B according to the table.

The table of FIG. 8E combines the data from the tables of FIG. 8C and FIG. 8D to create inferred associations between ports and printers. If each session of the present example transmits print data at a different port, it can be inferred from the tables of FIG. 8C and FIG. 8D that print data received at port 9100 should be directed to printer A and that print data received at port 9101 should be directed to printer B, absent any indication to the contrary received in connection with the print data.

FIG. 9 illustrates one example of a print router 140-d consistent with the foregoing principles. The print router 140-d may include a printer selection identification module 905, a print server mapping module 910, and a driver mapping module 915. Each of these components may be in communication, directly or indirectly. The print router 140-d may be an example of the print router 140 described with reference to FIG. 1, 2, 6, or 7.

The printer selection identification module 905 may include logic for identifying a printer (e.g., printer 150 of FIG. 1, 5, or 6) selected for a particular print job. In certain examples, the printer 150 may be selected in connection with the generation of print data for the print job. For instance, a user of a device (e.g., device 605 of FIG. 6 or 7) may be prompted to select a printer 150 when generating a print job at the device. The user selection may be transmitted to the print router 140-d and identified at the printer selection identification module 905.

Additionally or alternatively, the printer selection identification module 905 may identify the selection of a printer 150 by receiving metadata associated with the print data, where the metadata specifies the printer 150 selected for the print job. In this example, the printer selection identification module 905 may simply read the metadata to identify the printer selection.

In other examples, the printer selection identification module 905 may identify the printer selection by inference. In certain embodiments, the printer selection identification module 905 may identify the printer selected for the print job by receiving a network identifier (e.g., a network address or a port number) associated with the print job and determining that the network identifier is associated with the printer.

In additional or alternative examples, the printer selection identification module 905 may receive a location identifier associated with the print job. The location identifier may identify a location of the device generating the print job and/or a desired printing location. The printer selection identification module 905 may then identify the selected printer based on a stored association between the location identifier and the selected printer.

In certain examples, the printer selection identification module 905 may identify the printer 150 selected for the print job using a combination of direct and inferential identification techniques. For example, metadata associated with the print job may specify a certain type of printer. The type of the printer, in combination with the identification of the port at which the print job is received, may identify the printer selection.

The print server mapping module 910 may include logic for mapping the selected printer 150, as identified by the printer selection identification module 910, to a specific print server 145. In certain examples, the print server mapping module 910 may map the selected printer 150 to the print server 145 by accessing a data store (e.g., data store 110 of FIG. 1, 3, or 7). The data store 110 may store a mapping association 720 that associates the selected printer 150 with a print server 145. For example, the print server mapping module 910 may communicate with the data store 110 to search one or more tables or other data structures in the data store 110 for an identifier of the selected printer 150. The identifier of the selected printer 150 may be associated in the data store 110 with an identifier for the print server 145. In other examples, the data store 110 may be more intelligent, and the print server mapping module 910 may simply query the data store 110 with an identifier for the printer 150 to obtain an identifier for the print server 145.

The driver mapping module 915 may include logic for mapping a driver (e.g., from drivers 305 of FIG. 3) to the print server 145. The driver 305 may be a custom driver created specifically for the selected printer 150 or for a certain printer type. As such, mapping the driver to the print server 145 may include determining that the selected printer 150 is of a certain type and determining that a driver 305 is associated with that type of printer. Additionally or alternatively, the driver 305 may be a generic driver 305 that is operable to control multiple types of printers. In still other examples, the driver 305 may be a driver 305 specific to the print server 145 or an operating system of the print server 145.

In certain examples, the driver mapping module 915 may communicate with data store 110 to determine that the driver 305 is associated with the selected printer 150. For example, the driver mapping module 915 may search or query the data store 110 to identify a driver matching the printer 150. In some examples, the driver mapping module 915 may determine that the selected printer 150 is of a certain type (e.g., vendor, model, feature set) and search or query the data store 110 for drivers 305 matching that type to identify an appropriate driver 305 to map to the print server 145. Mapping a driver 305 to the print server 145 may further include searching or querying the data store 110 to determine that an appropriate driver 305 for the print server 145 individually, for a type associated with the print server 145, and/or for an operating system of the print server 145.

Once the printer selection identification module 905 has identified the printer 150 selected for the print job, the print server mapping module 910 has mapped the printer 150 to a print server 145, and the driver mapping module 915 has mapped an appropriate driver 305 to the print server 145, the print server 145 may transmit the print job to the selected printer 150 using the driver 305.

FIG. 10 illustrates one example of central server computer system 105-c that may be used in a distributed printing system 100, such as the systems 100, 600, 700 of FIG. 1, 6, or 7. The central server computer system 105-c may be an example of the central server computer systems 105 of FIG. 1, 2, or 5.

The central server computer system 105-c may include a rules engine 130, a session manager 135, a print router 140-e, and a print server manager 205-a. Each of these components may be in communication, directly or indirectly. The rules engine 130 and the session manager 135 may function substantially as described above in FIG. 2.

The print router 140-e may be an example of the print router 140-d described with reference to FIG. 1, 2, 6, 7, or 9. The print router 140-d may include a printer selection identification module 905, a print server mapping module 910, and a driver mapping module 915 that perform substantially the same functionality as described above with reference to FIG. 9. Additionally, the print router 140-e may include a print job receiving module 1005, a metadata interpretation module 1010, a print job transmission module 1015, and a driver notification module 1020.

The print job receiving module 1005 may be configured to communicate with a device (e.g., device 605 of FIG. 6) generating print data for a print job to receive the print data. The print data may include the actual data to be printed in addition to metadata. The metadata may include data not for printing that is associated with the print job to convey certain attributes of the print job. For example, the metadata may include direct or indirect information indicating a printer selection for the print job. The metadata interpretation module 1010 may receive and parse the metadata, passing information relevant to the printer selection to the printer selection identification module 905.

The print job transmission module 1015 of the print router 140-e may forward some or all of the print data received at the print job receiving module 1005 to the print server (e.g., print server 145 of FIG. 1, 5, 6, or 7) mapped to the selected printer (e.g., printer 150 of FIG. 1, 5, 6, or 7) by the print server mapping module 910. Depending on the nature of communication between the central server computer system 105-c and the print server 145, the print data may be forwarded to the print server 145 over one or more local connections, network connections, logical connections, and/or combinations thereof.

The print server manager 205-a may be configured to coordinate the installation and use of drivers 305 by specific print servers 145. The print server manager 205-a may include a driver notification module 1025, a driver deployment analysis module 1030, and a driver deployment module 1035.

The driver notification module 1025 may include logic for notifying a print server 145 of the identity of the driver 305 mapped to the print server 145 for the print job. For example, the driver notification module 1025 may receive an identifier of the driver 305 from the driver mapping module 915 and forward the identifier to the print server 145. Upon receiving the identifier of the driver 305, the print server 145 may know to use that driver 305 for the print job.

The driver deployment analysis module may include an installation detection submodule 1040 and an update analysis submodule 1045. In certain examples, drivers 305 for print jobs may be centrally distributed to print servers 145 from the central server computer system 105-c on a per-print job basis, an as-needed basis, and/or another basis.

As such, when a driver 305 has been mapped to the print server 145 for use with a printer 150 selected for a print job, the installation detection submodule 1040 may communicate with the print server 145 to determine whether the print server 145 already has that driver 305 installed. Where the print server 145 has a version of the driver 305 installed that is different from the version stored by the central server computer system 105-c, the update analysis submodule 1045 may determine whether an update to the driver installed on the print server 145 is merited. If the print server 145 does not have the driver 305 installed or has an incorrect version of the driver 305 installed, the driver deployment module 1035 may communicate with the print server 145 to write the correct version of the driver 305 into the local storage of the print server 145.

Alternatively, the print server 145 may manage driver installation on its own. For example, the print server 145 may receive notification from the driver notification module 1025 that a certain driver 305 has been mapped to the print server 145 for use with a selected printer 150 on a print job. In response to the notification, the print server 145 may search its local storage to determine whether that driver 305 is already installed on the print server 145. If the print server 145 does not have the driver installed, or if an incorrect or out-of-date version of the driver is installed, the print server 145 may request the driver from the central server computer system 105-c or another source.

FIG. 11 illustrates one example of a method 1100 of centralized print distribution in a distributed printing environment. The method 1100 of FIG. 11 may be performed, for example, by the print router 140 of FIG. 1, 2, 5, 6, 7, 9, or 10 and/or by the central server computer system 105 of FIG. 1, 2, 5, 7, or 10. At block 1105, a printer selected for a print job is determined. In certain examples, the selected printer may be determined based on a selection made by a user of a device generating the print job, a location identifier associated with the print job, metadata received with the print job, and/or other data conveying or inferring a printer selection.

At block 1110, the selected printer is mapped to a print server in communication with the selected printer. In certain examples, mapping the selected printer to the print server may include consulting a data store to determine that an identifier stored for the selected printer in a table of printer identifiers is associated with an identifier stored for the print server in a table of print server identifiers.

At block 1115, a driver associated with the selected printer is mapped to the print server. The mapping of the selected printer to the print server may also include communicating with a centralized data store to determine that an identifier stored for the selected printer in a table of printer identifiers is associated with an identifier stored for the driver in a table of print drivers. The mapping of the selected printer to the print server may additionally or alternatively include determining that the selected printer is of a specified type and determining that the driver is associated with the specified type of the selected printer.

FIG. 12 illustrates another example of a method 1200 of centralized print job routing in a distributed printing environment. The method 1200 of FIG. 12 may be performed, for example, by the print router 140 of FIG. 1, 2, 5, 6, 7, 9, or 10 and/or by the central server computer system 105 of FIG. 1, 2, 5, 7, or 10.

At block 1205 a printer selected for a print job is determined based on a network identifier associated with the print job. The network identifier may include, for example, a source port, a destination port, a source address, and/or a destination address. At block 1210, the selected printer is mapped to a print server in communication with the selected printer. At block 1215, a driver associated with the selected printer is mapped to the print server. At block 1220, communication with the print server occurs to notify the print server of the driver mapped to the print server. In certain examples, the print server may install the driver in response to receiving the notification.

FIG. 13 illustrates another example of a method 1300 of centralized print job routing in a distributed printing environment. The method 1300 of FIG. 13 may be performed, for example, by the print router 140 of FIG. 1, 2, 5, 6, 7, 9, or 10 and/or by the central server computer system 105 of FIG. 1, 2, 5, 7, or 10.

At block 1305, multiple drivers are stored at a centralized data store. At block 1310, a print job is received over a network. At block 1315, a printer selected for the print job is determined. At block 1320, the selected printer is mapped to a print server in communication with the selected printer. At block 1325, a driver from the centralized data store is mapped to the print server. At block 1330, the print job is transmitted over the network to the print server.

The functionality of the central server computer system 105 of 1, 2, 5, 7, or 10, the print router 140 of FIG. 1, 2, 5, 6, 7, 9, or 10, the backend 120 of FIG. 1 or 4, the print server 145 of FIG. 1, 5, 6, or 7, or the device 605 of FIG. 6 or 7, may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In other embodiments, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Arrays (FPGAs), and other Semi-Custom ICs), which may be programmed in any manner known in the art. The functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.

A device structure 1400 that may be used for one or more components of the central server computer system 105 of 1, 2, 5, 7, or 10, the print router 140 of FIG. 1, 2, 5, 6, 7, 9, or 10, the backend 120 of FIG. 1 or 4, the print server 145 of FIG. 1, 5, 6, or 7, or the device 605 of FIG. 6 or 7, or for other computing devices or printers described herein, is illustrated with the schematic diagram of FIG. 14.

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 1405, including processor(s) 1410 (which may further comprise a digital signal processor (DSP) or special-purpose processor), storage device(s) 1415, input device(s) 1420, and output device(s) 1425. The storage device(s) 1415 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 1445 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 1445 may permit data to be exchanged with a network.

The structure 1400 may also include additional software elements, shown as being currently located within working memory 1430, including an operating system 1435 and other code 1440, 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.

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.

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.

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.

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.

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.

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.

CENTRALIZED PRINT JOB ROUTING IN A DISTRIBUTED PRINTING ENVIRONMENT

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims

CROSS REFERENCES

Provisional Applications (1)