JP2006252119A - Distributed print control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve printing speed by simultaneously executing the creation and printing of printing data by a printer driver or the like, in a system wherein a client issues a print request to a server. <P>SOLUTION: A network print system creating image data in the server is added with the following systems: for requesting the creation of page print data for obtaining an actual specific print page; for receiving the page print data to store them in consideration of processing for transferring them to an image generation part; and for transferring the data to the image generation part by detecting printing completion in the image generation part. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a network print system for printing a form or the like via a network.

  Processing for generating and printing print data on a server in response to an instruction from a browser is provided. On the other hand, a process for reducing the processing load of the entire system by independently configuring a plurality of image generation units from the server is provided for the proposal.

As a conventional example, for example, Patent Document 1 can be cited.
JP 2000-284937 A

  In the conventional distributed printing method, although there are a plurality of image generation units, it is not possible to perform a distributed process in which a plurality of image generation units perform a printing process in parallel in order to obtain one print result. , Hardware and software resources could not be used effectively.

  The present invention has been made to solve the above-described problems, and for printing to obtain a specific page as a printing result in order to finish printing in the shortest time within the range of the two-pole concept of “front” and “back”. To improve the printing speed by transferring the data and the form form for printing (hereinafter referred to as “page print data”) sequentially to the two image generators, printing each face-up and face-down. Provide a framework.

  According to the present invention, in a network print system under a Web environment, image generation and printing can be performed substantially in parallel without performing special distributed scheduling, and in a form that completely complements both. Printing can be performed, and printing can be completed even if one of the printings is delayed.

  A request is made to a conventional network system to generate page print data, the result is received and stored in consideration of processing to transfer to the image generation unit, and the data is detected by detecting the completion of printing in the image generation unit Is added to the image generation unit.

  The mechanism for receiving the completion of printing is not limited.

(Example 1: System configuration)
The system configuration will be described with reference to FIG. Reference numeral 101 denotes an information processing apparatus such as a PC as a client. Reference numeral 102 denotes a browser for inputting / outputting data to / from the server. Reference numeral 103 denotes a print output unit for converting an image displayed on the browser into standard print data in accordance with an instruction from the 102 browser. Reference numeral 104 denotes a printing apparatus. Reference numeral 105 denotes that the server and the client are connected via a network. As long as it corresponds to the communication procedure of Web environment, such as LAN, the internet, and radio | wireless, the kind will not ask | require.

  Reference numeral 106 denotes an information processing apparatus that is a Web server, and also serves to distribute processing according to designated input / output. Reference numeral 107 denotes a network communication control unit that plays a role of 106 as a Web server. Reference numeral 108 denotes a part for storing addresses of image generation apparatuses that are candidates for processing, 109 denotes a part for sequentially distributing page print data to a plurality of image generation units, and 110 denotes a part for storing a form template for form printing. . 111 is equivalent to 105.

  Reference numeral 112 denotes an image generation apparatus. There are several in this proposal. Reference numeral 113 denotes a network communication control unit 112 that communicates with the Web server. Reference numeral 114 denotes a storage portion of a form template for performing form printing.

  Reference numeral 115 denotes a data storage unit such as a database, which stores business data. Reference numeral 116 denotes an application logic stored in the data processing unit. Reference numeral 117 denotes an image generation unit that creates a form image according to a predetermined format. An image generation program 118 is dynamically added to the image generation unit. A print output unit 119 converts data generated by the image generation unit into a format that can be output by the printer, and is generally called a printer driver. Reference numeral 120 denotes a printer.

(Example 2: page print data)
The outline of the intermediate data and page print data which are the premise of the present proposal will be described with reference to FIG.

  The image generation unit inputs a plurality of print form forms and a plurality of print page data, rearranges them in the order of print pages, generates intermediate data (201) composed of page print data, and generates page print data and Assume that print page number information (203 to 205) can be extracted. Hereinafter, the information of the page print data and the print page number is simply referred to as page print data.

  Reference numeral 201 denotes file management information that holds an offset value in a file of data serving as a source of a plurality of page print data and a page number when the data is actually printed. Reference numeral 202 denotes one extraction unit in 201, and the page print data indicated by 203 to 205 is generated based on it. For example, 203 represents the first page and 205 represents the last page.

  Further, it is assumed that the image generation unit can generate a form print image by extracting a print form form and print data from the page print data.

  Although FIG. 2 shows an example in which three page print data are generated from one intermediate data, the number of page print data is generally arbitrary.

  In this proposal, the intermediate data is only mentioned in the process of extracting the page print data and does not use the characteristics of the intermediate data. Details of the format of the page print data are not mentioned.

(Example 3: Processing for distributing page print data)
An outline of processing for distributing the extracted page print data to the two image generation apparatuses will be described with reference to FIG. It is assumed that there are printers capable of face-up output and printers capable of face-down printing.

  Reference numeral 301 denotes a page print data group. In the figure, page print data 1 represents the first page, and page print data n represents the last page. Reference numeral 302 denotes a Web server, which requests 303 to generate page print data. In 303, the top of the page and the end of the page are alternately separated, and the page print data is sequentially returned to 302. In 302, the first page side is transferred to the image generation unit 1 304, and the last page side is transferred to the image generation unit 2 305 to request printing. The page print data 304 is printed face-down sequentially, and the page print data is printed 305 face-up sequentially. Reference numeral 306 represents a face-down print, and 307 represents a result printed with the face-up print.

(Embodiment 4: Push processing of page print data stack in Web server)
A process of stacking page print data generated by the image generation unit as a preparation for efficiently transferring the page print data to the two image generation units will be described with reference to FIG.

  Each of the page print data has an identification number and a symbol indicating that it has been separated from the first page side (hereinafter referred to as a head end identifier): f, or a symbol: b indicating that it has been separated from the last page side. Stack management. Let us denote the beginning and end identifier indicating the end of extraction by e. The index on which the identification number is pushed will be expressed as an index. The initial value of the index is 0, that is, index: 0 means the first.

  The third image generation unit is requested to generate page print data (401). If the head / end identifier is not e (402), an identification number is inserted at the index number of the stack (403). If e, the process is interrupted and preparation for a new intermediate data generation request is started. The head / end identifier of the received page print data is confirmed (404). If it is f, 1 is added to index (405). If it is b, the next page print data is processed without doing anything. . 405 is intended for preparation of 403, and 403 is a device for facilitating pulling of a stack described later.

(Example 5: Face-down printer print request in Web server)
With reference to FIG. 5, page print data transfer to an image generation unit that executes printing on a face-down printer will be described. A case where the stack is empty is expressed as null. It is assumed that the image generation unit can detect completion of printing and notify the Web server.

  If the stack is null, it waits until it is stacked (501). When waiting for the completion of printing from the image generation unit (502), it waits for the end (503). When the index is not 0 (504), that is, only when there is data to be pulled, the identification number is pulled from the top of the stack, the corresponding page print data is transferred to the image generation unit, and printing is requested (505). 1 is subtracted from the index (506). If it is 0, it means that there is no identification number that can be pulled, and the processing returns to step 501. 506 is preparation for 403, and is a device for enabling 505.

(Example 6: Face-up printer print request in Web server)
With reference to FIG. 6, page print data transfer to an image generation unit that performs printing on a face-up printer will be described. As in the fifth embodiment, the case where the stack is empty is expressed as null. It is assumed that the image generation unit can detect completion of printing and notify the Web server.

  601 is equivalent to 501, 602 is equivalent to 502, and 603 is equivalent to 503. When the index is not equal to the stack size (604), that is, only when there is data to be pulled, the corresponding page print data is transferred from the end of the stack to the image generation unit and requested to be printed (605).

(Embodiment 7: Reception of page print data in a Web server and transfer to the image generation unit)
The reception of page print data and transfer to the image generation unit in the Web server will be specifically illustrated with reference to FIGS.

  FIG. 7 is a processing sequence diagram, in which identifiers (1) to (8) of page print data are transferred to the Web server at timings indicated by 701 to 708, and transferred to the image generation unit at timings indicated by 710 to 717. Assume that the reception is repeated. Reference numeral 709 denotes a process indicating the end of separation.

  FIG. 8 shows a time series of time, page print data identification number, head end identifier, stack state, index, and transferred data identification number when processed in the sequence of FIG. The page print data identification numbers in FIG. 8 correspond to those in FIG.

(Example 8: Return of print data)
If actual printing is expected to take a long time, the page print data is converted to print data, transferred to the Web server, and then transferred to the image generation unit. It is also possible to increase the throughput by omitting the process of converting data into print data.

Block diagram of a network print system embodying the present invention Explanation of the characteristics of the intermediate data format Conceptual diagram of distributed transfer of page print data to image generator Flowchart for pushing page print data Flowchart for pulling page print data Flowchart for pulling page print data Sequence example of page print data generation and transfer to image generation unit Example of time series such as stack contents

Claims (4)

A network print system including a client terminal that performs a plurality of print instructions on a network, a Web server that can store form data and print data, and an image generation unit that can generate a print image, in accordance with instructions from the client terminal, The Web server extracts print data and a print form, transfers the print data and the print form to an image generation unit, and the image generation unit creates and outputs a form print image. And
In a network print system, wherein processing is distributed to a plurality of the image generation apparatuses existing on a network,
In general, an arbitrary image generation unit extracts a set of print data and a print form form that obtains a specific page as a print result from a plurality of print data and a plurality of print form forms as a print unit. A network printing system, wherein after returning to a server, the printing unit is transferred to an arbitrary plurality of image generating units, and the image generating unit creates and prints a form print image.   2. The network print system according to claim 1, wherein print units are extracted in order from the side closest to the print first page, while print units are extracted in order from the side close to the print end page, and returned to the Web server in the process of extraction, The Web server transfers the received data to the two image generation units, one of the print units on the print first page side in the order received, and when the completion of printing is notified from the image generation unit The other print unit is transferred, and the print unit on the end page side of the print is transferred in the order received, and when the completion of printing is notified from the image generation unit, the next print unit is transferred and there is no print unit to transfer. The network print system is characterized in that the processing is terminated at the time of receipt.   3. The network print system according to claim 2, wherein the image generation unit transferred from the head prints face-down and the image generation unit transferred from the end prints face-up.   3. The network print system according to claim 2, wherein the print unit is converted into print data and then returned to the Web server.

Images