JP2015172933A - Information processing apparatus, information processing method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing apparatus that can efficiently utilize resources.SOLUTION: There is provided an information processing apparatus 32 that creates drawing data by using a print job including print data and setting information, the information processing apparatus including: conversion means 56 for converting the setting information into setting information for the apparatus for drawing data creation means; drawing data creation request means 55 for outputting a request to create drawing data to drawing data creation control means by using the print data and the setting information for the apparatus; the drawing data creation control means 58 for storing the print job the creation of which has been requested by the drawing data creation request means, in storage means 66 associated with the respective plurality of drawing data creation means; and the plurality of drawing data creation means 59 for creating the drawing data by acquiring the print job stored in the storage means from the drawing data creation control means.

Description

  The present invention relates to an information processing apparatus that creates drawing data using a print job including print data and setting information.

  So-called production printing for printing and binding a large amount of business-use documents is known (see, for example, Patent Document 1). Patent Document 1 discloses a printing system capable of notifying a user whether or not post-processing is available in consideration of the entire printing system.

  In production printing, a printing process is often handled as a workflow, but in the printing workflow, the printing workflow is being opened. With the opening, it becomes possible for each company's software (workflow application to be described below) and printing devices to describe settings of print jobs in the main printing process using a common description method. A standard format called JDF (Job Definition Format) is known as a format for describing the entire process of a print workflow.

  The print workflow process includes various processes such as document and content creation, print method designation, printing, and post-processing. Each of these processes is performed by various workflow applications and printing devices, but JDF enables cooperation between printing devices and management of printing processes regardless of differences in the manufacturers of workflow applications and printing devices.

  However, each workflow application or printing device may extend JDF. In this case, the JDF created by each company's workflow application may include a description unique to the workflow application. In this case, it is known that a situation occurs in which the workflow application or the printing device in the lower process cannot analyze and process the JDF.

  FIG. 23 is an example of a diagram for explaining inconvenience when the JDF is extended. It should be noted that FIG. 23 is a comparative example and not a conventional example. In a situation where the JDF cannot be analyzed and processed, as shown in FIG. 23A, the workflow application or printing device in the lower process can determine the manufacturer of the workflow application that created the JDF by analyzing the JDF. Be considered. For example, the print processing apparatus of company C analyzes the JDF in company A (company B) format created by the workflow application of company A (company B) and determines that the print job is for company A (company B). If it can be determined that the JDF is in Company A (Company B) format, the extended format is known, so the print processing apparatus converts JDF of Company A (Company B) into setting information corresponding to Company C, and Company A (Company B). ) Print jobs can be rendered.

  However, the output result may change depending on the workflow application of each company or the rendering engine of the printing device.

  Therefore, as shown in FIG. 23B, it is considered that the print processing apparatus of company C has a rendering engine (hereinafter referred to as RIP engine) corresponding to the workflow application of each company. As a result, even if each company extends PDL, the print processing apparatus of company C can render a print job with a finish intended by the user.

  However, when a plurality of RIP engines are installed as shown in FIG. 23B, there is a problem that the print processing apparatus cannot efficiently use the resources of the print processing apparatus including each RIP engine.

  In view of the above problems, an object of the present invention is to provide an information processing apparatus that can efficiently use resources.

  The present invention is an information processing apparatus that creates drawing data using a print job including print data and setting information, and converts the setting information into apparatus setting information for each drawing data creation means ( For example, a JDF analysis unit), a drawing data creation request unit (for example, a job control unit) that outputs a drawing data creation request to the drawing data creation control unit using the print data and the apparatus setting information, and the drawing The drawing data creation control means (for example, RIP control unit) for storing the print job requested to be created by the data creation request means in the storage means associated with each of the plurality of drawing data creation means, and the drawing data creation A plurality of drawing data creation means (for example, a RIP engine) that obtains a print job stored in the storage means from the control means and creates drawing data And having a, the.

  An information processing apparatus that can efficiently use resources can be provided.

FIG. 6 is an example of a diagram schematically illustrating an operation when a DFE shown for comparison acquires a print job. It is an example of the figure explaining the schematic structure of DFE of this embodiment. 1 is an example of an overall configuration diagram of a printing system. It is an example of the hardware block diagram of DFE. It is a figure which shows an example of the functional block diagram of DFE. It is an example of the detailed functional block diagram of a job control part and a RIP part. It is an example of the figure which illustrates a job management list typically It is a figure which shows an example of the execution order setting screen displayed on the display. It is an example of the figure explaining a part of description of JDF. It is a figure which shows an example of a conversion table. FIG. 10 is an example of a diagram illustrating creation of “job attributes within DFE”. It is a figure which shows an example of the "job attribute in DFE". It is a figure which shows an example of "RIP Parameter List." FIG. 6 is an example of a diagram illustrating a correspondence between a RIP standby queue and a job management list. FIG. 6 is an example of a diagram illustrating an order in which a print execution request is made to a printer control unit. It is an example of the sequence diagram which shows the procedure in which a user sets a printing order. It is an example of a sequence diagram showing an operation procedure of the printing system. FIG. 6 is an example of a diagram illustrating rendering processing and printing timing of each RIP engine. It is a figure which shows an example of the execution order setting screen displayed on the display. FIG. 5 is an example of a flowchart illustrating a procedure for controlling a printing order by a job control unit. FIG. 6 is an example of a diagram schematically illustrating pre-RIP performed for a print job in a RIP standby queue. It is a figure which shows an example of the RIP part 57 by which several RIP engines of the same kind were mounted. It is an example of the figure explaining the inconvenience when JDF is extended.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

FIG. 1 is an example of a diagram schematically illustrating an operation when a DFE (Digital Front End) shown for comparison acquires a print job. It should be noted that the configuration and operation of the DFE 32 in FIG. 1 are only comparative examples for explaining the characteristic part of this embodiment, and are not known examples or conventional examples. Details of the DFE 32 will be described later.
(1) The workflow application of company A sends JobA1, JobA2, and JobA3 to the DFE.
(2) Company B's workflow application sends JobB1 to DFE.
(3) The job control unit 55 outputs the print jobs to the corresponding RIP engine in the order received. For this reason, the job A1 is output to the A company RIP engine in order, and when the rendering of Job A2 and Job A3 is completed, the Job B1 is output to the B company RIP engine.
(4) Therefore, while the Company A RIP engine is processing in order from JobA1, even if the Company B RIP engine is free, JobB1 is not output to the Company B RIP engine, so the raster data creation efficiency is reduced. .

[Outline of operation of DFE of this embodiment]
Therefore, in the present embodiment, the RIP engines can be rendered in parallel as follows, and the raster data creation efficiency is improved.

FIG. 2 is an example of a diagram illustrating a schematic configuration of the DFE of the present embodiment.
I. The DFE 32 has a RIP standby queue 66 for each RIP engine. The A company RIP standby queue 66a stores the print job of the A company RIP engine, the B company RIP standby queue 66b stores the print job of the B company RIP engine, and the C company RIP standby queue 66c stores the print job of the C company RIP engine. Print jobs are stored. Therefore, even if print jobs are received in the order of JobA1, JobA2, JobA3, and JobB1, JobB1 is stored at the head of the B company RIP standby queue 66b. Therefore, if the B company RIP engine is free, the B company RIP engine It becomes possible to render.

  II. The DFE 32 also creates an instance of the job control unit 55 (A1 job control unit INS55a1, A2 job control unit INS55a1, A3 job control unit INS55a1, B1 job control unit INS55b1) for each print job. The job control unit 55 requests the RIP engine to execute rendering, and causes the RIP engine to perform rendering from one page to the last page for one print job. By creating an instance of the job control unit 55 for each print job, rendering processing can be parallelized. That is, the rendering that the A1 job control unit INS55a1 performs for the A company RIP engine and the rendering that the B1 job control unit INS55b1 performs for the B company RIP engine can be performed in parallel in time.

  Therefore, the DFE 32 of this embodiment can improve the efficiency of creating raster data because a plurality of RIP engines can render in parallel.

[Configuration example]
FIG. 3 illustrates an example of an overall configuration diagram of the printing system 200 according to the present embodiment. The printing system 200 according to the present embodiment includes one or more end user environments 1 and a POD (Print On Demand) printing system environment 2 connected via a network 3 such as a LAN or the Internet.

  A client PC 11 is arranged in the end user environment 1. The client PC 11 is equipped with a workflow application (hereinafter simply referred to as an application) 12 for POD printing work, and can generate a print job in response to a user operation.

  The application 12 may execute an aggregate printing function (Number Up imposition function) for pasting a plurality of logical page images on a sheet surface, and an image editing function for adding a header, footer, page number, and the like. it can. Further, the application 12 can designate instructions such as punching (punching) and stapling (stapling) for bookbinding. These instructions and settings are described in JDF. JDF is sometimes called a job ticket, work instruction, print instruction, or the like.

  The POD printing system environment 2 includes a process management unit 20, a digital printing unit 30, and a post press unit 40 connected via a network 3. The process management unit 20 instructs the processes of the digital printing unit 30 and the post press unit 40 in the POD printing system environment 2 to centrally manage the workflow of the POD printing system environment 2.

  The process management unit 20 receives a print job (JDF and PDL) from the end user environment 1 and stores the print job. The JDF is an example of setting information for claims. PDL is an example of print data in the claims. PDL is a language for instructing the drawing contents of a page image (rasterized image), but here, it means data described in PDL. PDL includes PDF (Portable Document Format), PostScript, PCL, RPDL, and the like.

  Further, the process management unit 20 assembles work in each process as a workflow based on a print job from the end user environment 1, efficiently schedules the work of the digital printing unit 30, the post press unit 40, and each worker, When an error occurs during automatic operation, the operator can be notified as necessary. Generally, the process management unit 20 is configured to include one or more PC servers 21.

  The process management unit 20 transmits a print job to the digital printing unit 30 to perform printing. Further, the printed material is conveyed to the post press unit 40, and the post press unit 40 performs bookbinding or the like according to an instruction from the process management unit 20. Note that the print job may be transmitted directly from the digital printing unit 30 to the post press unit 40.

  The digital printing unit 30 is configured to include various printers (printer devices such as a printer for production, a high-speed color inkjet printer, and a color / monochrome MFP) 31. A DFE 32 is disposed in the digital printing unit 30. The DFE 32 is also called a print processing apparatus, and controls printing by the printer 31 (printing apparatus). The DFE 32 may be separate from the printer 31 as illustrated, or may be integrated with the printer 31. When the DFE 32 obtains a print job from the process management unit 20, the DFE 32 uses the JDF and PDL to generate raster data (an example of the drawing data in the claims) for forming a toner image or an image using ink. It is generated and transmitted to the printer 31.

  The digital printing unit 30 has various printers 31. The digital printing unit 30 is a printer directly connected to a finisher (post-processing device) for post-processing (post-processing) such as paper folding, saddle stitching, case binding, punching, etc., on the printed recording paper. 31 may be included.

  The post-press unit 40 performs post-processing such as a paper folding machine, saddle stitch binding machine, case binding machine, cutting machine, sealing machine, and bookbinding machine in accordance with the work instruction of the printed matter (post-press job) received from the process management unit 20. Configured to include devices. Further, the post-press unit 40 performs finishing processing such as paper folding, saddle stitching, case binding, cutting, enclosing, and packing on the printed matter output from the digital printing unit 30. The post press unit 40 includes post-processing devices for performing post-processing (post-processing) after digital printing, such as a stapler 401 and a punch punching machine 402.

  The end user of the end user environment 1 uses the application 12 for POD printing work from the client PC 11 to perform image editing, imposition, text insertion, post-processing instruction, etc. A print job is transmitted to the management unit 20.

  The PC server 21 of the process management unit 20 instructs printing to the digital printing unit 30 and instructs post-processing to the postpress unit 40 in accordance with JDF.

[Hardware configuration]
In this embodiment, the process management unit 20 receives a print job created by the end user environment 1, and the process management unit 20 transmits the print job to the DFE 32.

  FIG. 4 shows an example of a hardware configuration diagram of the DFE 32. The DFE 32 is realized by a hardware configuration as shown in FIG. That is, the DFE 32 has a function as an information processing apparatus (computer). The DFE 32 includes a CPU 321, a RAM 322, an auxiliary storage device 323, a communication device 324, an input device 325, a display control unit 326, and a recording medium I / F 327 that are mutually connected via a bus 329.

  The CPU 321 controls the entire DFE 32 by executing a program using the RAM 322 as a work memory. The auxiliary storage device 323 is a non-volatile memory such as a hard disk drive (HDD) or a solid state drive (SSD). The auxiliary storage device 323 stores a program 328 having a function of converting a print job.

  The communication device 324 is a modem, a LAN card or the like, and is connected to the network 3 to communicate with the end user environment 1, the process management unit 20, or the post press unit 40. In addition, it communicates with the printer 31. The input device 325 is a keyboard, a mouse, or the like. The input device 325 is a device that receives user operations, and is a keyboard, a mouse, or the like. The display control unit 326 is connected to the display 330 and displays a screen on the display 330 according to an instruction from the CPU 321. The display 330 may be a touch panel.

  The recording medium I / F 327 is detachable from a portable recording medium, and writes data to the recording medium 331 or reads data from the recording medium 331 according to an instruction from the CPU 321. The recording medium 331 electrically records information like an optical, electrical, or magnetic recording medium such as a CD-ROM, optical disk, USB memory, SD card (registered trademark), or a flash memory. Various types of semiconductor memories can be used.

  The program 328 is distributed in a state stored in the recording medium 331, or is distributed by being downloaded from a server (not shown) via the network 3.

  The hardware configuration diagram of the client PC 11 of the end user environment 1 and the PC server 21 of the process management unit 20 can also be realized with the same configuration as that of FIG.

[DFE functions]
FIG. 5 is a diagram illustrating an example of a functional block diagram of the DFE. The DFE 32 performs job control, RIP (Raster Image Processor) control, and printer control in the print workflow. As described above, the DFE 32 operates as a server that provides the main functions of printing to the end user environment 1 and the process management unit 20. Note that job control refers to a series of control of print job procedures such as print job reception, JDF analysis, raster data creation, and printing by the printer 31. The RIP control refers to control in which a “RIP Parameter List” is created and raster data is created by the RIP engine 59 after creating the “job attribute in DFE” described below. “RIP” is an abbreviation for “Raster Image Processor”, and refers to creating dedicated IC and raster data for creating raster data. Printer control refers to control that causes the printer 31 to transmit raster data and a part of “job attributes within DFE” (“Finishing information” described later) to perform printing.

  The DFE 32 includes a job reception unit 51, a system control unit 52, a UI control unit 54, a job control unit 55, a JDF analysis unit 56, a RIP unit 57, a RIP control unit 58, a RIP engine 59, and a printer control unit 61. ing. These are realized by the CPU 321 executing the program 328 and cooperating with various kinds of hardware including FIG. The DFE 32 also includes a job data storage unit 53 and an image storage unit 60 that are built in the auxiliary storage device 323, the RAM 322, the recording medium 331, and the like.

  The job receiving unit 51 receives a print job from the application 12 or the like via the network 3. As the log, for example, a unique job number, reception date / time, end date / time, status, and the like are recorded in association with the print job. In addition to being input from the application 12, the print job may be input from a USB memory or the like. In the present embodiment, it is assumed that JDF is included in the print job. However, when JDF is not included, the job receiving unit 51 creates a dummy JDF to enable rendering.

  The system control unit 52 stores the received print job in the job data storage unit 53 or outputs it to the job control unit 55. For example, if the DFE 32 is set in advance to store a print job in the job data storage unit 53, the system control unit 52 stores the print job in the job data storage unit 53. For example, when the JDF describes whether or not to store in the job data storage unit 53, the description is followed.

  Further, the system control unit 52 outputs the JDF from the job data storage unit 53 to the UI control unit 54 when the user performs an operation to display the contents of the print job stored in the job data storage unit 53 on the display 330, for example. . When the user changes the JDF, the UI control unit 54 receives the change contents, and the system control unit 52 stores the changed JDF in the job data storage unit 53 again.

  When the system control unit 52 receives an instruction to execute a print job from the user, the end user environment 1 or the process management unit 20 (an example outside the scope of claims), the system control unit 52 receives the job data storage unit 53. The print job stored in is output to the job control unit 55. For example, when the print time is set in the JDF, the print job stored in the job data storage unit 53 is output to the job control unit 55 when the print time is reached.

  The job data storage unit 53 is a storage area for storing a print job as described above, and is provided in the auxiliary storage device 323 or the recording medium 331 of the DFE 32. Further, it may be provided in a storage device (not shown) on the network.

  The UI control unit 54 interprets the JDF and displays the contents of the print job on the display 330. Further, raster data created by the RIP engine 59 can be displayed on the display 330.

  The UI control unit 54 includes an execution order setting unit 62 (which is an example of a print order setting reception unit in the scope of claims). The execution order setting unit 62 receives the order in which the printer control unit 61 executes print jobs. Conventionally, rendering has been completed in the order in which print jobs are received. However, in this embodiment, the RIP engines 59 of each company can render in parallel, so the order in which print jobs are received may not match the order in which rendering is completed. is there.

  The user can select the print job execution order from two: the print job reception order and the rendering completion order, and the execution order setting unit 62 accepts the user's selection. For example, when the printer control unit 61 executes print jobs in the order of completion of rendering, the waiting time of the printer 31 is reduced, and the time until the print job is executed (time until printing) can be shortened. Also, if the printer control unit 61 executes print jobs in the order of reception, printing is performed according to the order transmitted by the user, so that the user can easily grasp the print order.

  The job control unit 55 causes the RIP control unit 58 to create raster data and causes the printer control unit 61 to perform printing. Specifically, first, the JDF of the print job is transmitted to the JDF analysis unit 56 and a JDF conversion request is output to the JDF analysis unit 56.

  The JDF analysis unit 56 acquires a JDF and a JDF conversion request from the job control unit 55. The JDF analysis unit 56 analyzes the description of the JDF and determines the manufacturer of the application 12 that created the JDF. Determining the manufacturer of the application 12 that created the JDF has almost the same meaning as determining the RIP engine 59 that is supposed to render the print job.

  The JDF analysis unit 56 converts the JDF into “job attributes within DFE” that can be handled by the DFE 32 by using a conversion table 63 prepared for the manufacturer of the application 12. That is, if the DFE 32 is created by the company C, the JDF created by the application of the company A or B as well as the company C can be used as the “job attribute in DFE” that can be handled by the company DFE 32. Convert. “Job attributes within DFE” is an example of apparatus setting information in the claims.

  When it is determined that the application 12 that created the print job does not have the RIP engine 59 that is supposed to be rendered, the JDF analysis unit 56 converts the conversion table 63 for company A and the conversion table for company B. 63 and the conversion table 63 for company C create “job attributes within DFE”. Then, the attribute value of JDF and the item value of “job attribute in DFE” are compared to give a larger evaluation value as the difference is smaller, and the RIP engine 59 of “job attribute in DFE” having a larger evaluation value is selected as the optimum RIP. Select as engine 59.

  The JDF analysis unit 56 sets “RIP control mode” to “job attribute within DFE” when creating “job attribute within DFE”. The “RIP control mode” will be described below. The “RIP control mode” includes “Page Mode” and “Sheet Mode”. Whether each company's print job is created in “Page Mode” or “Sheet Mode” is investigated in advance. Therefore, if the manufacturer of the workflow application that created the JDF is determined, the “RIP control mode” can also be determined. In this embodiment, it is assumed that the DFE 32 handles the setting of the aggregate print of print jobs in “Page Mode” (Page Mode is the default).

  The job control unit 55 that has acquired the “job attributes within DFE” as described above converts the “job attributes within DFE” and the PDL into “RIP Parameter List”, and sends the “RIP Parameter List” to the RIP control unit 58. To output the print job. In the present embodiment, the job control unit 55 outputs a print job to the RIP control unit 58 for each print job.

The “RIP Parameter List” is a set of information necessary for the RIP engine 59 to perform RIP processing. The job control unit 55 determines the RIP processing instruction to the RIP engine 59 from the information of the “RIP Parameter List”. This instruction is called a RIP command. The “RIP Parameter List” includes “RIP control mode”. The RIP control unit 58 controls the RIP engine 59 in accordance with the “RIP control mode”. Therefore, the sequence is determined by the “RIP control mode”.
“Page Mode”: RIP processing is instructed for each page to create raster data consolidated into one sheet. “Sheet Mode”: Each part of one page in which multiple pages are already aggregated (each page part before aggregation) Each of the job control unit 55 has an instance creation unit 64, and the instance creation unit 64 creates an instance of the job control unit 55 for each print job. An instance created by the instance creation unit 64 is called a job control unit INS. Since the job control unit INS is created for each print job, “print job name + job control unit INS” is used for distinction. The job control unit INS has a job management list 65 for RIP execution requests. Details of these will be described with reference to FIG.

  In contrast to programming terms, the job control unit 55 corresponds to “class”, and the job control unit INS corresponds to “instance”. “Class” is generally called “type”, “design drawing”, “definition”, and “template (template)”, and “instance” is a “class” made into “actual”. Note that the programming language used in the present embodiment is not limited, and a class and an instance of a specific programming language are not intended.

  The job control unit INS does not have to be instantiated all of the functions of the job control unit 55. The job control unit INS makes a RIP execution request (an example of a claim creation request) to at least the RIP control unit 58. As long as it has. Therefore, instead of using the job control unit INS as an instance of the job control unit 55, the job control unit 55 may be created as a class by inheriting another class, and the instance of the class may be used as the job control unit INS.

  Instead of the instance creation unit 64 dynamically creating the job control unit INS, a plurality of job control units INS may be mounted in the DFE 32 in advance. However, when creating instances, it is only necessary to create as many instances as the number of print jobs, so it is easy to suppress the load on the DFE 32.

  The RIP unit 57 includes a RIP control unit 58 and a RIP engine 59, and creates raster data using them. The RIP control unit 58 analyzes the information of “RIP Parameter List” and determines a RIP engine 59 to be used from a plurality of RIP engines 59. The determination of the RIP engine 59 may be based on one or more items of the “RIP Parameter List” or based on RIP engine identification information specified in the “RIP Parameter List”. For example, based on the description “xmlns: A =“ www.aaa.com/schema/aaa ”” or “xmlns: B =“ www.bbb.com/schema/bbb ”” in the “RIP Parameter List”, the RIP engine 59 is to decide. For example, if the job control unit 55 clearly indicates the RIP engine identification information in the “RIP Parameter List”, the RIP engine 59 indicated by the RIP engine identification information is selected. The RIP control unit 58 refers to the “RIP Parameter List” and transmits a RIP command to the selected RIP engine 59.

  The RIP control unit 58 has a RIP standby queue 66 for each RIP engine. When distinguished, they are referred to as an A company RIP standby queue 66a, a B company RIP standby queue 66b, and a C company RIP standby queue 66c, respectively. The RIP standby queue 66 stores print jobs in the order in which RIP execution requests are made from the job control unit 55 to the corresponding RIP engine 59. The RIP control unit 58 outputs RIP execution requests to the RIP engine 59 in the order stored in the RIP standby queue 66.

  Further, the RIP control unit 58 refers to the “RIP Parameter List”, and outputs the RIP command to the RIP engine 59 according to “Sheet Mode” when the “RIP control mode” is “Sheet Mode”. Thereby, it is possible to absorb the difference between the print jobs (mainly PDL).

  The RIP engine 59 is a rendering engine, and creates raster data by performing rasterization according to the RIP command. The RIP engine 59 is an example of the “drawing data creation means” in the claims. The RIP engine 59 may be implemented by either software or hardware such as LSI. When implemented in software, each RIP engine 59 renders in parallel by multitasking, and when implemented in hardware, each RIP engine 59 can render independently and can render in parallel. In the RIP engine 59, software and hardware may be mixed.

  The image storage unit 60 is a storage unit that stores created raster data. The image storage unit 60 is mounted on the auxiliary storage device 323, for example. Alternatively, it may be mounted on a storage device on the network.

  The printer control unit 61 is connected to the printer 31, and performs printing by reading raster data stored in the image storage unit 60 and transmitting the raster data to the printer 31. Also, finishing processing is performed based on “Finishing information” acquired from the job control unit 55.

  The printer control unit 61 can acquire information of the printer 31 by communicating with the printer 31 using various communication standards. For example, CIP4, which defines a print workflow standard, defines a standard called DevCaps that transmits / receives device specification information to / from the printer 31 as a JDF standard. Also known is a method of collecting information about the printer 31 using a communication protocol called SNMP (Simple Network Management Protocol) and a database called MIB (Management Information Base). The printer control unit 61 uses these to acquire various types of information stored in the printer 31. For example, it is possible to obtain the configuration of the printer 31 (the presence or absence of ADF, the presence or absence of a duplex printing unit, the tray configuration, the presence or absence of a manual feed tray, the presence or absence of various finishers, etc.). In addition, the status of the printer 31 (printing, scanning, FAX reception, sleep, etc.) can be acquired. In addition, the remaining amount of paper in each tray can be acquired.

  FIG. 6 is an example of a detailed functional block diagram of the job control unit 55 and the RIP unit 57. The instance creation unit 64 creates the A1 job control unit INS55a1 by obtaining JobA1, creates the A2 job control unit INS55a2 by obtaining JobA2, and creates the A3 job control unit INS55a3 by obtaining JobA3. The B1 job control unit INS55b1 is created by acquiring JobB1 (hereinafter, the job control unit INS is omitted from the description).

  In the job management list 65, the following information is registered for each print job.

-Job reception order
-Job ID
The page number job control unit 55 registers the “reception order”, “job ID”, and “page number” of the print job in the job management list 65.

  FIG. 7 is an example of a diagram for schematically explaining the job management list 65. By managing the reception order, it is possible to control the order in which the printer control unit 61 executes print jobs (printing order) in the order of reception. The job ID is a number, character, symbol, alphabet, or a combination thereof that uniquely manages a print job in the job management list 65. The number of pages is the number of pages in the print job.

  The A1 job control unit INS outputs a RIP execution request for JobA1 to the RIP control unit 58. The A2 job control unit INS outputs a RIP execution request for JobA2 to the RIP control unit 58. The A3 job control unit INS outputs a RIP execution request for JobA3 to the RIP control unit 58. The B1 job control unit INS outputs a RIP execution request for JobB1 to the RIP control unit 58. Each job control unit INS outputs RIP execution requests in parallel.

  The RIP control unit 58 determines which RIP engine 59 the print job corresponds to, and stores it in the RIP standby queue 66 corresponding to the RIP engine 59. That is, the RIP engine 59 on which the print job is assumed to be rendered is determined, or the manufacturer of the application 12 that created the print job is determined.

  The RIP standby queue 66 stores print jobs in units of print jobs in the order in which RIP execution requests are received. The RIP control unit 58 performs rendering using each RIP engine 59 in the order of storage.

  In addition, each RIP engine 59 returns a RIP end notification (an example of a claim creation end notification) to the RIP control unit 58 for each page, so that the RIP control unit 58 performs job control for the RIP end notification for each page. Output to the unit INS. The RIP end notification includes a job ID, and the job control unit INS can determine how many pages of the print job have been rendered.

  When the job control unit 55 determines that rendering has been completed up to the last page of one print job, for example, the instance creation unit 64 deletes the job control unit INS of the print job for which rendering has been completed. Thereby, it is possible to suppress the use of resources by the job control unit INS that is no longer needed.

  Similarly, the RIP control unit 58 deletes the print job from the RIP standby queue 66 when rendering of all pages of each print job is completed.

[Setting the execution order of print jobs]
FIG. 8 is a diagram illustrating an example of an execution order setting screen displayed on the display 330. On the execution order setting screen, messages of “print job reception order” and “rendering end order” are displayed together with radio buttons 501 and 502. The user selects one of the radio buttons 501 and 502. The UI control unit 54 receives the setting of the selected execution order and outputs it to the job control unit 55. Accordingly, the job control unit 55 can output print execution requests to the printer control unit 61 in the set order.

[Determination of JDF and the manufacturer of the application that created JDF]
JDF is described in XML (Extensible Markup Language). XML is a standard for structured text in which a tag is structured to structure a document.

FIG. 9 is an example of a diagram for explaining a part of the description of JDF. Assume that the JDF in FIG. 9A is created by the application 12 of company C. In JDF, instruction contents for a print job are described.
“JDF xmlns =“ http://www.CIP4.org/JDFSchema_1_1 ”” indicates that this is a CIP4-compliant JDF ticket.
“Xmlns: C =“ www.ccc.com/schema/ccc ”” indicates a JDF tag definition uniquely extended by each printer / vendor not conforming to CIP4. In this example, all tags starting with “C:” in the JDF are extended tags.
“ResourcePool” defines a set of attributes for realizing printing.
“LayoutPreparationParams” is one of the attributes defined in “ResourcePool” and defines imposition-related attributes.
“ResourceLinkPool” defines a set of references to commonly used attributes in “ResourcePool” for a specific range within a job, such as between pages.
“ComponentLink” is one of the definitions of references in “ResourceLinkPool”, and specifies the attribute reference and information related to the output.
“Amount” specifies the number of copies.
“Rotate” specifies the rotation angle of the image.

  FIG. 9B shows an example of expansion of company A, and FIG. 9C shows an example of expansion of company B. “Xmlns: A =“ www.aaa.com/schema/aaa ”” in FIG. 9B means that all tags starting with “A:” in the JDF become extension tags of company A. “Xmlns: B =“ www.bbb.com/schema/bbb ”” in FIG. 9C means that all tags starting with “B:” in the JDF become expansion tags of B company.

  Therefore, the JDF analysis unit 56 can determine the manufacturer of the application 12 that created the JDF by referring to these descriptions in the JDF. The JDF can be converted into “job attributes within DFE” that can be handled by the CFE DFE 32 using a conversion table 63 described later according to the manufacturer of the application 12.

[Create job attributes in DFE]
Creation of “job attributes within DFE” will be described with reference to FIGS. FIG. 10 is an example of a conversion table, and FIG. 11 is an example of a diagram illustrating creation of “job attributes within DFE”. The JDF analysis unit 56 converts the JDF into “job attributes within DFE” using the conversion table 63 of the manufacturer of the application 12 that created the JDF (the RIP engine 59 that is supposed to process the print job). If the manufacturer of the application 12 that created the JDF cannot be determined, the JDF is converted into “job attributes within DFE” using all the conversion tables 63. Therefore, “job attributes within DFE” for all RIP engines are created (“job attributes within DFE” for each drawing data creation means are created).

  FIG. 10A shows an example of a conversion table for company C. The conversion table 63 of company C associates the attribute value of the attribute name “Amount” with the item value of the item name “number of copies” and sets the attribute value of the attribute name “Rotate” to the item value of the item name “rotate”. To correspond to.

  As shown in FIG. 11, the conversion method refers to the conversion table 63 that associates the attribute in the JDF tag with the item “job attribute in DFE”, and sets the JDF attribute value to the item value of “job attribute in DFE”. It is something to arrange as.

  The JDF analysis unit 56 holds not only the conversion table 63 of company C but also the conversion table 63 of company A and the conversion table 63 of company B in advance. FIG. 10B shows a conversion table for company A, and FIG. 10C shows a conversion table for company B. The JDF analysis unit 56 detects the description specifying the extension tag from the JDF as described above, determines the manufacturer of the application 12, and uses the conversion table 63 corresponding to each manufacturer.

  In the case of JDF of Company A and Company B, conversion can be performed in the same manner. The conversion table 63 of company A associates the attribute value of the attribute name “A: Amount” with the item value of the item name “number of copies” and sets the attribute value of the attribute name “A: Rotate” to the item “rotation”. Corresponds to the name field value. The conversion table 63 of company B associates the attribute value of the attribute name “B: DeliveryAmount” with the item value of the item name “number of copies” and sets the attribute value of the attribute name “B: Rotate” to the item “rotation”. Corresponds to the name field value. In the conversion table 63 of company B, rotation is enabled only when the attribute value of the attribute name “B: AlternateRotation” is “false”. Therefore, if it is determined that the JDF is from Company A or Company B, the “job attribute in DFE” can be created in the same manner as Company J's JDF.

  If the JDF analysis unit 56 determines that the print job format in the aggregate printing is created by the application 12 of a company different from the company (C company), the item “RIP control mode” of “Job attribute in DFE” Set “Sheet Mode” to. If the application 12 is an in-house manufactured application or the application 12 of the same company as the company (C company) in the print job format in aggregate printing, “Page Mode” is set in the item “RIP control mode”. Thereby, the RIP control unit 58 can control the RIP command output to the RIP engine 59 in accordance with the “RIP control mode”.

FIG. 12 is a diagram illustrating an example of “job attributes within DFE”. The “job attributes within DFE” are broadly divided into “Job information” relating to job execution, “Edit information” relating to raster data, and “Finishing information” relating to finishing processing.
The job information has an item “number of copies” that specifies the number of copies.
The item “Orientation Information” in the Edit information specifies the printing direction.
The item “printing surface information” in the Edit information specifies the printing surface.
-The item "Rotation" in the Edit information specifies the page rotation angle.
-The item "Enlarge / Reduce" in Edit information specifies enlargement / reduction and scaling.
-The item “image position: offset” in the Edit information specifies an offset of the image.
The item “image position: position adjustment information” in the Edit information specifies image position adjustment.
-The item "layout information: custom in-position arrangement" in the Edit information specifies the arrangement of the custom surface.
The item “layout information: number of pages” of the Edit information designates the number of pages of one sheet.
The item “layout information: imposition information” in the Edit information specifies information related to the surface layout.
The item “layout information: page order information” in the Edit information specifies information related to the order of pages to be printed.
The item “layout information: creep position adjustment” of the Edit information specifies information related to the adjustment of the creep position.
-The item "margin information" in Edit information specifies information about margins such as fit box and gutter.
The item “Crop mark information: center crop mark information” in the Edit information specifies information about the center crop mark.
The item “Crop Mark Information: Corner Crop Mark Information” in the Edit information specifies information regarding the corner crop mark information.
The item “Collate information” of the Finishing information specifies information on whether to print in units of pages or in units of documents when a plurality of copies of a document are printed.
The item “staple / bind information” of the finishing information designates information related to stapling / binding.
-The item "punch information" in the Finishing information specifies information related to punching.
-The item "folding information" of the Finishing information specifies information about folding.
-The item "Trim" in the Finishing information specifies information related to trim.
-The item "output tray information" of the Finishing information specifies information about the output tray.
-The item "input tray" in the Finishing information specifies information related to the input tray.
-The item "cover / sheet information" of the Finishing information specifies information about the cover / sheet.

  Further, as shown in the figure, “RIP control mode” is set in “job attribute within DFE”. In “RIP control mode”, “Page Mode” or “Sheet Mode” is set. In the case of a dummy JDF, “Page Mode” is set to “RIP control mode”.

[RIP Parameter List]
FIG. 13 is a diagram illustrating an example of “RIP Parameter List”.
• Input / output data type information specifies the type of input and output data. (For input and output data, not only PDL but also text files and image data such as JPEG are designated.
-The input / output data read / write position designation method information designates the method for designating the input / output data offset (read / write position). For example, from the specified position, from the current position, from the tail, etc. can be specified.
-The input / output data read / write position information specifies the current processing position of input and output data.
The execution mode information for reading and writing input / output data is information for specifying the execution mode. For example, READ, WRITE, READ_WRITE, etc. are specified.
-Unit information (dimension) specifies the unit to be used in the “RIP Parameter List”. For example, “mm”, “inch”, “pel”, “point”, and the like are designated.
-Input / output data compression method information specifies the compression method for input and output data. For example, “UNCOMPRESSED”, “PACKBITS”, etc. are specified.
“RIP control mode” designates a control mode in aggregate printing. For example, “Page Mode” or “Sheet Mode” is designated.

The input / output image information section includes “information relating to an output image”, “information relating to an input image”, and “information relating to image handling”.
-The image format type specifies the format of the output image format. For example, raster or the like is designated.
-The image format / dimension specifies the dimension of the output image format.
・ Image format / resolution specifies the resolution of the output image format.
-The position of the image specifies the position of the output image.
-Color separation information specifies color separation (color separation). For example, “k”, “cmyk”, “separation” and the like are designated.
The color plane fit policy information specifies the color plane development method.
The plane shift information specifies the color plane shift amount.
-The number of color bits of the image format specifies the number of color bits of the output image format.
The image orientation information specifies the page orientation of the output image.
-The image forming position information specifies the position information of the crop area.
-Image formation size information specifies size information of the crop area.
-The image formation method information specifies the clip policy.
-Color ICC information specifies information related to the color ICC profile.
-Font substitution information specifies information about font substitution.
-The image formation origin point specifies the image formation origin. For example, “center”, “upper right”, etc. are designated.
-Flat K black information specifies information about flat K black.
Rendering information specifies information related to render links (rasterization).
The image format type specifies the format type of the input image. For example, raster or the like is designated.
-The image format / dimension specifies the dimension of the input image format.
-The image format / resolution specifies the resolution of the input image format.
-The position of the image specifies the position of the input image.
-Input data specifies input data.
・ Page range information specifies page numbers.
-Color ICC information specifies information related to the color ICC profile.
-Scaling offset information specifies the offset of the scaling algorithm. For example, a horizontal offset, a vertical offset, etc. are designated.
Object / area information specifies the width and height of the object area.
-Halftone information specifies halftone offset. For example, a horizontal direction offset and a vertical direction offset are designated.
• Scaling algorithm information specifies the scaling method.

Information related to PDL specifies a data area, size information, and a data arrangement method.
The data area specifies area information in which PDL is stored. Font information, information on the number of pages, and the like are included in the PDL existing in this data area.
-The size information specifies the size of the PDL.
-The data arrangement method specifies the data arrangement method. For example, little endian or big endian is specified.

[About RIP standby queue]
FIG. 14 is an example of a diagram for explaining the correspondence between the RIP standby queue 66 and the job management list 65. 14A shows an example of the job management list 65, and FIG. 14B shows an example of a conventional RIP standby queue 66, each company, and the RIP standby queue 66.

The DFE 32 equipped with the RIP engines 59 of Company A, Company B, and Company C receives a total of four print jobs (JobA1, JobA2, JobA3, JobB1) in order. Jobs A1 to A3 have a JDF in company A format, and JobB1 has a JDF in company B format.
JobA1 (page 3)
JobA2 (2 pages)
JobA3 (page 4)
JobB1 (page 3)
Each print job received by the DFE 32 is output to the job control unit 55 via the job reception unit 51 and the system control unit 52. The system control unit 52 spools the acquired print job once in the job data storage unit 53, and after the user edits JDF or the like via the UI control unit 54, the system control unit 52 outputs the print job to the job control unit 55. Also good.

  The job control unit 55 outputs the JDF of the received print job to the JDF analysis unit 56 together with the JDF conversion request. The JDF analysis unit 56 converts the received JDF into “job attributes within DFE”, adds RIP control mode information, and outputs the information to the job control unit 55.

  As illustrated in FIG. 14A, the job control unit 55 adds the job reception order, job ID, and job page number information of the received “job attributes within DFE” as one record of the job management list 65. To do. The job control unit 55 generates a “RIP Parameter List” from the “job attributes within DFE” and the PDL.

  When receiving the RIP execution request, the RIP control unit 58 distributes the print job to the RIP standby queue 66 of each company based on the information of the “RIP Parameter List”. The first print job in the RIP standby queue 66 of each company is processed in parallel, and RIP processing can be performed more efficiently than the conventional method using the RIP standby queue.

  This will be described with reference to FIG. Conventional print jobs are stored in the same RIP standby queue 66 even if the print jobs are different. For this reason, only one (in the figure, only JobA1) could be rendered.

  On the other hand, in the present embodiment, since each RIP engine has the RIP standby queue 66, a plurality of print jobs can be executed in parallel. In the illustrated example, JobA1 in the A company RIP standby queue 66a and JobB1 in the B company RIP standby queue 66b can be rendered in parallel. If all print jobs are stored in one RIP standby queue 66, the RIP control unit 58 increases the processing for searching for a print job with an empty RIP engine from the RIP standby queue 66, and the processing load increases. Resulting in. In this embodiment, rendering can be performed in parallel without searching.

  The RIP control unit 58 makes a RIP execution request for each page to the RIP engine 59 based on the RIP control mode of the “RIP Parameter List”. The RIP control unit 58 acquires a RIP end notification in units of pages from the RIP engine 59, and outputs the RIP end notification in units of pages to the job control unit 55 together with the job ID.

  As shown in FIG. 14C, the first print job in the RIP standby queue is taken out from the RIP standby queue after rendering of all pages of the print job is completed.

  The job control unit 55 determines whether or not rendering of all pages of the print job has been completed based on the job page number information in the job management list and the RIP completion notification for each job page.

  The job control unit 55 outputs a print execution request for the print job that has been rendered to the printer control unit 61. As described above, the order in which the print execution request is made is set to either the job reception order or the rendering completion order.

  FIG. 15 is an example of a diagram illustrating the order in which print execution requests are made to the printer control unit 61. For example, assume that the print job reception order is JobA1, JobA2, JobA3, JobB1, and the rendering order is JobA1, JobB1, JobA2, JobA3.

  The job control unit 55 selects JobA1 (first page) → JobB1 (first page) → JobA1 (second page) → JobB1 (second page) → JobA1 (third page) → JobB1 (third page) in this order. Get RIP end notification. Thereafter, the job control unit 55 acquires RIP end notifications for JobA2 (first page and second page) and JobA3 (first page to fourth page).

  The job control unit 55 determines that the rendering of JobA1 is completed when the RIP completion notification for JobA1 is acquired three times as compared with the number of pages of each print job in the job management list 65. The same applies to JobB1. Therefore, the job control unit 55 can detect the timing when rendering of each print job is completed. The job management list 65 also reveals the order in which print jobs are received.

  When the execution order setting unit 62 accepts the setting of job reception order, the job control unit 55 outputs print execution requests to the printer control unit 61 in the order of JobA1, JobA2, JobA3, and JobB1. When the setting of rendering end order is accepted, print execution requests are output to the printer control unit 61 in the order of JobA1, JobB1, JobA2, and JobA3.

[Operation procedure]
FIG. 16 is an example of a sequence diagram illustrating a procedure for the user to set the printing order. The user operates the DFE 32 to display a print order setting screen on the display 330.
S1: The UI control unit 54 receives a user operation and requests the job control unit 55 to set the current printing order.
S2: The job control unit 55 outputs the current print order setting to the UI control unit 54.
S3: The UI control unit 54 marks a radio button according to the current print order setting and displays a print order setting screen.
S4: The UI control unit 54 accepts the setting of the printing order by the user.
S5: The UI control unit 54 outputs a print order setting storage request to the job control unit 55.

FIG. 17 is an example of a sequence diagram illustrating an operation procedure of the printing system 200.
S1: The application 12 transmits a print job (JobA1 = JDF + PDL) to the DFE 32.
S2: The job receiving unit 51 outputs the print job (JobA1 = JDF + PDL) to the system control unit 52.
S3: The system control unit 52 outputs the print job to the job control unit 55. When the DFE 32 is set to store the print job in the job data storage unit 53, the system control unit 52 stores the print job in the job data storage unit 53.
S4: The job control unit 55 outputs a JDF and a JDF conversion request to the JDF analysis unit 56.
S5: The JDF analysis unit 56 analyzes the JDF, determines the manufacturer (RIP engine 59) of the application 12 that created the JDF, and creates a “job attribute within DFE” using the conversion table 63 corresponding to the RIP engine 59. .
S6: The JDF analysis unit 56 outputs “job attribute within DFE” to the JDF analysis unit 56.
S7: The job control unit 55 creates a “RIP Parameter List” using “Job Attributes in DFE” and PDL for each page.
S8: The job control unit 55 registers the reception order, job ID, and number of pages in the job management list 65.
S9: The instance creation unit 64 of the job control unit 55 creates the job control unit INS. Here, it is assumed that the A1 job control unit INS has been created. Thereafter, the A1 job control unit INS makes a RIP execution request independently of the other job control units INS. Since the A1 job control unit INS is not affected by other job control units INS, RIP execution requests can be made in parallel with each other. RIP execution requests to the RIP control unit 58 of each job control unit INS are sequentially executed without waiting for a response from the RIP control unit 58, and the RIP execution requests are processed in parallel. When the RIP execution request is issued, the job ID of the job management list 65 is output to the RIP control unit 58 together with the generated “RIP Parameter List”.
S10: First, the A1 job control unit INS outputs the job ID to the RIP control unit 58.
S11: The RIP control unit 58 sorts and stores the print job in each RIP standby queue.
S 12: The job control unit 55 outputs “RIP Parameter List” to the RIP control unit 58.
S13: The RIP control unit 58 initializes the RIP engine 59.

The following processing differs depending on whether the “RIP control mode” is “Page Mode” or “Sheet Mode”. First, the case of “Page Mode” will be described.
S14-1: The job control unit 55 makes a RIP execution request to the RIP control unit 58.
S15-1: The RIP control unit 58 outputs a RIP command instead of the job control unit 55. When the “RIP control mode” is “Page Mode”, the RIP control unit 58 outputs a RIP command in a sequence suitable for “Page Mode”.
S16-1: The RIP engine 59 performs rasterization.
S17-1: The RIP engine 59 stores raster data in the image storage unit 60.
S18-1: The RIP engine 59 outputs a RIP end notification to the RIP control unit 58.
S19-1: The RIP control unit 58 outputs a RIP end notification to the A1 job control unit INS.

Next, the case of “Sheet Mode” will be described.
S14-2: The job control unit 55 makes a RIP execution request to the RIP control unit 58.
S15-2: When the “RIP control mode” is “Sheet Mode”, the RIP control unit 58 outputs a RIP command in a sequence suitable for “Sheet Mode”.
S16-2: The RIP engine 59 performs rasterization.
S17-2: The RIP engine 59 stores raster data in the image storage unit 60.
S18-2: The RIP engine 59 outputs a RIP end notification to the RIP control unit 58.
S19-2: The RIP control unit 58 outputs a RIP end notification to the A1 job control unit INS.

Next, it is assumed that the application 12 has transmitted JobA2 to the DFE 32 as a print job.
S20: The application 12 transmits a print job (JobA2 = JDF + PDL) to the DFE 32.
S 21: The job receiving unit 51 outputs a print job (JobA 2 = JDF + PDL) to the system control unit 52.
S 22: The system control unit 52 outputs a print job to the job control unit 55. When the DFE 32 is set to store the print job in the job data storage unit 53, the system control unit 52 stores the print job in the job data storage unit 53.
S23: The job control unit 55 outputs a JDF and a JDF conversion request to the JDF analysis unit 56.
S24: The JDF analysis unit 56 analyzes the JDF, determines the manufacturer (RIP engine 59) of the application 12 that created the JDF, and creates a “job attribute within DFE” using the conversion table 63 corresponding to the RIP engine 59. .
S25: The JDF analysis unit 56 outputs “job attribute within DFE” to the JDF analysis unit 56.
S26: The job control unit 55 creates a “RIP Parameter List” using “Job Attributes in DFE” and PDL for each page.
S27: The job control unit 55 registers the reception order, job ID, and number of pages in the job management list 65.
S28: The instance creation unit 64 of the job control unit 55 creates the job control unit INS. Here, it is assumed that the A2 job control unit INS has been created. Thereafter, the A2 job control unit INS performs the processes of S10 to S19-2 performed by the A1 job control unit INS in parallel.

The same applies when the application 12 transmits JobA3 and JobB1 to the DFE as print jobs.
S29, S30: The instance creation unit 64 creates an A3 job control unit INS and a B1 job control unit INS. The A3 job control unit INS and the B1 job control unit INS also perform each process of S10 to S19-2.

S31: The A1 job control unit INS outputs, to the job control unit 55, a RIP end notification for each page together with the job ID.
S32: The RIP control unit 58 also retrieves JobA1 from the RIP queue of the company A when rendering of all pages is completed.
S33: The job control unit 55 determines whether or not rendering of all pages has been completed.
S34: The instance creation unit 64 of the job control unit 55 deletes the job control unit INS (A1 job control unit INS in the drawing) of the print job that has been finished when rendering of all pages is completed.

Thereafter, the job control unit 55 reads the setting of the print order, and determines whether the job reception order or rendering is finished.
S35: The job control unit 55 outputs “Finishing information” to the printer control unit 61 together with the print execution request. This timing may be before or after the creation of raster data.
S36: The printer control unit 61 confirms the raster data in the image storage unit 60 and prints by acquiring the print execution request.

  As described above, when the DFE 32 of this embodiment includes a plurality of RIP engines 59, the job control unit 55 is instantiated, and the RIP standby queue 66 is provided for each RIP engine. 59 can render in parallel. Therefore, efficient rendering is possible when a plurality of print jobs are continuously input.

  According to the first embodiment, since there are a plurality of RIP engines 59 and each RIP engine 59 can perform rendering in parallel and can be printed in the order in which rendering has been completed, printing can be performed efficiently. Is possible.

  However, as shown in FIG. 18A, there are cases where, for example, raster data created by a certain RIP engine (A company RIP engine in the figure) is continuously printed first. FIG. 18 is an example of a diagram illustrating rendering processing and printing timing of each RIP engine 59.

  In FIG. 18A, Company A RIP engine, Company B RIP engine, and Company C RIP engine render JobA1, JobB1, and JobC1 almost in parallel, and then Company A RIP engine renders JobA2. Yes. When the print order setting is the rendering end order, the printer control unit 61 prints in order of JobA1, JobB1, JobC1, and JobA2. However, when there is a relationship between JobA1 and JobA2, the user may want to print JobA2 after JobA1.

  On the other hand, if the raster data of the same RIP engine 59 is always set to be continuously printed, printing starts even though there is raster data that has been rendered as shown in FIG. Therefore, efficient printing becomes difficult. In FIG. 18B, since it takes time to render JobA2, rendering of JobB1 and JobC1 is finished, but the printer control unit 61 cannot print JobB1 and there is a waiting time.

  Thus, in this embodiment, a DFE that efficiently prints the same RIP engine 59 print job in succession will be described.

  For example, it may be determined whether or not the time at which JobA2 rendering ends is earlier than the time at which JobA1 printing ends. JobA1 and JobA2 can be efficiently printed by continuously printing the same RIP engine 59 print jobs only when JobA2 rendering finishes earlier than JobA1 printing finishes.

  Further, as shown in FIG. 18B, even if the time when JobA2 rendering ends is not earlier than the time when JobA1 printing ends, JobA1 and JobA2 may be forcibly printed continuously.

  Although the functional block diagram of the DFE of this embodiment may be the same as that shown in FIG. 6, the job control unit 55 has the following functions. That is, when a plurality of print jobs are stored in the same RIP standby queue 66, when “the time when rendering of the next print job is completed” is earlier than “the time when printing of the previous print job is completed”, Print jobs of the same RIP engine 59 are continuously printed.

  The “time when printing of the immediately preceding print job is completed” is obtained by multiplying the number of printed sheets (number of pages × number of copies) by the printing time per sheet. The “time when rendering of the next print job ends” is obtained by multiplying the number of pages of the print job by a rendering time per page (for example, an average value is obtained in advance).

  FIG. 19 is a diagram illustrating an example of an execution order setting screen displayed on the display. In FIG. 19, radio buttons 503 and 504 are added as compared to FIG. The radio button 503 displays a message “print the same RIP engine print jobs continuously as much as possible”. The radio button 504 displays a message “Forcibly print the same RIP engine print jobs continuously”.

  When the user selects the “rendering end order” radio button 502, the radio buttons 503 and 504 can be selected. Therefore, when the user selects the radio button 503, the same RIP engine 59 print job can be continuously printed while efficiently printing. When the user selects the radio button 504, the same RIP engine 59 print job can be continuously printed even when a waiting time occurs.

  FIG. 20 is an example of a flowchart illustrating a procedure by which the job control unit 55 controls the printing order. FIG. 20 is executed in a state where “print the same RIP engine print jobs continuously as much as possible” is selected on the execution order setting screen and a plurality of print jobs are stored in the RIP standby queue 66. The

  The job control unit 55 determines whether or not a plurality of print jobs are registered in one RIP standby queue 66 (S10). If a plurality of print jobs are not registered in one RIP standby queue 66, the process ends.

  When a plurality of print jobs are registered in one RIP standby queue 66 (Yes in S10), the job control unit 55 sets the time when the rendering of the next print job is finished and the time when printing of the immediately preceding print job is finished. It is determined whether it is earlier (S20).

  If the determination in step S20 is Yes, the job control unit 55 prints the next print job following the previous print job even if the other RIP engine 59 finishes rendering (S30). Thereby, the print job of the same RIP engine 59 can be continuously printed without causing the printer control unit 61 to wait.

  When the determination in step S20 is No, the job control unit 55 determines whether or not “force continuous printing of print jobs of the same RIP engine” is selected (S40).

  If the determination in step S40 is Yes, the job control unit 55 performs the process in step S30. Therefore, it is possible to continuously print the print jobs of the same RIP engine 59 by making the printer control unit 61 stand by.

  If the determination in step S40 is No, the job control unit 55 prints the print job of another RIP engine that has been rendered (S50). Thereby, it is possible to print in the order in which rendering is completed.

  As described above, the DFE 32 of the present embodiment can continuously print the same RIP engine 59 print jobs while efficiently printing in the order in which rendering is completed.

  In this embodiment, a DFE 32 that can delete a print job from the RIP standby queue 66 will be described.

  The DFE 32 has a mechanism called pre-RIP. Pre-RIP is processing in which the JDF analysis unit 56 outputs a PDL command to the RIP control unit (or RIP engine 59) 58 without actual rendering and acquires attribute information (attributes and attribute values) (RIP The attribute information returned by the control unit 58 is an example of print setting information in the scope of claims).

  The attribute information returned by pre-RIP with respect to the PDL command is the same as the attribute information of the PDL command when the RIP engine 59 supports PDL.

  In this embodiment, the RIP control unit 58 performs pre-RIP, so that it can be determined whether or not the RIP engine 59 supports PDL commands.

An example of pre-RIP will be described using the PDL command “%% A_CropMark: Center” as an example. The attributes and attribute information of “%% A_CropMark: Center” are as follows.
Attribute ... A_CropMark
Attribute value… Center
The RIP engine 59 returns attribute information (attribute and attribute value) in response to the PDL command.
Attribute ... Center crop mark attribute value ... ON
Is returned.

  Therefore, in this example, the attribute information of the pre-RIP command is different from the attribute information returned by the pre-RIP, and it can be estimated that the print job does not correspond to the RIP engine 59, and the user's intended finish may not be achieved. There is.

  Conventionally, after performing pre-RIP, the job control unit 55 stores the print job in the RIP standby queue 66, but when the RIP control unit 58 has a plurality of RIP standby queues 66 as in the present embodiment, It becomes possible to pre-RIP the print job stored in the RIP standby queue 66.

  In addition, since there are a plurality of RIP engines 59 and RIP standby queues 66, pre-RIP can be performed in parallel. Therefore, an increase in time due to pre-RIP can be suppressed, and print jobs whose finish cannot be expected by pre-RIP can be deleted.

  FIG. 21 is an example of a diagram schematically showing pre-RIP performed for a print job in the RIP standby queue 66. The RIP control unit 58 performs pre-RIP on JobA1, JobA2, and JobA3 in the Acompany RIP standby queue 66a using the Acompany RIP engine. Further, the RIP control unit 58 performs pre-RIP on JobB1 of the B company RIP standby queue 66b using the RIP engine for B company.

  Unlike the prior art, the B company RIP engine and the A company RIP engine can perform pre-RIP in parallel.

  For example, when there is a possibility that JobA2 does not support the A company RIP engine, the job control unit 55 deletes JobA2 from the A company RIP standby queue 66a. By deleting, the DFE 32 can suppress unnecessary printing.

  Therefore, according to the present embodiment, pre-RIP can be performed in parallel by utilizing the plurality of RIP engines 59 and RIP standby queues 66, and unnecessary printing can be suppressed according to the result of pre-RIP. it can.

  In this embodiment, a DFE 32 in which a plurality of RIP engines 59 of the same type are mounted will be described. For example, when there are a plurality of RIP engines of Company A, a plurality of RIP engines of Company A can render in parallel, so that when a print job created by the same application 12 is input in a short time, the rendering time Can be shortened compared to the first embodiment.

  FIG. 22 is a diagram illustrating an example of the RIP unit 57 in which a plurality of RIP engines 59 of the same type are mounted. The RIP unit 57 has two A company RIP engines, two B company RIP engines, and two C company RIP engines. Each company may have three or more RIP engines. When the RIP engine 59 is not created by hardware such as an LSI, a plurality of RIP engines 59 may be prepared while suppressing an increase in cost.

  Further, the RIP control unit 58 has not only the RIP standby queue 66 for each company but also one RIP standby queue 66 for one RIP engine 59. That is, one A company RIP standby queue 66a-1 and 66a-2 for one A company RIP engine, one B company RIP standby queue 66b-1 and 66b-2 for one B company RIP engine, and one C company The RIP engine has one C company RIP standby queue 66c-1 and 66c-2. By having the RIP standby queue 66 in this way, the process of searching for a print job corresponding to the RIP engine 59 from the RIP standby queue 66 can be omitted.

  The RIP control unit 58 determines for which RIP engine the print job output from the job control unit 55 is created, and assigns the print job to the one having a smaller number of stored print jobs among the plurality of RIP standby queues. Store. This makes it possible to equalize print jobs stored in one RIP standby queue. Also, by equalizing, it is possible to increase the chances that the RIP engines 59 corresponding to the same application 12 render in parallel.

  Note that the instantiated job control unit INS only has to output “RIP Parameter List” independently, as in the first embodiment, etc., so even if there are multiple RIP engines 59 of the same type, the operation is changed. There is no.

  Therefore, according to the DFE 32 of the present embodiment, it is possible to render more efficiently than the first embodiment by having a plurality of the same RIP engines 59.

[Preferred modification]
The best mode for carrying out the present invention has been described above with reference to the embodiments. However, the present invention is not limited to these embodiments, and various modifications can be made without departing from the scope of the present invention. And substitutions can be added.

  For example, although the DFE 32 has all the functions in FIG. 5, these functions may be arranged in separate devices that can communicate with each other via the network 3. For example, each company's RIP engine 59 and JDF analysis unit 56 need only exist on a network accessible by the DFE 32.

  The same applies to the image storage unit 60 and the job data storage unit 53 as long as they exist on a network accessible by the DFE 32.

  The execution order may be set in the DFE 32 from the client PC via the network, for example. In this case, the DFE transmits a Web page or the like as a server to the client PC, and accepts an execution order setting.

1 End user environment 2 POD printing system environment 11 Client PC
12 Application 20 Process Management Department 30 Digital Printing Department 31 Printer 32 DFE
51 Job Reception Unit 52 System Control Unit 53 Job Data Storage Unit 54 UI Control Unit 55 Job Control Unit 56 JDF Analysis Unit 57 RIP Unit 58 RIP Control Unit 59 RIP Engine 60 Image Storage Unit 61 Printer Control Unit 62 Execution Order Setting Unit 63 Conversion Table 64 Instance creation section 65 Job management list

JP 2012-238188 A

Claims (13)

An information processing apparatus that creates drawing data using a print job including print data and setting information,
Conversion means for converting the setting information into apparatus setting information for each drawing data creation means;
Drawing data creation requesting means for outputting a drawing data creation request to the drawing data creation control means using the print data and the apparatus setting information;
The drawing data creation control means for storing a print job requested to create drawing data from the drawing data creation request means in a storage means associated with each of the plurality of drawing data creation means;
A plurality of drawing data creation means for obtaining a print job stored in the storage means from the drawing data creation control means and creating drawing data;
An information processing apparatus comprising: A plurality of drawing data creation requesting means;
Each drawing data creation request means outputs a drawing data creation request to the drawing data creation control means independently of the other drawing data creation request means.
The information processing apparatus according to claim 1. Having a creation request means generating means for generating the drawing data creation request means dedicated to the print job when there is a request to create the drawing data of the print job from outside;
The information processing apparatus according to claim 1 or 2. Printing device control means for causing the printing device to print drawing data;
Print job recording means for recording the number of pages when a print job drawing data creation request is received from the outside,
The drawing data creation request unit obtains a creation end notification for each page of the print job by outputting a creation request to the drawing data creation control unit, and when the creation end notification of the number of recorded pages is acquired, Determine that drawing data for one print job has been created,
Causing the printing apparatus control means to start printing drawing data;
The information processing apparatus according to any one of claims 1 to 3. Printing device control means for causing the printing device to print drawing data;
Print job recording means for recording the reception order of print jobs when there is an external request for creating print job drawing data;
The drawing data creation request unit obtains a print job creation end notification by outputting a creation request to the drawing data creation control unit, determines that drawing data of one print job has been created,
Causing the printing apparatus control means to start printing of drawing data in the order of reception of print jobs;
The information processing apparatus according to any one of claims 1 to 3. Setting whether the printing apparatus control means starts printing drawing data in order from the print job in which the drawing data is created, or whether the printing apparatus control means starts printing drawing data in the order in which the print job is received Having a print order setting accepting means for accepting
The information processing apparatus according to claim 4 or 5, The print order setting accepting unit accepts a setting for starting printing of drawing data in order from a print job in which drawing data is created, and further accepts a setting for continuously printing the same print job of the drawing data creating unit. If
When the creation of drawing data for the second print job in which the same drawing data creation means creates the drawing data after the first print job is completed before the printing of the first print job is completed, Even when the drawing data creation means finishes creating the drawing data,
The drawing data creation requesting unit causes the printing apparatus control unit to print drawing data of a second print job following printing of the first print job.
The information processing apparatus according to claim 6. The print order setting accepting unit accepts a setting to start printing the drawing data in order from the print job in which the drawing data is created, and further forcibly prints the same print job of the drawing data creating unit continuously. If you accept the settings,
Even when the creation of the drawing data of the second print job in which the same drawing data creation means creates the drawing data after the first print job is not completed before the printing of the first print job is completed,
The drawing data creation requesting unit causes the printing apparatus control unit to print drawing data of a second print job following printing of the first print job.
The information processing apparatus according to claim 7. The drawing data creation control means analyzes the print job output from the drawing data creation request means, determines the drawing data creation means for creating drawing data from the print job, and determines the determined drawing data creation means Storing a print job in the associated storage means;
Causing the drawing data creation means to create drawing data in order from a print job stored in the storage means for a long time;
The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. The drawing data creation means returns print setting information designated by the description when the description of the predetermined unit of the print data is acquired;
The drawing data creation control unit obtains the print setting information by outputting the description of the predetermined unit of the print job stored in the storage unit to the drawing data creation unit, and acquires the print setting information and the description. Delete the print job from the storage means when
The information processing apparatus according to claim 1. A plurality of the same drawing data creating means;
The storage means provided for each drawing data creation means,
The drawing data creation control means determines the drawing data creation means for creating drawing data by analyzing a print job for which drawing data is requested to be created by the drawing data creation request means,
When there are a plurality of the determined drawing data creation means, a print job is allocated and stored in the storage means that stores few print jobs among the storage means associated with the drawing data creation means. The information processing apparatus according to claim 9, wherein: An information processing method for creating drawing data using a print job including print data and setting information,
Converting means for converting the setting information into apparatus setting information for each drawing data creating means;
A drawing data creation request means for outputting a drawing data creation request to the drawing data creation control means using the print data and the apparatus setting information;
The drawing data creation control means storing the print job requested to create the drawing data from the drawing data creation request means in a storage means associated with each of the plurality of drawing data creation means;
A plurality of drawing data creation means for obtaining a print job stored in the storage means from the drawing data creation control means and creating drawing data;
An information processing method characterized by comprising: In an information processing apparatus that creates drawing data using a print job including print data and setting information,
A conversion step of converting the setting information into apparatus setting information for each drawing data creation means;
A drawing data creation request step for outputting a drawing data creation request to the drawing data creation control means using the print data and the apparatus setting information;
A step of causing the drawing data creation control means to store the print job requested to create the drawing data in the drawing data creation request step in a storage means associated with each of the plurality of drawing data creation means;
Acquiring a print job stored in the storage means from the drawing data creation control means and causing each of a plurality of drawing data creation means to create drawing data;
A program that executes

Images