1. Field of the Invention
The present invention relates to a method of sharing a printer, and, more particularly, to a method of sharing a printer on a computer network.
2. Description of the Related Art.
It is known for a printer to be controlled by a host computer on a computer network. The essential purpose of all networks is to provide a common media for the orderly exchange of data between cooperating nodes. This host-based paradigm separates the image processing (fonts, images, etc.) from the physical printing mechanism such that the intensive raster image processing is performed on the host computer, leaving the printer's processor free to perform the task of physically placing the pixels on the media. The processing power required to physically place the pixels is significantly smaller than that required of printers that also interpret data streams. Thus, printers that do not have to interpret data streams have a lower cost.
Adding traditional protocol-based networking to a host based printer is cost prohibitive because the cost of the network electronics approaches or exceeds the cost of the complete printer electronics.
What is needed in the art is a low cost method of extending the host-based printing paradigm to host-based networking.
The present invention provides a transport protocol that can be easily implemented in hardware and that can co-exist with standard network protocols.
The present invention comprises, in one form thereof, a method of sharing a printer between a plurality of users on a computer network. Host-based networking hardware is attached to the printer. A network communication protocol defines a command channel and a data channel. Only one of the users is allowed to own the data channel at any single point in time. The host-based networking hardware will only accept information on the data channel only from the user that owns the data channel, in turn passing this data to the printer.
The present invention enables the use of conventional networking infrastructure to physically connect host-based printers to workstations. A data channel is reserved for exclusive use by the host-based driver. A command channel responds to certain signals but replies with an all-inclusive set of field values indicating the present state of the device. A “set of rules” allows at least one workstation with a host-based network print driver to deliver print data to a host-based network printer using the shared network medium.
Standard networking protocols require a substantial amount of overhead (and cost) to maintain many concurrent connections between many clients and many servers. The present invention, in contrast, disallows any concurrent data connections, i.e., allows only one data connection to exist at a time, shifts the burden of sharing to the host, and only allows the host-based networking application to connect to the host-based networking printer. Thus, the present invention provides a low cost, high speed data transport mechanism that fits the host-based printing paradigm.
An advantage of the present invention is that the need for a protocol-processing engine, such as a central processing unit (CPU), is eliminated, thereby significantly reducing the cost of the printer.
Another advantage is that the functionality of the printing system is not reduced, since the “protocol-processing” function can be implemented in host software.
The above-mentioned and other features and advantages of this invention, and the manner of attaining them, will become more apparent and the invention will be better understood by reference to the following description of an embodiment of the invention taken in conjunction with the accompanying drawings, wherein:
Corresponding reference characters indicate corresponding parts throughout the several views. The exemplification set out herein illustrates one preferred embodiment of the invention, in one form, and such exemplification is not to be construed as limiting the scope of the invention in any manner.
Referring now to the drawings, and particularly to
To facilitate printing, the print driver, i.e., the application, must be able to create host-based networking printer specific data and deliver it in order and unaltered to the host-based networking printer. Workstation host-based networking print drivers are designed to cooperate in order to facilitate the “fair-sharing” of the host-based networking printer amongst a number of workstations. To exist concurrently with other networking appliances, a common standard for transporting data on the medium must be adhered to by all devices. For example, DIX or IEEE 802.3 defines the standard for Ethernet. In adhering to the standard, each device must have a universally unique address (IEEE assigns these for Ethernet and token ring). Further adherence dictates that the host-based networking appliances will use these addresses to exchange basic units of data (frames). Within the frame, these addresses are used by the networking hardware to deliver the frame much like the address and return address fields on a piece of postage are used to deliver the piece of postage.
A communication frame (
The conceptual frame shown in
The data channel is used to send print objects from the workstation host-based printing driver to the printer using the “payload” field in the frame. To minimize complexity and thus minimize cost, only one workstation is allowed to “own” the data channel at any given point in time. Any traffic received on the data channel that does not originate from the “owner” is immediately discarded by the hardware.
The command channel is used to signal the host-based networking hardware. Any host-based networking appliance can send a signal to the host-based networking hardware. Various signals can be defined. In this embodiment, the signals “connect”, “close”, “terminate” and “status” are defined. “Connect” is a request to acquire the data channel with a desire to send data. “Close” is a request to release the data channel. “Terminate” is a request to release the data channel and abort the print job. Only a host-based network appliance that is the owner of the data channel can send a “close” command. “Status” is a request for printer status with no desire to send data.
The host-based networking hardware 14 will respond to any signal received on the command channel by transmitting a frame whose payload a fixed structure dynamically populated using the hardware's status and operational registers to the originator of the signal. This fixed structure is the STATUS response. When designing the target system the STATUS response must include the owner of the data channel. Other informational items may also be of use such as: ink levels, paper tray levels, head alignment settings, etc.
The interaction of the commands and the STATUS response are specified by data channel logic, command channel logic, and host rules.
According to the data channel logic, the printer waits for a data channel connection. The printer then waits for a frame. If the sender of the frame is not the data channel owner, then the frame is discarded. If the sender of the frame is the data channel owner, then the frame is processed by host-based networking hardware 14.
If the sequence number is correct, the data content of the frame is sent to the print engine, and an acknowledgement signal is sent to the host. If the sequence number is incorrect, the frame is discarded, and an acknowledgement signal is sent to the host indicating the frame number of the last successfully received frame.
If a terminate signal is received on the command channel, the data channel is released and the printer again waits for a data channel connection. If a timeout occurs while the printer waits for a frame, i.e., a communication frame has not been received within a predetermined time period, then an acknowledgement signal is sent to the host indicating the last successfully received frame. If three timeouts occur in succession, the print engine is signaled to abort the print job, the data channel is released, and the print again waits for a data channel connection.
According to the command channel logic, the host-based networking hardware waits for a command signal to do something. If the command is a connect signal, then the printer checks for data channel ownership. If the data channel is not in use, then the sender of the connect signal is recorded as the owner of the data channel and the STATUS response containing the new owner is transmitted to the sender. If, on the other hand, the data channel already has an owner, then the STATUS response containing the current owner is sent to the sender of the connect signal.
If the command is the status signal, then the printer sends the STATUS response to the sender of the status signal. If the command is the close signal, and the source of the close signal is the data channel owner, then the data channel is freed, and the STATUS response is sent to the sender of the close signal. If the command is the terminate signal, then the print engine is signaled to abort the job, the data channel is freed, and the STATUS response is sent to the sender.
According to the host rules, on the command channel, a status signal can be sent at any time to fetch the STATUS response. A connect signal can be sent at any time to indicate desire to use the data channel. A STATUS response indicates who is the current owner of the data channel. If the owner of the data channel is the same as the sender of the connect signal, then the data channel has been successfully acquired.
A close signal will only be recognized by host-based networking hardware 14 if the sender is the data channel owner. The close signal provides for the orderly release of the data channel by the owner. The STATUS response indicates whether the data channel has been successfully released.
The terminate signal will only be recognized by host-based networking hardware 14 if the sender is the data channel owner. The terminate signal is similar to a close command, but additionally provides an indication to the printer to abort printing as soon as possible. The STATUS response indicates that the data channel has been successfully released.
On the data channel, only frames from the data channel owner are processed by the host-based networking hardware. All other frames are discarded with no response. All frames from the data channel owner are acknowledged to the sender of the frame. The acknowledgement includes the frame number.
The host-based networking hardware can selectively process certain frames of data that have been transmitted in a layered protocol without the host-based networking hardware having either UDP (User Dataframe Protocol)/IP or Ethernet processing engines. UDP/IP, an example of such a layered protocol, is encapsulated in internetwork protocol that is encapsulated in an Ethernet frame. More particularly, a workstation can transmit a data frame into the network such that an initial portion of the data frame includes a unique, identifying data sequence that indicates the data in the next portion of the data frame is in a format that can be recognized as print data and passed on to printer 12 by host-based networking hardware 14. The media access hardware or other hardware within host-based networking hardware 14 can receive the initial portion of the data frame and determine whether it includes the unique, identifying data sequence. If so, host-based networking hardware 14 reads, processes and sends the next portion of the data frame to printer 12. If not, host-based networking hardware 14 ignores the next portion of the data frame and discards the data frame without performing any further processing.
Host-based networking hardware 14 can read the first portion of the data frame and determine in real time whether it includes the predetermined data sequence without having to store any of the data frame in any type of memory. Since host-based networking hardware 14 only processes Ethernet data frames identified as having a specific, unique format that is ready for printing, host-based networking hardware 14 does not need a protocol-processing engine to further process the data frame, as does a conventional network appliance that can interpret various types of Ethernet protocols.
If a frame from the data channel owner does not have the expected sequence number, the frame is discarded. The acknowledgment includes the frame number of the last successfully received frame.
While the present invention may use Ethernet as the shared media, it is to be understood that other forms of shared network media may be used as well.
While this invention has been described as having a preferred design, the present invention can be further modified within the spirit and scope of this disclosure. This application is therefore intended to cover any variations, uses, or adaptations of the invention using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains and which fall within the limits of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
5323393 | Barrett et al. | Jun 1994 | A |
5438528 | Emerson et al. | Aug 1995 | A |
5530862 | Wadsworth et al. | Jun 1996 | A |
5537550 | Russell et al. | Jul 1996 | A |
5537626 | Kraslavsky et al. | Jul 1996 | A |
5548728 | Danknick | Aug 1996 | A |
5550957 | Davidson, Jr. et al. | Aug 1996 | A |
5550997 | Ip et al. | Aug 1996 | A |
5568612 | Barrett et al. | Oct 1996 | A |
5606671 | Wadsworth et al. | Feb 1997 | A |
5611046 | Russell et al. | Mar 1997 | A |
5613160 | Kraslavsky et al. | Mar 1997 | A |
5623604 | Russell et al. | Apr 1997 | A |
5633992 | Gyllenskog | May 1997 | A |
5636333 | Davidson, Jr. et al. | Jun 1997 | A |
5647056 | Barrett et al. | Jul 1997 | A |
5651114 | Davidson, Jr. | Jul 1997 | A |
5657448 | Wadsworth et al. | Aug 1997 | A |
5696899 | Kalwitz | Dec 1997 | A |
5699493 | Davidson, Jr. et al. | Dec 1997 | A |
5701411 | Tran et al. | Dec 1997 | A |
5710908 | Man | Jan 1998 | A |
5720015 | Martin et al. | Feb 1998 | A |
5724555 | Wadsworth | Mar 1998 | A |
5727135 | Webb et al. | Mar 1998 | A |
5727220 | Hohensee et al. | Mar 1998 | A |
5732198 | Deppa et al. | Mar 1998 | A |
5768483 | Maniwa et al. | Jun 1998 | A |
5784622 | Kalwitz et al. | Jul 1998 | A |
5815722 | Kalwitz et al. | Sep 1998 | A |
5819015 | Martin et al. | Oct 1998 | A |
5841991 | Russell | Nov 1998 | A |
5862404 | Onaga | Jan 1999 | A |
5873659 | Edwards et al. | Feb 1999 | A |
5905906 | Goffinet et al. | May 1999 | A |
5960167 | Roberts et al. | Sep 1999 | A |
5982994 | Mori et al. | Nov 1999 | A |
6003078 | Kodimer et al. | Dec 1999 | A |
6023727 | Barrett et al. | Feb 2000 | A |
6025925 | Davidson, Jr. et al. | Feb 2000 | A |
6029198 | Iizuka | Feb 2000 | A |
6047319 | Olson | Apr 2000 | A |
6091507 | Vatland et al. | Jul 2000 | A |
6202096 | Williams et al. | Mar 2001 | B1 |
6321258 | Stollfus et al. | Nov 2001 | B1 |
6348973 | Vatland et al. | Feb 2002 | B1 |
6370592 | Kumpf | Apr 2002 | B1 |
6384926 | Mochizuki | May 2002 | B2 |
6490052 | Yanagidaira | Dec 2002 | B1 |
6785727 | Yamazaki | Aug 2004 | B1 |
Number | Date | Country | |
---|---|---|---|
20020142720 A1 | Oct 2002 | US |