JP2000267831A - Network printer system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent traffic congestion from occurring in a local node in the vicinity of a server with small line capacity by making a client transmitting a request token distribute a command string directly to a printer. SOLUTION: When a client 1[3] distributes print data to a network printer 3[1], it transmits the first request token designating the printer 3[1] to a server 2. The server 2 returns a start token 12 to the client 1[3] when the printer 3[1] becomes in a printing standby state. The client 1[3] distributes a printing command string 14 directly to a selected prescribed network printer 3[1] without the intervention of the server 2. As a result, a server 2 that is subject to congestion receives and returns only a request token 11 and a start token 12 with a small data amount. A printing command string 14 with a large data amount is distributed directly to the printer 3[1].

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a network printer system.

[0002]

2. Description of the Related Art Conventionally, a plurality of client computers connected to a network (hereinafter referred to as clients).
Share a printer that can be directly connected to a network or a printer that is connected to a network via a print server (hereinafter, these two types of printers are referred to as network printers). A method in which a print server receives print data from a plurality of clients, temporarily stores the print data in a server disk provided therein, and then distributes the print data to a predetermined network printer in a predetermined order. 2. 1 beforehand between the client and the network printer
One-to-one logical connection is set, and one client occupies a network printer according to this setting and performs printing. During this time, another client with the same settings waits until the printing is completed. The above two control methods are mainly employed.

[0003] Further, the network configuration is such that a large capacity line using an optical fiber or the like is used as a backbone,
A relatively small-capacity local node using 10BaseT or the like is arranged via a router, and the client and the network are connected to the local node.

[0004]

However, the above-mentioned conventional techniques have the following problems to be solved. Data is concentrated on a specific print server or network printer, and traffic congestion tends to occur in peripheral local nodes.

[0005]

The present invention adopts the following constitution in order to solve the above points. <Structure 1> In a network printer system in which a client that requests a print job, a printer that executes the print job, and a server that controls the client and the printer are arranged, the client specifies print data request contents. A request token to be executed, and a print command string for specifying print content, and a network driver for designating a printer to execute a print job and transmitting the request token to the server. Prior to the delivery of the print command sequence, the request token is transmitted to the server, and the server monitors the token queue for storing the request tokens in the order in which the request tokens are received from the client, and monitors whether the printer is in a print standby state. A printer that detects the print standby status of the above printer When the print server manager detects that the printer is in a print standby state, the print server manager takes out the request token from the token queue and sends the print command sequence directly to the client that transmitted the request token. A network printer system for distributing to the printer.

<Structure 2> In the network printer system described in Structure 1, the print server manager takes out the request token, reads out the request contents, and recognizes that the printer specified by the client cannot operate. A network printer system for directly transmitting the print command sequence to another printer in place of the printer designated by the client.

<Structure 3> In the network printer system described in Structure 1, the server includes a virtual network printer that receives and temporarily stores the print command sequence and a server disk, and the print server manager transmits the request token to the server. When the data amount of the print command string is smaller than a predetermined value, the print command string is directly delivered to the virtual network printer in place of the printer specified by the client, and A network printer system, wherein the command sequence is temporarily stored in a server disk, and the command sequence temporarily stored in the server disk is read out at a predetermined time and forwarded to a predetermined printer.

<Configuration 4> In the network printer system according to Configuration 1, the server includes a simple network management system for individually managing a plurality of local nodes constituting the network system, and the print server manager includes: Using the simple network management system, the operating load of the local node including the printer is monitored, and when the operating load exceeds a predetermined reference load, the operating load of the local node is compared with the operating load of the local node. A network printer system, comprising detecting an operating load of another small local node and directly delivering the print command sequence to the other local node.

<Structure 5> In the network printer system according to Structure 1, when the server receives the request token from a plurality of clients, the server determines the order of the clients for distributing the print command sequence to the printer. Wherein the print server manager causes the plurality of clients to directly deliver the print command sequence to the printer in the order defined in the client priority table. .

<Structure 6> In the network printer system according to Structure 1, the server includes a network printer paper size table for registering paper sizes set in the printer, and the print server manager includes the client server. A network printer system which, when receiving the request token from the client, refers to the network printer paper size table and directly distributes the command sequence to a printer in which paper of a size designated by the client is set.

[0011]

Embodiments of the present invention will be described below in detail with reference to the drawings. <Structure of Embodiment 1> FIG. 1 is a block diagram of a network printer system according to Embodiment 1. 1, the network printer system according to the first embodiment includes a client 1, a server 2, a network printer 3, a backbone 4, a local node 5, and a router 20.

The client 1 is a server 2 described later.
This is the part for requesting printing work. The operator inputs desired print data, and transmits to the server 2 a request token 11 indicating the intention of a print request and designating request contents. When a start token 12 permitted to distribute print data is received from the server 2, the print data is distributed to a predetermined network printer 3 described later.

Usually, a small computer such as a workstation or a personal computer is employed, and has functions such as an application 6, a printer driver 7, and a network driver 8. These functions are executed in accordance with a software program provided in the client 1 in advance.

The application 6 is a general term for tasks that the operator instructs the client 1 to process. That is, in the present invention, a print job is processed, and print data is input by an operator. The printer driver 7 is a part that translates print data input by the application 6 into data printable by the network printer 3 described later, that is, a data stream.

The network driver 8 transmits the request token 11 from the client 1 to the server 2 described later, and distributes a print command sequence 14 for designating print contents to the network printer 3 described later to the network printer 3. Control software. The print command sequence 14 is a portion obtained by removing the request token from the data stream.

The server 2 controls a network printer 3 that executes a printing job, which will be described later, based on a request from the client 1. Multiple clients 1
When a print job is requested to a specific network printer 3 by the user, this is also a part for determining the execution order.

That is, it is a part for executing a network operation system (hereinafter referred to as NOS) for managing a network. Usually, a small computer such as a workstation or a personal computer is employed, and has the functions of a token queue 9 and a print server manager 10. These functions are executed according to a software program provided in advance in the server 2.

The token queue 9 is a queue for receiving and storing the request token 11 from the client 1. The print server manager 10 has a function of returning a start token that permits distribution of the print command sequence 14 when a plurality of request tokens are accepted, among the functions of the server.

Also, a monitoring token (not shown) is sent to the network printer 3 to monitor the operation state and confirm whether the network printer 3 is printing or has finished printing and is on standby. Part. This operation is periodically performed as a part of NOS.

The network printer 3 is a part that receives a print command sequence 14 from the client 1 and executes a print job under the control of the server 2. The backbone 4 is a large-capacity line using an optical fiber or the like, and a 10-bass line is provided around the backbone 4 via a router 20 described later.
This is a portion to which a relatively small capacity local node 5 using eT or the like is connected.

The local node 5 is a relatively small-capacity line using 10BaseT or the like, and is a part to which the client 1, the server 2, the network printer 3 and the like are connected. The router 20 is a relay device that connects the local node 5 to which the terminal devices such as the client 1, the server 2, and the network printer 3 are connected to the backbone 4. Next, how these components are arranged in the network system will be described with reference to the drawings.

FIG. 2 is a configuration diagram of a network system according to the first embodiment. As shown in FIG. 2, in the network system according to the first embodiment, a plurality of local nodes 5 are connected to a backbone 4 via a router 20. In FIG. 2, the local node 5 includes four local nodes 5 [1] to 5 [4] and the router 20 as an example.
Are limited to four routers 20 [1] to router [4].

Further, to each local node 5, a client 1, a server 2, and a network printer 3 are connected. In FIG. 2, as an example, the local node 5
[1] has Client 1 [1] and Client 1 [2]
Client 1 [3] and client 1 [4] are on local node 5 [2], client 1 [5] and network printer 3 [1] are on local node 5 [3], and server 2 is on local node 5 [4]. And network printer 3 [2]
Are described in a limited manner. Specific example 1
After the description of the configuration of the network system according to the above, the operation will be described next.

<Operation of Embodiment 1> First, the outline of the operation of Embodiment 1 will be described with reference to FIG. In the present invention, when distributing print data to the network printer 3 [1], the client 1 [3] first transmits the request token 11 specifying the network printer 3 [1] to the server 2. The server 2 accepts the request token 11.
After confirming that the network printer 3 [1] is in the print standby state, the server 2 returns the start token 12 to the client 1 [3]. When the client 1 [3] receives the start token 12, it distributes the print command sequence 14 directly to the selected predetermined network printer 3 [1] without passing through the server 2.

As a result, in the server 2 which is easily congested, only the request token 11 and the start token 12 having a small data amount are received and returned. The print command sequence 14 having a large data amount is directly delivered to the network printer 3 [1]. Further, when the server 2 receives a plurality of request tokens 11 from a plurality of clients 1, the start token 1
When replying No. 2, it is also possible to determine the reply order according to a predetermined priority. This priority order will be described later as a specific example 5. The details of the control operation will be described below with reference to FIG.

In FIG. 1, an operator inputs print data with the application 6 of the client 1 and starts a print job. This print data is transferred to the printer driver 7. The print data is translated by the printer driver 7 into a printable data stream 15. This data stream 15 is sent to the network driver 8 where it is converted into a request token 11 and a print command sequence 14. The operation of the network driver 8 will be described in detail with reference to other drawings.

FIG. 3 is a diagram for explaining the operation of the network driver. In FIG. 3, a spooler 30 is a hard disk provided in the client 1, and is a memory for temporarily storing the print command sequence 14. As shown in FIG. 3, the network driver 8 receives the data stream 15 from the printer driver 7. The data stream 15 includes the print command sequence 14 and the request token 11
Are converted into information that is converted into The print command sequence 14 is temporarily stored in the spooler 30. at the same time,
From the information for generating the request token 11, the request token 1
1 is generated.

The configuration of the request token 11 will be described with reference to the drawings. FIG. 4 is a configuration diagram of the request token and the start token. FIG. 4A shows a request token. FIG. 4B shows a start token. FIG.
From (a), the request token is framed as follows.

At the beginning of the frame, a command RQ indicating that this token is a request token is written, and thereafter, an SCRnam indicating the client name of the request source in order.
e, DSTna indicating the network printer name of the printing destination
me, job # indicating the printing operation, Nbyte indicating the data size, and terminator T indicating the end of the token
M is written respectively. Things to keep in mind here are
It is as follows. That is, the data amount of the request token 11 is extremely small compared to the data amount of the print command sequence 14.

Returning to FIG. 1, description of the details of the control operation will be continued. The request token 11 is transmitted from the network driver 8 to the server 2. The server 2 accepts the request token 11. Although only one client 1 is shown in FIG. 1 for convenience of explanation,
In an actual system, a plurality of clients 1 are connected (for example, FIG. 2).

Therefore, the request token 11 accepted by the server 2 can be plural. This multiple request token 1
1 are temporarily stored in the token queue 9 in the order of acceptance. The print server manager 10 takes out the request tokens 11 from the token queue 9 in the order of acceptance each time it detects that the network printer is in the print standby state by the monitoring token. A start token 12 is generated based on the contents described, and is returned to the network driver 8 of the client 1.

The start token 12 will be described with reference to FIG. From FIG. 4B, the start token is framed as follows. At the beginning of the frame, a command ST indicating that this token is a start token is written, and thereafter, an SCRname indicating the client name of the requester, a predetermined network printer name DST
name, job # indicating that the job is a printing job, and an end element TM indicating the end of the token are written.

The network driver 8 which has received the start token 12 sends a predetermined print command sequence 14 once stored in the spooler 30 from the spooler 30 (FIG. 3).
Read out. This print command sequence 14 is directly delivered to the network printer 3 without going through the server 2.

<Effects of Specific Example 1> The following effects are obtained by providing the above-described configuration. 1. In a server where data tends to be concentrated, only a request token and a start token having a small data amount are processed, and a print command sequence having a large data amount is directly delivered from a client to a network printer without passing through the server. 2. Since a print command sequence having a large data amount does not pass through the server, traffic congestion is less likely to occur in local nodes around the server having a small line capacity.

<Configuration of Specific Example 2> In specific example 1, the server 2 (FIG. 1) that has received the request token 11 (FIG. 1) from the client 1 (FIG. 1) starts based on the operating status of the network printer 3. Token 12 was being created.
However, a failure may occur in the network printer 3. In this case, a predetermined network printer 3 is designated in place of the failed network printer 3, and
You need to create a start token. To achieve this object, the network system according to the second embodiment is configured as follows.

FIG. 5 is a block diagram of a network system according to the second embodiment. As shown in FIG. 5, the network printer system according to the second embodiment includes a client 1, a server 32, a network printer 3 [1], a network printer 3 [2] backbone 4, and a local node 5.
And the router 20.

Hereinafter, only differences from the first embodiment will be described. The server 32 is a part that controls the network printer 3 that executes a printing job based on a request from the client 1. When a print job is requested from a plurality of clients 1, the start token 12 is generated and returned in the order of acceptance. Further, when the network printer 3 specified by the client 1 is out of order or stopped for maintenance and inspection, the network printer 3 selects another predetermined network printer 3 instead of the network printer 3.

That is, this is the part that executes the NOS for managing the network. Usually, a small computer such as a workstation or a personal computer is employed, and has the functions of the token queue 9 and the print server manager 33. These functions are executed according to a software program provided in advance in the server 32.
The token queue 9 is a queue for receiving and storing the request token 11 from the client 1.

The print server manager 33 is a part of the function of the server 32 that has a function of returning the start token 12 when the request token 11 is accepted. In addition, whether the network printer is currently printing
Or, it is a part that holds information such as an operation status such as whether printing is completed and in a standby state, a breakdown or a stop for maintenance and inspection. Information such as during the failure and during the inspection is input in advance by the network administrator via the console. Alternatively, the state of the network printer 3 can be detected by sending a monitoring token.

A portion for selecting a predetermined network printer 3 from a plurality of network printers 3 based on these information. In order to collect such information, a monitoring token (not shown) is sent to all the network printers 3 connected to the network to check the operation state of the network printers 3.
This operation is periodically performed as a part of NOS. The other parts are completely the same as the configuration of the first embodiment, and the description is omitted. Next, how these components are arranged in the network system will be described with reference to the drawings.

FIG. 6 is a configuration diagram of a network system according to the second embodiment. As shown in FIG. 6, in the network system according to the second embodiment, a plurality of local nodes 5 are connected to a backbone 4 via a router 20. In FIG. 2, the local node 5 includes four local nodes 5 [1] to 5 [4] and the router 20 as an example.
Are limited to four routers 20 [1] to 20 [4].

Further, to each local node 5, a client 1, a server 32, and a network printer 3 are connected. In FIG. 2, as an example, the local node 5
[1] has Client 1 [1] and Client 1 [2]
The local node 5 [2] has the client 1 [3] and the client 1 [4], the local node 5 [3] has the client 1 [5] and the network printer 3 [1], and the local node 5 [4] has the server 32. And network printer 3
[2] is described in a limited manner. This concludes the description of the configuration of the network system according to the first specific example, and then describes the operation.

<Operation of Specific Example 2> Referring to FIG. 5, the operation of specific example 2 will be described based on the precondition that the network printer 3 [2] is out of order. Only the differences from the operation of the specific example 1 will be described. First, the outline of the operation of the specific example 2 will be described with reference to FIG. Example 2
Then, the client 1 [3]
The request token 11 is transmitted to the server 32 by designating [2]. The server 32 accepts the request token 11.

The server 32 designates the network printer 3 [1] instead of the predetermined network printer 3 [2] because the NOS causes the client 1 to fail.
The start token 12 is returned to [3]. Client 1
[3], when accepting the start token 12, distributes the print command sequence 14 directly to the selected predetermined network printer 3 [1] without going through the server 2.

Among the above operations, the difference from the operation of the first embodiment is that when the server 32 accepts the request token 11, the server 32 determines that the network printer 3 [2] is out of order. Only the operation of designating the printer 3 [1] and returning the start token 12 is performed.
All other operations are the same as those of the first embodiment, so the designated network printer 3 [2] is changed to the network printer 3 [1].
Only the operation of changing to "" will be described with reference to a flowchart.

FIG. 7 is an explanatory diagram of the operation of the network system according to the second embodiment. A description will be given according to steps S1 to S4 in FIG. Step S1 The print server manager 33 (FIG. 5) takes out the request token 11 (FIG. 5) from the token queue 9 (FIG. 5) and proceeds to step S2.

Step S2 The print server manager 33 (FIG. 5) checks based on the NOS whether the designated network printer 3 [2] described in the section of the request token DSTname (FIG. 4) can be operated. . If the designated network printer 3 [2] cannot operate due to a failure or the like, the process proceeds to step S3. If the designated network printer 3 [2] can operate, the process jumps to step S4. Here, the process proceeds to step S3 according to the preconditions.

Step S3 The print server manager 33 (FIG. 5) selects an operable network printer 3 [1] instead of the designated network printer 3 [2], and proceeds to step S4. Step S4: The print server manager 33 (FIG. 5) starts the designated network printer 3 [1] with the start token DSTname.
(FIG. 4) is written in the section to generate the start token 12, and the processing ends.

The start token 12 generated through the above steps is returned to the client 1 [3]. Thereafter, by the same operation as in the specific example 1, the client 1 [3]
When the start token 11 is accepted, the print command sequence 14 is directly delivered to the selected predetermined network printer 3 [1] without going through the server 2. here,
Although the cause of the designated network printer change has been described only in the case of failure, inspection, or the like, the specific example is not limited to this cause. That is, when the designated network printer is congested during processing of the request token 12 with a high degree of urgency, the start token 12 in which the designated network printer has been changed to another network printer waiting for printing can be returned. It is.

<Effects of Specific Example 2> With the above-described configuration, the following effects are obtained in addition to the effects of Specific Example 1. 1. When the printer designated by the client is out of order or under inspection, the print command sequence can be forwarded to another predetermined network printer. 2. When processing a request token with a high degree of urgency, if a request destination printer is congested, it is possible to forward a print command sequence to another predetermined network printer.

<Configuration of Specific Example 3> In specific example 1, after transmitting the request token 11 (FIG. 1), the client 1 (FIG. 1) transmits the start token 12 (FIG. 1) from the server 2 (FIG. 1). Until it was accepted, it was not released from the data link state with the server 2 (FIG. 1). In some cases, such as when the request token 11 (FIG. 1) is received from many clients 1 (FIG. 1) at the same time, it takes a long time to be released from the data link state. On the other hand, the data amount of the print command sequence 14 (FIG. 1) requested by the client 1 (FIG. 1) also varies.

In this case, in the specific example 3, a predetermined value (hereinafter referred to as a specified value TH) is set in advance to the data amount of the print command sequence 14 (FIG. 1). This specified value TH
The following print command sequence 14 (FIG. 1) is accepted by the server 2 (FIG. 1). The received print command sequence 14 is temporarily stored in a server disk (not shown in FIG. 1) owned by the user. As a result, server 2
The data link state between (FIG. 1) and client 1 (FIG. 1) is released. Then, at a predetermined time, the server 2 (FIG. 1)
Forwards the print command sequence 14 (FIG. 1) to the network printer 3 (FIG. 1). In order to perform such an operation, the present specific example is configured as follows.

FIG. 8 is a block diagram of a network system according to the third embodiment. 8, the network printer system according to the third embodiment includes a client 1, a server 40, a network printer 3 [1], a virtual network printer 3 [Y], a backbone 4, a local node 5, and a router 20. Is done.

Only the differences from the first embodiment will be described.
The server 40 controls the network printer 3 based on a request from the client 1 and executes a printing job. In addition, the data amount of the print command string 14 is read from the request token 11, and when the data amount is equal to or smaller than the specified value TH, the print command string 14 is accepted and temporarily stored in the server disk 41 owned by the user. This specified value TH
Is previously input by the network administrator via the console.

That is, this is a portion for executing NOS. Usually, a small computer such as a workstation or a personal computer is employed and has the functions of the token queue 9, the print server manager 42, and the virtual network printer 3 [Y]. These functions are executed according to a software program provided in advance in the server 40. Further, the server disk 41 as a storage element
Is provided.

The print server manager 42 is a part of the function of the server 40 that, when a plurality of request tokens 11 are accepted, generates and returns a start token 12 in the order of acceptance. Further, the Nbyte (FIG. 4) of the request token 11 is read, and when the data amount of the print command sequence 14 is equal to or smaller than the specified value TH, the start token 12 specifying the virtual network printer 3 [Y] described later is generated. This is also a part that sends a reply to the client 1. The specified value TH has been input in advance via a console by a network administrator.

The virtual network printer 3 [Y] sends the print command string 1 sent from the client 1 when the print server manager 42 returns the start token 12 specifying the virtual network printer 3 [Y].
4 is the part that accepts. The server disk 41 temporarily stores the print command sequence 14 received by the virtual network printer 3 [Y]. Usually, this part is performed by a hard disk provided in the server 40.

The other parts are exactly the same as in the configuration of the first embodiment, and the description is omitted. Next, how these components are arranged in the network system will be described with reference to the drawings.

FIG. 9 is a configuration diagram of a network system according to the third embodiment. As shown in FIG. 9, in the network system according to Example 3, a plurality of local nodes 5 are connected to a backbone 4 via a router 20. In FIG. 9, the local node 5 includes four local nodes 5 [1] to 5 [4] and the router 20 as an example.
Are limited to four routers 20 [1] to router [4].

Further, to each local node 5, a client 1, a server 40, and a network printer 3 are connected. In FIG. 9, as an example, the local node 5
[1] has Client 1 [1] and Client 1 [2]
The client 1 [3] and the client 1 [4] are in the local node 5 [2], the client 1 [5] and the network printer 3 [1] are in the local node 5 [3], and the server 40 is in the local node 5 [4]. And network printer 3
[2] is described in a limited manner. This concludes the description of the configuration of the network system according to the third embodiment, and then describes the operation.

<Operation of Embodiment 3> First, the outline of the operation of Embodiment 3 will be described with reference to FIG. In the specific example 3, the client 1 [1] transmits to the server 40 the request token 11 specifying the network printer 3 [1] and specifying the print job of the print command sequence 14 whose data amount is smaller than the specified value TH. And The server 40 accepts the request token 11. At this time, the network printer 3 [1] has already sent the print command string 1 from the client 1 [3].
It is assumed that printing is being accepted by accepting No. 4.

The server 40 sends the Nby of the request token 11
Read te (FIG. 4). As a result, client 1 [1]
Recognizes that the data amount of the print command sequence 14 requested by the user is smaller than the specified value TH. At that time server 40
Returns the start token 12 specifying the virtual network printer 3 [Y] to the client 1 [1]. The client 1 [1] that has accepted the start token 12 sends a print command sequence 14 to the virtual network printer 3 [Y].

The virtual network printer 3 [Y] receives the print command sequence 14 and stores it in the server disk 41. At this stage, the data link state between the server 40 and the client 1 [1] is released. After that, the server 40 continues to monitor the network printer 3 [1]. After the network printer 3 [1] shifts to the print standby state, the server 40 reads out the print command string 14 stored in the server disk 41 and reads out the network printer 3 [1]. 1].

Among the above operations, the difference from the operation of the specific example 1 is that when the server 40 receives the request token 12 from the client 1 [1], the server 40
1 is read and the print command string 1 is read.
4 is only the operation when the data amount is smaller than the specified value TH. That is, the only operation is to generate and return a start token 12 specifying the virtual network printer 3 [Y]. All other operations are the same as those of the first embodiment, so only the operation of generating and returning the start token 12 specifying the virtual network printer 3 [Y] will be described using a flowchart.

FIG. 10 is an explanatory diagram of the operation of the network system according to the third embodiment. A description will be given according to steps S1 to S4 in FIG. Step S1 The print server manager 42 (FIG. 8) takes out the request token 11 (FIG. 8) from the token queue 9 (FIG. 8) and proceeds to step S2.

Step S2 The print server manager 42 (FIG. 8) reads out the Nbytes of the request token 11 (FIG. 8) and compares whether the data amount of the print command sequence 14 (FIG. 8) is larger than the specified value TH. If Nbyte <TH, the process proceeds to step S3, and if Nbyte ≧ TH, the process proceeds to step S4.
Fly to. Here, the process proceeds to step S3 according to the preconditions.

Step S3 The print server manager 42 (FIG. 8) proceeds to step S4, replacing the designated network printer 3 [1] of the DSTname (FIG. 4) of the start token 12 with the virtual network printer 3 [Y]. Step S4: The print server manager 42 (FIG. 8) generates the start token 12 in which the virtual network printer 3 [Y] is written, and ends.

The start token 12 generated through the above steps is returned to the client 1 (FIG. 8). Thereafter, the client 1 (FIG. 8)
When (FIG. 8) is accepted, the print command sequence 14 (FIG. 8) is delivered to the virtual network printer 3 [Y] (FIG. 8). This print command sequence 14 (FIG. 8) is temporarily stored in the server disk 41. Thereafter, after the network printer 3 [1] (FIG. 8) returns to the print standby state, the print command sequence 14 (FIG. 8) is read out by the print server manager 42 (FIG. 8), and the network printer 3 [1].
(FIG. 8).

<Effect of Specific Example 3> With the configuration described above, the following effect can be obtained in addition to the effect of the specific example 1. 1. When the network printer specified by the client is congested and the data amount of the print command sequence is relatively small, the print command sequence is once received by the server and stored in the server disk provided therein. Thus, the data link between the client and the server can be released in a short time. 2. As a result, efficient operation of the client becomes possible.

<Configuration of Specific Example 4> In specific example 1, the client 1 [3] (FIG. 2) sends the network printer 3 [1].
The server 2 (FIG. 2) that has received the request token 11 (FIG. 2) specifying (FIG. 2) is based on only the order in which the request token 11 was received and the operating status of the network printer 3 [1] (FIG. 2). Thus, the start token 12 (FIG. 2) was generated. However, the local node 5 [3] (FIG. 2) to which the network printer 3 [1] (FIG. 2) is connected also has another terminal device (FIG. 2 shows only the client 1 [5]). It is connected.

Accordingly, if the start token 12 (FIG. 2) is generated by focusing only on the network printer 3 [1] (FIG. 2), the local node 5 [3] (FIG. 2) depends on the operation status of the other terminal device. 2) may be congested. In the specific example 4, in order to avoid such a state, the local node 5 is used by using a simple network management system.
[3] (Fig. 2) Start token 1 based on overall operation status
2 (FIG. 2). To achieve this object, the network system according to the fourth embodiment is configured as follows.

FIG. 11 is a block diagram of a network printer system according to the fourth embodiment. As shown in FIG. 11, the network printer system according to the fourth embodiment includes a client 1, a server 50, and a network printer 3 [1].
And network printer 3 [2] and backbone 4
And the local node 5 [1] and the local node 5 [2]
, A local node 5 [3], a router 53 [1], a router 53 [2], a router 53 [3], a simple network management route 52 [1], and a simple network management route 52.
[2]. Hereinafter, only differences from the first embodiment will be described.

The server 50 controls the network printer 3 based on a request from the client 1 and executes a printing job. In addition, this is a part for examining the operating status of the local node 5 to which the network printer 3 is connected by using the simple network management system and examining the operating load LordS of the entire local node 5 at the present time. When a client 1 requests a print job by specifying a specific network printer 3,
The operating load LordS of the local node 5 to which the specified network printer 3 is connected is checked.

At this time, if the operating load amount LordS of the local node 5 exceeds the reference load OL, the specified network printer 3 is replaced with
A start token 12 specifying another network printer 3 connected to the local node 5 which has not yet exceeded the reference load OL or whose running load amount LordS is relatively light is generated and returned to the client 1. Here, the load OL has been input in advance by the network administrator via the console.

The simple network management system is a request message in which a management station (here, a print server manager described later) writes necessary items to a device to be managed (here, a router 53 described later). Send 56. On the other hand, this is a network management system in which the device to be managed returns a response message 57 in which desired items are written in the management station.

The server 50 is usually a small computer such as a workstation or a personal computer, and includes a token queue 9 and a print server manager 5.
1 function is provided. These functions are executed according to a software program provided in advance in the server 50.

The print server manager 51 uses the simple network management system among the functions of the server 50 to operate the load L of the entire local node 5.
This is the part for examining ordS. That is, request message 5
6 is transmitted to the router 53, and a response message 57 in which the operating load amount LordS of the local node 5 is written is accepted from the router 53.

At this time, when the operating load LordS load load of the local node 5 exceeds the reference load OL, another network printer 3 has not yet exceeded the reference load OL in place of the specified network printer 3. The start token 12 is generated by designating the network printer 3 connected to the local node 5 and returned to the client 1.

The router 53 is a relay device for connecting the local node 5 to which the terminal devices such as the client 1, the server 2, and the network printer 3 are connected to the backbone 4. Further, upon receiving the request message 56 from the print server manager 51, the operating load amount Lor of the entire local node 5 connected thereto is determined.
It is also a part for returning a response message 57 in which dS is written.

The simple network management route 52 is a virtual transmission path for the request message 56 and the response message 57 of the simple network management system. The virtual transmission path is a virtual logic circuit that connects the management target device and the management station by using the backbone 4, the local node 5, and the like that normally constitute a network. Next, the operation of the specific example 4 will be described.

<Operation of Embodiment 4> First, the outline of the operation of Embodiment 4 will be described with reference to FIG. In Example 4,
The client 1 sends the request token 11 indicating the print request by designating the network printer 3 [2] to the server 50.
Suppose you sent to This request token 11 is transferred to the server 50
Accept.

At this time, the print server manager 51
Sends a request message 56 to the router 53 [2] via the simplified network management route 52 [2]. Router 5
3 [2] accepts the request message 56 and returns a response message in which the operating load amount LordS is written to the print server manager 51. It is now assumed that the terminal device 54 and the terminal device 55 connected to the local node 5 [2] are also operating, and the active load amount LordS has exceeded the reference load OL.

At this time, the print server manager 51
Sends a request message 56 to the router 53 [1] via the simplified network management route 52 [1]. Router 5
3 [1] accepts this request message 56 and returns a response message in which the running load amount LordR is written to the print server manager 51. Now, suppose that the operating load amount LordR of the local node 5 [1] has not exceeded the reference load OL. At this time, the print server manager 51 generates a start token 12 specifying the network printer 3 [1], and returns it to the client 1. Subsequent operations are the same as those of the first embodiment.

Among the above operations, the difference from the operation of the specific example 1 is that the request token 11 is transmitted from the client 1 to the server 5.
0 accepts, starts using the simple network management system to check the operating load amount LordR of the local node 5 [2] and the local node 5 [1], and selects and designates a predetermined network printer 3 [1]. Only the operation of generating and returning the token 12 is performed. All other operations are the same as those of the first embodiment, so only the operation of generating and returning the start token 12 specifying the predetermined network printer 3 [1] will be described using a flowchart.

FIG. 12 is a diagram for explaining the operation of the network system according to the fourth embodiment. A description will be given according to steps S1 to S7 in FIG. As a precondition, the operating load LordS of the local node 5 [2] (FIG. 11) is
The load exceeds the reference load OL, and the local node 5 [1]
It is assumed that the operating load amount LordR in FIG. 11 still has room. Step S1 The print server manager 51 (FIG. 11) takes out the request token 11 (FIG. 11) from the token queue 9 (FIG. 11) and proceeds to step S2.

Step S2 The print server manager 51 (FIG. 11) reads the designated network printer 3 [2] (FIG. 11) of the DSTname (FIG. 4) of the request token 11 (FIG. 11). The print server manager 51 (FIG. 11) sends a simple network management route 52 [2] (FIG. 1) to the router 53 [2] to which the network printer 3 [2] (FIG. 11) is connected.
The request message 56 (FIG. 11) is transmitted via 1) to inquire about the active load amount LordS. Router 53
[2] indicates a response message 57 indicating the operating load amount LordS.
, And returns to step S3.

Step S3 The print server manager 51 (FIG. 11) compares the operating load amount LordS with the reference load OL to determine whether the load amount LordS is equal to LordS.
<OL, the network printer 3 [2]
Since there is no problem even if a print job is requested to (FIG. 11), the process jumps to step S6. When LordS ≧ OL, if the printing is requested to the network printer 3 [2] (FIG. 11) as it is, the local node 5 [2] is congested, and the operation of the other network printer 3 [1] (FIG. 11) is performed. The process proceeds to step S4 to investigate the medium load amount LordR. Here, the process proceeds to step S4 based on the preconditions.

Step S4 The print server manager 51 (FIG. 11) sends the simple network management route 52 [1] (FIG. 1) to the router 53 [1] to which the network printer 3 [1] (FIG. 11) is connected.
A request message 56 (FIG. 11) is transmitted via 1) to inquire about the active load amount LordR of the local node 5 [1]. The router 53 [1] has an operating load amount LordR.
Is written in the response message 57 and returned.
Go to 5.

Step S5 The print server manager 51 (FIG. 11) compares the operating load amount LordS of the local node 5 [2] with the operating load amount LordR of the local node 5 [1].
When S <LordR, the process proceeds to step S6, where LordS ≧
If it is LordR, go to step S7. Here, the process proceeds to step S7 based on the preconditions.

Step S7 The print server manager 51 (FIG. 11) changes the designated network printer 3 [2] to the designated network printer 3
The process proceeds to step S6 instead of [1]. Step S6 The print server manager 51 (FIG. 11) generates the start token 12.

The start token 12 generated through the above steps is returned to the client 1 (FIG. 8). Thereafter, the client 1 (FIG. 8)
When the print command sequence 14 (FIG. 8) is received when the network printer 3 [1] (FIG.
Deliver to 1). In step S5, LordS
<OL is the most ideal state, and the operation flow proceeds to step S7.

<Effects of Specific Example 4> With the configuration described above, the following effects can be obtained in addition to the effects of Specific Example 1. 1. When the operating load of the local node connected to the network printer specified by the client exceeds the reference load, change the specification to a network printer connected to another local node with a lighter operating load. be able to. 2. As a result, network congestion can be prevented.

<Configuration of Specific Example 5> In specific example 1, the client 1 [3] (FIG. 2) sends the network printer 3 [1].
The server 2 (FIG. 2) that has received the request token 11 (FIG. 2) designating (FIG. 2) has generated the start token 12 (FIG. 2) in the order in which the request token 11 (FIG. 2) was received. In the specific example 5, this request token 11 (FIG. 2)
Start token 1 taking into account the priorities determined in advance
2 (FIG. 2).

FIG. 13 is a block diagram of a network system according to the fifth embodiment. As shown in FIG. 13, the network printer system according to the fifth embodiment includes a client 1
It comprises a server 60, a network printer 3, a backbone 4, a local node 5, and a router 20. Only differences from the first specific example will be described.

The server 60 controls the network printer 3 based on a request from the client 1 to execute a printing job. When a print job is requested by specifying a specific network printer 3 from a plurality of clients 1, this is also a part for determining the execution order. That is, it is the part that executes the NOS for managing the network. Usually, a small computer such as a workstation or a personal computer is employed, and the token queue 9
, A print server manager 61, and a client priority table 62. These features
It is executed according to a software program provided in advance in the server 60.

The token queue 9 is a queue for receiving and storing the request token 11 from the client 1. The print server manager 61 communicates with the server 60
Is a part having a priority order table 62 to be described later and having a function of determining the order of return of start tokens when a plurality of request tokens are accepted.
The client priority table 62 is a table in which priorities for a plurality of clients are determined. This priority is input in advance by the network administrator via the console.

<Operation of Embodiment 5> FIG. 14 is an explanatory diagram of the operation of the network system according to Embodiment 5. Only the difference from the specific example 1, that is, the operation for determining the priority order
4 will be described in accordance with steps S1 to S5. Preconditions are defined as follows. Although only one client 1 is described in FIG. 13, it is assumed here that five clients 1 [1] to 1 [5] are connected as shown in FIG. 2, for example.

As described in the client priority table 62 (FIG. 13), the client 1 [1] and the client 1 [2] have the highest priority, and the client 1 [3] and the client 1 [3] have the highest priority. It is assumed that 1 [4] is set as the second priority. Further, in the token queue 9 (FIG. 13), the network printer 3 [2] (FIG. 13) is designated, and the request token 11 (FIG. 13) from the client 1 [1], the client 1 [3], and the client 1 [5]. 13)
Is stored. It is assumed that the network printer 3 [2] (FIG. 13) is currently operating based on a request from another client.

Step S1 The print server manager 61 (FIG. 13) waits until the network printer 3 [2] (FIG. 13) terminates the printing currently in operation and is released, and
When [2] (FIG. 13) is released after printing is completed, the process proceeds to step S2.

Step S2 The print server manager 61 (FIG. 13) searches for a request token 11 for the network printer 3 [2] (FIG. 13). Here, from the precondition, client 1 [1]
Then, the request token 11 from the client 1 [3] and the client 1 [5] is searched, and the process proceeds to step S3.

Step S3 The print server manager 61 (FIG. 13) refers to the client priority table 62 (FIG. 13) and selects the request token 11 having the highest priority from the retrieved request tokens 11. Here, the client 1 [1] is selected based on the precondition, and the process proceeds to step S4.

Step S4 The print server manager 61 (FIG. 13) generates the start token 12 and returns it to the client 1 [1]. The client 1 [1] that has accepted the start token 12 sends the print command sequence 14 directly to the network printer 3 [2].
Distribute to

Step S5 The print server manager 61 (FIG. 13) searches for the request token 11 to the network printer 3 [2] (FIG. 13) again. If the print waiting request token can be searched, the process returns to step S1, and the process ends after returning the start token to all the print waiting request tokens.
Here, the processing returns to step S1 from the preconditions, and the processing is performed according to the priority order.
After returning the start token in the order of [5], the process ends. Subsequent operations and other operations have already been described in the first embodiment, and will not be described here.

<Effect of Specific Example 5> With the configuration described above, the following effect can be obtained in addition to the effect of the specific example 1. That is, the priority of a client with a high degree of urgency can be increased and the priority of a client with a relatively low degree of urgency can be lowered, so that congestion can be resolved for important data and the like.

<Configuration of Specific Example 6> In the specific example 2, the server 2 that has received the request token 11 (FIG. 5) specifying the network printer 3 [2] from the client 1 (FIG. 5).
(FIG. 5) designates a predetermined network printer 3 [1] (FIG. 5) in place of the network printer 3 [2] (FIG. 5) when the network printer 3 [2] (FIG. 5) is out of order. , Created a starting token. In this case, when selecting the predetermined network printer 3 (FIG. 5), it is necessary to select the predetermined network printer 3 (FIG. 5) based on the size of the paper size used for printing.

In the specific example 1, the client 1 (FIG. 5)
Is network printer 3 [2] and print paper size is A
The request token 11 (FIG. 5) specified in No. 4 was transmitted,
The designated network printer 3 [2] may have A3-size paper currently set. In such a case, the server 2 needs to find a network printer on which A4 size paper is set. To cope with such a case, the specific example 6 has the following configuration.

FIG. 15 is a block diagram of a network system according to the sixth embodiment. As shown in FIG. 15, the network printer system according to the sixth embodiment
, A server 80, a network printer 3 [1], a network printer 3 [2], a backbone 4, a local node 5, and a router 20.

Only the differences from the first embodiment will be described.
The client 70 is a part that requests the server 80 for a printing job. The operator inputs desired print data and transmits the request token 73 to the server 80. This server 80
When the start token 74 is received, the print data is distributed to a predetermined network printer 3. Usually, small computers such as workstations and personal computers are employed, and applications 6
, Printer driver 7 and network driver 71
And other functions. These functions are provided by the client 70
It is executed according to a software program provided in advance.

The network driver 71 is control software for transmitting the request token 73 from the client 70 to the server 80 and distributing the print command sequence 14 to the network printer 3. Example 1 and Example 6
The difference from this is in the request token 73. The request token will be described with reference to the drawings.

FIG. 16 is a configuration diagram of a request token and a start token according to the sixth embodiment. (A) shows a request token. (B) shows a start token. From FIG. 16A, the request token is framed as follows.

At the head of the frame, a command RQ indicating that this token is a request token is written, and thereafter, an SCRnam indicating the client name of the request source in order.
e, destination network printer name DSTname,
A job # indicating the printing operation, a Psize indicating the size of the sheet, and an end element TM indicating the end of the token are written. In the specific example 2, Nby indicating the size of the data is replaced by Psize indicating the size of the sheet.
te was written.

Similarly, the start token is framed as shown in FIG. 16B as follows. At the beginning of the frame, a command S indicating that this token is a start token
T is written, and in the following, SCRname indicating the client name of the request source, network printer name DSTname of the printing destination, job # indicating the printing job,
A terminator TM indicating the end of the token is written.

Returning to FIG. 15 again, the description of the configuration of the embodiment 6 will be continued. The server 80 controls the network printer 3 based on a request from the client 1 and executes a printing job. When a printing job is requested from a plurality of clients 1, the execution order is determined. Further, when the size of the paper set in the network printer 3 specified by the client 1 is different from the paper size specified by the client 1, this portion is used to select another predetermined network printer 3.

Normally, a small computer such as a workstation or a personal computer is employed, and has the functions of a token queue 9, a print server manager 81, and a network printer paper size table.
These functions are executed according to a software program provided in the print server manager 81 in advance.

The print server manager 81, when receiving the request token 73, refers to the network printer paper size table 82, selects a predetermined network printer 3, and returns a start token 74. Network printer paper size table 82
Is a table in which paper sizes of a plurality of network printers are described. This paper size has been input in advance by the network administrator via the console. Next, the operation of the specific example 6 will be described.

<Operation of Embodiment 6> FIG. 17 is an explanatory diagram of the operation of the network system according to Embodiment 6. Preconditions are defined as follows. Network printer 3 [1]
The paper size of (FIG. 15) is defined as A4 size, and the paper size of the network printer 3 [2] (FIG. 15) is defined as A3 size.

It is assumed that the client 70 (FIG. 15) has transmitted to the server 80 the network printer 3 [2] and the request token 73 in which the paper size Psize is specified to be A4 size. Hereinafter, the processing of the request token 73 will be described with reference to steps S1 to S6 in FIG.

Step S1 The print server manager 81 (FIG. 15) takes out the prerequisite request token 73 (FIG. 15) from the token queue 9 (FIG. 15) according to the order, and proceeds to step S2. Step S2: The print server manager 81 (FIG. 15) reads the network printer paper size table 82 (FIG. 15)
The paper size set in the network printer 3 [2] specified by the request token 73 (FIG. 15) is searched, and the process proceeds to step S3.

Step S3 The print server manager 81 (FIG. 15) reads the designated paper size from the request token 73 (FIG. 15) and reads the specified paper size from the network printer paper size table 82 (FIG. 1).
Compare with the paper size retrieved from 5). If the two paper sizes are equal, the process proceeds to step S4. If the two paper sizes are different, the process proceeds to step S5. Here, the process proceeds to step S5 based on the preconditions.

Step S5 The print server manager 81 (FIG. 15) searches the network printer paper size table 82 (FIG. 15) to detect the network printer 3 [1] on which A4 size paper is set, and proceeds to step S6. Proceed to.

Step S6 The print server manager 81 (FIG. 15) rewrites the DSTnamer (designation destination) of the start token 74 to the network printer 3 [1], and proceeds to step S4. Step S4: A start token 74 is generated and returned to the client 70, and the operation ends. Subsequent operations are exactly the same as those in the specific example 2, and the description is omitted.

<Effect of Specific Example 6> With the configuration described above, the following effect can be obtained in addition to the effect of the specific example 2. 1. The printing process will not be interrupted because the specified network printer does not match the paper size requested by the client. 2. As a result, congestion in the network can be avoided.

[Brief description of the drawings]

FIG. 1 is a block diagram of a network printer system according to a specific example 1.

FIG. 2 is a configuration diagram of a network system according to a specific example 1.

FIG. 3 is an explanatory diagram of an operation of a network driver.

FIG. 4 is a configuration diagram of a request token and a start token.

FIG. 5 is a block diagram of a network system according to a specific example 2.

FIG. 6 is a configuration diagram of a network system according to a specific example 2.

FIG. 7 is an explanatory diagram of an operation of a network system according to a specific example 2.

FIG. 8 is a block diagram of a network system according to a specific example 3.

FIG. 9 is a configuration diagram of a network system according to Example 3;

FIG. 10 is an explanatory diagram of an operation of the network system according to the third specific example.

FIG. 11 is a block diagram of a network system according to Example 4;

FIG. 12 is an explanatory diagram of an operation of a network system according to a specific example 4.

FIG. 13 is a block diagram of a network system according to a specific example 5.

FIG. 14 is an explanatory diagram of the operation of the network system according to the specific example 5.

FIG. 15 is a block diagram of a network system according to a specific example 6.

FIG. 16 is a configuration diagram of a request token and a start token according to a specific example 6.

FIG. 17 is an explanatory diagram of the operation of the network system according to Example 6;

[Explanation of symbols]

 1 Client 2 Server 3 Network Printer 4 Backbone 5 Local Node 6 Application 7 Printer Driver 8 Network Driver 9 Token Queue 10 Print Server Manager 11 Request Token 12 Start Token 14 Print Command String 20 Router

Claims (6)

[Claims] 1. A network printer system in which a client for requesting a print job, a printer for executing a print job, and a server for controlling the client and the printer are arranged. It converts it into a request token to be specified and a print command string to specify the print contents, and specifies the printer that executes the print job.
A network driver for transmitting the request token to the server, wherein the network driver transmits the request token to the server prior to distribution of the print command sequence, and the server receives the request token from the client A token queue that sequentially accumulates, and a print server manager that detects whether the printer is in a print standby state and detects a print standby state of the printer, wherein the print server manager is that the printer is in a print standby state Detecting the request token from the token queue, and causing the client transmitting the request token to directly distribute the print command sequence to the printer. 2. The network printer system according to claim 1, wherein the print server manager takes out the request token, reads out the contents of the request, and recognizes that the printer specified by the client cannot be operated. A network printer system for directly distributing the print command sequence to another printer in place of the printer designated by the client. 3. The network printer system according to claim 1, wherein the server includes a virtual network printer that receives and temporarily stores the print command sequence and a server disk, and the print server manager extracts the request token. The request content is read out, and when the data amount of the print command sequence is smaller than a predetermined value, the print command sequence is directly delivered to the virtual network printer instead of the printer specified by the client, and the server A network printer system, wherein the command sequence is temporarily stored in a disk, and the command sequence temporarily stored in the server disk is read out at a predetermined time and forwarded to a predetermined printer. 4. The network printer system according to claim 1, wherein the server comprises a simple network management system for individually managing a plurality of local nodes constituting the network system, wherein the print server manager comprises: Using the simple network management system, the operating load of the local node including the printer is monitored, and when the operating load exceeds a predetermined reference load, the operating load is smaller than the operating load of the local node. A network printer system which detects an operating load amount of another local node and directly distributes the print command sequence to the other local node. 5. The network printer system according to claim 1, wherein, when the server receives the request token from a plurality of clients, the server determines an order of the clients for distributing the print command sequence to the printer. A network printer system comprising a client priority table, wherein the print server manager causes the plurality of clients to directly deliver the print command sequence to the printer in an order defined in the client priority table. 6. The network printer system according to claim 1, wherein the server includes a network printer paper size table for registering a size of paper set in the printer, and the print server manager receives a print request from the client. A network printer system that, when the request token is received, refers to the network printer paper size table and directly distributes the command sequence to a printer in which paper of a size designated by the client is set.