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

Description

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

  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 described below) and printing devices to describe print job settings and the like in the main printing process in a common description format. 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. However, JDF enables cooperation between printing devices, printing process management, and the like regardless of differences between manufacturers of workflow applications and printing devices.

  However, when a workflow application created by each software manufacturer extends JDF, the JDF may include a description unique to the workflow application. In this case, a situation may arise in which the workflow application or the printing device in the downstream process cannot analyze and process the JDF.

  As a method for solving such inconvenience, it is conceivable that the workflow application or printing device in the downstream process converts the JDF created by the upstream workflow application into a format that can be handled by itself (for example, see Patent Document 2). ). In Patent Document 2, when print instruction information described in JDF code is transmitted from a PC (Personal Computer) to a printing apparatus, the printing apparatus generates the print instruction information from the received print instruction information. A printing method is disclosed in which an application name of an application program is acquired and transmitted to a server, and JDF analysis data corresponding to the application name is transmitted to a printing apparatus.

  However, even if the JDF created by the upstream workflow application is converted into a format that can be handled by itself, the output result may differ. That is, the JDF is transmitted as a print job together with PDL (Page Description Language) from the upstream workflow application to the downstream workflow application or printing device. Here, even if the format of the print job (JDF + PDL) is the same among the companies, there is a problem that the output result may change due to the difference in the rendering engine of the printing device of each company.

  In view of the above problems, an object of the present invention is to provide an information processing apparatus that reduces differences in output results due to differences in rendering engines of different companies.

  In view of the above problems, the present invention is an information processing apparatus capable of communicating with a plurality of drawing data creating means for creating drawing data used for image formation in a printing apparatus, wherein the drawing data creating means creates the drawing data. An acquisition unit for acquiring print setting information and print data used in the processing, a conversion unit for converting the setting information into device setting information in a format handled by the information processing device, and analyzing information included in the device setting information. And a creation means control means for selecting the drawing data creation means and outputting the apparatus setting information and the print data to the drawing data creation means in a manner corresponding to the selected drawing data creation means. Features.

  The present invention can provide an information processing apparatus that reduces differences in output results due to differences in rendering engines of different companies.

1 is an example of an overall configuration diagram of a printing system according to an embodiment. It is an example of the hardware block diagram of DFE. It is an example of the functional block diagram of the conventional DFE shown for the comparison. It is an example of the functional block diagram of DFE of this embodiment. 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”. FIG. 10 is an example of a diagram for schematically explaining an example of “job attributes within DFE”; It is a figure which shows an example of "RIP Parameter List." It is a figure which shows an example of "RIP Parameter List." It is an example of the sequence diagram which shows the operation | movement procedure of DFE. FIG. 10 is an example of a flowchart showing a more detailed operation procedure centering on a RIP control unit when the RIP engine supports a page processing sequence. FIG. 10 is an example of a flowchart illustrating a more detailed operation procedure centering on a RIP control unit when the RIP engine does not support a page processing sequence.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.
FIG. 1 shows an example of an overall configuration diagram of a printing system 200 according to the present embodiment. The printing system 200 according to this 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 (Job Definition Format) and PDL (Page Description Language)) from the end user environment 1 and stores the print job. JDF is an example of claims setting information, and PDL is an example of claims print data. 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, and 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. In the digital printing unit 30, a DFE (Digital Front End) 32 is arranged. The DFE 32 is also called a printer control device, and controls printing by the printer 31. 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 instruct image editing, imposition, text insertion, post-processing, and the like. In addition, a print job is transmitted to the process management unit 20 of the POD printing system environment 2.

  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 the present 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. For this reason, the process management unit 20 or the DFE 32 has a print job conversion function of the present embodiment, a plurality of RIP engines described later, and the like. However, for example, the end user environment 1 may have a function for converting a print job and a RIP engine. In addition to these, for example, an information processing apparatus connected to the network 3 may have a function of converting a print job and a plurality of RIP engines. Hereinafter, in this embodiment, the DFE 32 will be described as having a function of converting a print job and a plurality of RIP engines.

  FIG. 2 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 the server via the network 3.

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

[Function block diagram]
FIG. 3 shows an example of a functional block diagram of a conventional DFE 32 shown for comparison. The DFE 32 performs job control, RIP (Raster Image Processor) control, and printer control in the 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. The “DFE job attribute” is an example of device setting information in the claims, and the “RIP Parameter List” is an example of control data in the claims.

  Note that “RIP” is an abbreviation for “Raster Image Processor”, and refers to creating (rendering) a dedicated IC or 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 corresponds to the application 12 of company C, and can print normally if it is a print job in the format of company C (JDF and PDL). Hereinafter, the procedure until printing will be described.
1. The job receiving unit 51 receives a print job (PDL + JDF) in company C format from the application 12 of company C operating in the end user environment 1.
2. The job receiving unit 51 outputs a print job to the system control unit 52.
3. The system control unit 52 once outputs the print job to the job control unit 55 after holding the print job in the job data storage unit 53 according to the setting.
4). The job control unit 55 transmits the JDF in the print job to the JDF analysis unit 56 and outputs a JDF conversion request to the JDF analysis unit 56.
5. The JDF analysis unit 56 converts the CDF format JDF into “job attributes within DFE” that can be handled by the DFE 32. The “job attributes within DFE” will be described later. For example, each attribute of a print job is converted into a format handled by the DFE 32 of company C.
6). The JDF analysis unit 56 transmits the converted “job attributes within DFE” to the job control unit 55.
7). The job control unit 55 generates a “RIP Parameter List” from the “job attributes within DFE” and “PDL”. 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 an RIP processing instruction to the RIP engine 59 from the information of the “RIP Parameter List”. This instruction is called a RIP command.
8). The job control unit 55 initializes the RIP engine 59, determines a RIP command using information necessary for the RIP processing described in the “RIP Parameter List”, and outputs the RIP command to the RIP engine 59.
9. The RIP engine 59 executes drawing processing according to the RIP command. Through the rendering process, raster data (bitmap data) matching the output resolution of the printer 31 is created.
10. After the drawing process ends, the RIP engine 59 stores raster data in the image storage unit 60 and notifies the job control unit 55 of a RIP end notification.
11. The job control unit 55 transmits the finishing information in the “job attributes within DFE” to the printer control unit 61 and makes a print execution request.
12 The printer control unit 61 receives a print execution request from the job control unit 55, confirms the image stored in the image storage unit 60, and then controls the printer 31 according to the Finishing information to execute printing.

  (A1) As described above, if the DFE 32 is a JDF in company C format, the JDF can be analyzed. Therefore, the JDF can be converted into “job attributes within DFE” and rasterized by the RIP engine 59. However, in the case of JDF other than the company C format, the JDF analysis unit 56 may not be able to analyze appropriately.

  (A2) Even if it becomes possible to analyze JDF other than company C, depending on the workflow applications of other companies, there are cases where there is a difference between not only JDF but also a print job including JDF and PDL from company C. In this case, the DFE 32 may not be able to print normally.

  (A3) Even if it corresponds to the difference in the print job, the output result may differ due to the difference in the RIP engine 59 regardless of the PDL type (for example, PDF, PostScript, etc.) in the print job. .

  (A4) For example, even if each company's RIP engine 59 can be installed to eliminate the difference in output results, each company's RIP engine 59 generally has a different control sequence, and each company's RIP engine 59 is simply installed. It is not possible to reduce the difference in output results simply by doing.

[DFE of this embodiment]
FIG. 4 shows an example of a functional block diagram of the DFE 32 of the present embodiment. The DFE 32 according to the present embodiment operates as follows as a main characteristic part in order to eliminate the above-described inconvenience.

  (B1) The JDF conversion unit 63 of the JDF analysis unit 56 converts JDF of each company format into “job attributes within DFE” that can be handled by the DFE 32 of company C. Thereby, (a1) can be solved.

In addition, at the time of conversion to “job attribute in DFE”, “RIP control mode” is set in “job attribute in DFE”. Specifically, either “Page Mode” or “Sheet Mode” is set as the “RIP control mode”.
“Page Mode”: RIP processing is instructed for each page to create raster data that is consolidated into one sheet. “Sheet Mode”: For each part (cell to be described later) of one page in which a plurality of pages are already aggregated. RIP processing is instructed to create raster data (b2) In addition, a new RIP control unit 58 is provided in the RIP unit 57. The RIP control unit 58 controls the RIP engine 59 in accordance with the “RIP control mode”. Therefore, the optimum sequence for the print job is selected by the “RIP control mode”. Thereby, (a2) can be solved.

  (B3) In addition, RIP engines 59 are arranged in the RIP unit 57 for each software manufacturer of the application (for each RIP engine identification information described later). As a result, it is possible to avoid the inconvenience that the output result changes due to the difference between the RIP engines 59 of the respective companies even if the PDLs in the print job having the same print job format (a3) are the same PDL type.

  (B4) The RIP control unit 58 determines the RIP engine 59 to be used from among the plurality of RIP engines 59, and controls the RIP engine 59 in accordance with the sequences of the RIP engines held in advance. Thereby, (a4) can be solved.

  Hereinafter, a description will be given based on FIG. 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 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. For example, JDF and PDL are extracted from the received data and output to the job control unit 55. Further, for example, as a log, a unique job number, reception date / time, end date / time, status, and the like are recorded in association with the job. In addition to being input from the application 12, the print job may be input by the job receiving unit 51 reading out the print job stored in the portable memory. In this embodiment, it is assumed that JDF is included in the print job. However, if JDF is not included, the job receiving unit 51 creates a dummy JDF and is necessary for job processing in the DFE. Define print job settings.

  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, the system control unit 52 sends the print job stored in the job data storage unit 53 to the job control unit 55. Output. Further, for example, when the print time is set in the JDF, the print job stored in the job data storage unit 53 is read out and 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 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 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 changes the JDF in the C company format to the “job attribute in DFE” of the C company as before. Further, the JDF conversion unit 63 of the JDF analysis unit 56 analyzes the description of the JDF, and determines the software manufacturer of the application 12 that created the JDF (which is an example of a creation source of claims). Determining the manufacturer of the application that created the JDF has almost the same meaning as determining the RIP engine 59 that is supposed to render the print job. Then, the JDF conversion unit 63 uses the conversion table 62 created based on the correspondence between the JDF in the format of each company and the “job attribute in DFE” of the C company, to convert the JDF that depends on the software manufacturer of the application 12. Change to “Job attribute in DFE” of company C. The conversion table 62 is created for each software manufacturer.

  Further, the JDF conversion unit 63 sets “RIP control mode (“ Page Mode ”or“ Sheet Mode ”)” in “Job attribute in DFE”. That is, it is determined that the JDF is in the format of Company A or Company B other than Company C, and the “RIP control mode” suitable for the print job created by the software manufacturer of the application 12 is set. Whether each company's print job is created in “Page Mode” or “Sheet Mode” is investigated in advance. In the present embodiment, it is assumed that the company C handles the print job consolidated printing setting in “Page Mode”.

  Further, the JDF conversion unit 63 may set “RIP engine identification information” in “job attribute within DFE”. That is, it is determined that the JDF is in the form of company A or company B other than company C, and appropriate “RIP engine identification information” corresponding to each company is set.

  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. The job control unit 55 causes the RIP control unit 58 to perform drawing processing using the RIP engine 59. That is, the job control unit 55 may create a “RIP Parameter List” from the “job attributes within DFE” and the PDL as in the case where the RIP control unit 58 is not provided. The “RIP Parameter List” includes “RIP control mode”.

  Further, the job control unit 55 always operates according to a sequence according to “Page Mode”. Since the job control unit 55 always operates in its own control mode, it does not need to be changed to cope with print jobs (JDF and PDL) of other companies. Since the job control unit 55 performs a main function in the execution of the print job, the development cost and the period can be reduced by avoiding the change to cope with the print job of another company.

  The RIP unit 57 includes a RIP control unit 58 and a RIP engine 59, and creates raster data using them. The RIP engine 59 is prepared for each application software manufacturer. Even if the software manufacturers are different, the same RIP engine 59 can be used if the software manufacturer uses the same RIP engine 59 as the other manufacturers. Although there are three RIP engines 59 in the figure, there may be two or more RIP engines 59, and there may be four or more.

  The RIP control unit 58 analyzes information of the “RIP Parameter List” and determines a RIP engine to be used from a plurality of RIP engines 59. The determination of the RIP engine may be based on one or more items in the “RIP Parameter List” or may be based on “RIP engine identification information” specified in the “RIP Parameter List”.

  The RIP control unit 58 internally holds a control sequence for each of a plurality of RIP engines 59. Therefore, the job control unit 55 may output a “RIP Parameter List” to the RIP control unit 58 regardless of the RIP engine 59 used.

  Also, the RIP control unit 58 refers to the “RIP Parameter List” and transmits a RIP command to the RIP engine 59. 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, the difference between print jobs can be absorbed.

  The RIP engine 59 is a rendering engine, and creates raster data by performing rasterization according to the RIP command. As described above, there are a plurality of RIP engines 59 corresponding to application software manufacturers.

  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.

  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. Further, finishing processing is performed based on the finishing information acquired from the job control unit 55.

[About other company information in 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. 5 is an example of a diagram for explaining a part of the description of JDF. In FIG. 5A, the instruction content for the print job is 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 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 the reference in ResourceLinkPool, and specifies the attribute reference and information related to the output product.
“Amount” specifies the number of copies.
“Rotate” specifies the rotation angle of the image.

  For example, if the JDF in FIG. 5A is created by the application 12 of company C, the DFE 32 of company C can correctly analyze the JDF. On the other hand, as shown in FIGS. 5B and 5C, the company of the application 12 may extend JDF.

  FIG. 5B shows an example of the extension of company A, and FIG. 5C shows an example of the extension of company B. “Xmlns: A =“ www.aaa.com/schema/aaa ”” in FIG. 5B 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. 5C means that all tags starting with “B:” in the JDF become expansion tags for company B.

Therefore, the JDF conversion unit 63 can determine the software manufacturer of the application 12 that created the JDF by referring to these descriptions in the JDF. Depending on the software manufacturer of the application 12, the JDF can be converted into “job attributes within DFE” that can be handled by the DFE 32 of company C using the conversion table 62 described later.
[Create job attributes in DFE]
Creation of “job attributes within DFE” will be described with reference to FIGS. FIG. 6 is an example of a conversion table 62, and FIG. 7 is an example of a diagram for explaining creation of “job attributes within DFE”. The JDF analysis unit 56 converts JDF in company C format into “job attributes within DFE” as in the conventional case. For example, the conversion method refers to the conversion table 62 that associates the attribute in the JDF tag with the item “job attribute in DFE”, and arranges the attribute value of JDF as the item value of “job attribute in DFE”. It is. The conversion table 62 in FIG. 7 is the conversion table in FIG. 6, and FIG. 6 (a) and FIG. 7 (a), FIG. 6 (b), FIG. 7 (b), FIG. FIG. 7C corresponds to each.

  FIG. 6A shows an example of a conversion table for company C. In the conversion table of company C, the value of the attribute name “Amount” corresponds to the item value of the item name “number of copies”, and the value of the attribute name “Rotate” corresponds to the item value of the item name “rotate”. .

  When the JDF conversion unit 63 determines the software manufacturer that created the print job as described above (that is, the RIP engine that is supposed to process the print job), the JDF conversion unit 63 uses the conversion table 62 corresponding to each software manufacturer. JDF is converted to “job attributes within DFE”.

  The JDF conversion unit 63 holds a conversion table 62 for company A and a conversion table 62 for company B in advance. 6B shows a conversion table for company A, and FIG. 6C shows a conversion table for company B. The JDF conversion unit 63 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 62 corresponding to each manufacturer.

  Company A and company B format JDFs can be converted in the same manner as the company C format JDF. The conversion table of company A associates the value of the attribute name “A: Amount” with the item value of the item name “number of copies”, and sets the value of the attribute name “A: Rotate” to the item name of the item name “rotation”. Corresponds to the value. The conversion table of company B associates the value of the attribute name “B: DeliveryAmount” with the item value of the item name “Copies” and sets the value of the attribute name “B: Rotate” to the item name “Rotation”. Corresponds to the value. In the conversion table of company B, rotation is valid only when the value of the attribute name “B: AlternateRotation” is “false”. Therefore, if it is determined that the JDF is in the A company or B company format, the “job attribute in DFE” can be created in the same manner as the JDF in the C company format.

  When the JDF conversion unit 63 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 product or an application of the same company as that of 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”.

  Note that the “RIP control mode” is not created by the application 12 of a company different from the company (C company) in the print job format in aggregate printing, but is created by the application 12 and actually in the JDF. This may be set when aggregated printing of two or more pages is set.

As described above, when the JDF conversion unit 63 creates the “job attributes within DFE”,
Tags starting with "xmlns: A =" www.aaa.com/schema/aaa "" or "xmlns: B =" www.bbb.com/schema/bbb "" or "A:" A: Amount ”, A: Rotate”) and tags beginning with “B:” (“B: DeliveryAmount”, B: Rotate ”) and the like are also included in the“ job attributes within DFE ”. Or it can be converted to be included. These pieces of information can be included in the “RIP Parameter List”. Thereby, the RIP control unit 58 can detect these descriptions from the “RIP Parameter List” and select one RIP engine 59.

  Further, the JDF conversion unit 63 may directly set “RIP engine identification information” as “job attribute in DFE” as in “RIP control mode”. In this case, for example, company names A company, B company, and C company are set, and IDs (identification information) unique to A company, B company, and C company are set. The unique ID (identification information) is an example of designation information.

FIG. 8A is an example of a diagram schematically 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.
-“Number of copies” of the job information specifies the number of copies of the print job.
The “number of pages” of the job information specifies the number of pages included in the print job.
The “RIP control mode” of the job information specifies the control mode of the RIP engine by the RIP control unit 58.
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.

  “Page Mode” or “Sheet Mode” is set in “RIP Control Mode” of “Job Attributes within DFE”. In the figure, “RIP control mode” is set as one item of “job attributes within DFE”, but may be set in a form attached to “job attributes within DFE”.

  FIG. 8B is an example of a diagram for schematically explaining another example of “job attributes within DFE”. In FIG. 8B, apart from the “RIP control mode”, “RIP engine identification information” for identifying a plurality of RIP engines 59 is set.

  When there is only one software manufacturer whose “RIP control mode” is “Sheet Mode”, the information identifying the RIP engine (software manufacturer) is that “Sheet Mode” is set as the “RIP control mode”. It becomes.

[About RIP Parameter List]
The “RIP Parameter List” is created from “Job Attributes within DFE” and PDL. As described above, the “job attributes within DFE” is information that can be handled by the DFE 32 of company C. That is, it is described in a terminology and format that can be analyzed by the job control unit 55 to create a “RIP Parameter List”. The “RIP Parameter List” includes an item “RIP control mode”, but the “RIP control mode” is only one item of “job attributes within DFE”. The same applies when “RIP engine identification information” is included.

  For this reason, even if “RIP control mode” or “RIP engine identification information” is included, it may be transferred from “job attribute in DFE” to “RIP Parameter List” in the same manner as other items. That is, the “RIP Parameter List” is the same regardless of whether the “RIP control mode” is set or not and “RIP engine identification information” is present. Therefore, for example, even if compared with the conventional job control unit 55 of FIG. 3, the function of the job control unit 55 is not changed at least, or at least not greatly changed.

FIG. 9 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 file and image data such as JPEG are specified.
-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 type of the output image. 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 rendering (rasterization).
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.

  Note that the “RIP control mode” is not limited to the location illustrated in FIG. 9, and may be set at another location in the “RIP Parameter List”. Further, even if the notation “RIP control mode” disappears, it is only necessary to be included as information.

  FIG. 10 is a diagram illustrating another example of the “RIP Parameter List”. In FIG. 10, “RIP engine identification information” is set after “RIP control mode” (in this case, a company name, etc.). As a result, the RIP control unit 58 reads “xmlns: A =“ www.aaa.com/schema/aaa ”” or “xmlns: B =“ www.bbb.com/schema/bbb ”” from the “RIP Parameter List” ( Alternatively, the RIP engine 59 can be selected simply by referring to a specific item (“RIP engine identification information”) without detecting “A: Amount”, “B: DeliveryAmount”, or the like.

[Control procedure]
FIG. 11 is an example of a sequence diagram illustrating an operation procedure of DFE.
S1: The application 12 transmits a print job (JDF + PDL) to the job receiving unit 51.
S2: The job receiver 51 outputs a print job to the system controller 52.

Either of the processes of steps S3-1 and S3-2 is performed.
S3-1: If the setting of the DFE 32 is to store the print job in the job data storage unit or the setting to store the print job in the job data storage unit is included in the JDF, the system control unit 52 The print job is stored in the job data storage unit.
S3-2: If there is no setting for storing the print job in the job data storage unit, the system control unit 52 outputs the print job to the job control unit 55.
S4: The job control unit 55 outputs the JDF of the print job to the JDF analysis unit 56 and also outputs a JDF conversion request to the JDF analysis unit 56.
S5: The JDF analysis unit 56 converts the JDF in the format of each company into “job attributes within DFE” that can be processed by the DFE 32 of company C. At the time of conversion, the JDF analysis unit 56 sets “RIP control mode (“ Page Mode ”or“ Sheet Mode ”)” in “Job attribute within DFE”. The “RIP control mode” may be set before, during, or after creation of “job attributes within DFE”.
S6: The JDF analysis unit 56 outputs “job attributes within DFE” to the job control unit 55.
S7: The job control unit 55 creates a “RIP Parameter List” from the “job attributes within DFE” and “PDL”.
S8: The job control unit 55 outputs “RIP Parameter List” to the RIP control unit 58.
S9: The RIP control unit 58 determines the RIP engine 59 to be used based on the “RIP Parameter List”.

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.
S10-1: The RIP control unit 58 initializes the determined RIP engine 59.
S11-1: The job control unit 55 makes a RIP execution request to the RIP control unit 58.
S12-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”.
S13-1: The RIP engine 59 performs rasterization.
S14-1: The RIP engine 59 stores raster data in the image storage unit 60.

Next, the case of “Sheet Mode” will be described.
S10-2: The RIP control unit 58 initializes the determined RIP engine 59.
S11-2: The job control unit 55 makes a RIP execution request to the RIP control unit 58.
S12-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”.
S13-2: The RIP engine 59 performs rasterization.
S14-2: The RIP engine 59 stores raster data in the image storage unit 60.

Therefore, if the RIP engine 59 can be determined by the “RIP Parameter List”, the RIP control unit 58 can control the RIP engine 59 according to “Page Mode” or “Sheet Mode”. The operation of the job control unit 55 is not different between “Page Mode” and “Sheet Mode”.
S15: The job control unit 55 outputs the finishing information together with the print execution request to the printer control unit 61. This timing may be before or after the creation of raster data.
S16: The printer control unit 61 confirms the raster data in the image storage unit 60 and prints by acquiring the print execution request.

  Note that the difference between “Page Mode” and “Sheet Mode”, which is an example of a difference between print jobs, is caused by a difference in JDF software manufacturers. For example, “RIP control mode” may be determined if the software manufacturer is determined, such as “Page Mode” for companies A and C, and “Sheet Mode” for company B. Therefore, the sequence of “Page Mode” and “Sheet Mode” may be switched according to the RIP engine 59 to be used instead of dividing the sequence by “Page Mode” and “Sheet Mode” as shown in FIG. That is, the difference between print jobs can be absorbed by selecting the RIP engine 59 and switching the sequence.

<Sequence differences due to differences in RIP engines>
Since the sequence differs depending on the RIP engine 59, an appropriate sequence is determined in advance for each RIP engine in the RIP control unit 58. For example, depending on the RIP engine 59, the page processing sequence may or may not be supported. The page processing sequence is a sequence for controlling rendering processing for one page on the RIP engine side. In the RIP engine 59 corresponding to the page processing sequence, if it is transmitted to the RIP engine 59 in units of pages, the RIP engine 59 autonomously renders one page.

FIG. 12 is an example of a flowchart showing a more detailed operation procedure centered on the RIP control unit 58 when the RIP engine 59 is compatible with the page processing sequence. This process replaces the process of S11-1 to S13-1 or S11-2 to S13-2 of FIG.
S1: The job control unit 55 outputs a job processing start request to the RIP control unit 58.
S2: The RIP control unit 58 outputs a job processing start instruction to the RIP engine 59.
S3: The RIP control unit 58 outputs a job processing start response to the job control unit 55.

The processes from S4 to S9 are repeated for each page by the number of pages.
S4: The job control unit 55 outputs a page processing start request to the RIP control unit 58.
S5: The RIP control unit 58 outputs a page processing start response to the job control unit 55.
S6: The RIP control unit 58 outputs page RIP data to the RIP engine 59.
S7: The RIP control unit 58 outputs a page RIP start instruction to the RIP engine 59.
S8: When the rendering of one page is completed, the RIP engine 59 outputs a page RIP completion notification to the RIP control unit 58.
S9: The RIP control unit 58 outputs a page processing completion notification to the job control unit 55.
S10: The RIP control unit 58 outputs a job processing completion notification to the job control unit 55.

FIG. 13 is an example of a flowchart showing a more detailed operation procedure centering on the RIP control unit 58 when the RIP engine 59 does not support the page processing sequence. This process replaces the process of S11-1 to S13-1 or S11-2 to S13-2 of FIG.
S1: The job control unit 55 outputs a job processing start request to the RIP control unit 58.
S2: The RIP control unit 58 outputs a job processing start instruction to the RIP engine 59.
S3: The RIP control unit 58 outputs a job processing start response to the job control unit 55.

The processing of S4 to S12 is repeated for each page by the number of pages.
S4: The job control unit 55 outputs a page processing start request to the RIP control unit 58.
S5: The RIP control unit 58 outputs a page processing start response to the job control unit 55.

Further, the processing of S6 to S11 is repeated for the number of RIP-completed image storage areas. The RIP-completed image storage area is an area for storing a RIP-completed image secured in the image storage unit 60 (the RIP-completed image storage area is an example of a rendering unit in the claims). When a sufficient area for storing an image for one page is secured, the number of repetitions is one. However, if the RIP-completed image storage area has only M size, for example, and the size of one page image is 5 × M, the image is repeated five times (= 5 × M / M).
S6: The RIP control unit 58 outputs a RIP preparation start instruction to the RIP engine 59.
S7: The RIP engine 59 outputs a RIP data request to the RIP control unit 58.
S8: The RIP control unit 58 transmits RIP data to the RIP engine 59. That is, since the RIP engine 59 does not support rendering for each page, the RIP control unit 58 transmits RIP data in response to a request from the RIP engine 59.
S9: The RIP engine 59 outputs a RIP preparation completion notification to the RIP control unit 58.
S10: The RIP control unit 58 outputs a RIP start instruction to the RIP engine 59.
S11: The RIP engine 59 outputs a RIP completion notification to the RIP control unit 58.
S12: When the processing of S6 to S11 is repeated by the number of RIP-completed image storage areas (when processing for one page is completed), the RIP control unit 58 outputs a page processing completion notification to the job control unit 55.
S13: When rendering of all pages is completed, the RIP control unit 58 outputs a job processing completion notification to the job control unit 55.

  As shown in FIGS. 12 and 13, the RIP control unit 58 switches the sequence according to the RIP engine 59, so that each RIP engine 59 can be appropriately controlled when the RIP engine 59 of each company is mounted on the DFE 32. . Therefore, by installing the RIP engines 59 of each company in the DFE 32, it is possible to reduce the occurrence of a difference in the output result due to the difference in the RIP engines 59.

  Even if the description format of JDE is different for each company, the JDF conversion unit 63 can determine the software manufacturer and convert it to “job attribute in DFE”. Further, even if the format of the print job is different for each company, the RIP control unit 58 can absorb it by switching the control procedure.

  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, in the upstream process of the DFE 32 of company C, the client PC 11 of the end user environment 1 executes the application, and the JDF conversion unit 63 determines the software manufacturer of the application. However, a printing device may exist in the upstream process of the DFE 32 of company C, and the printing device may execute an application.

  In the present embodiment, JDF is converted in the framework of a print workflow, but print settings that are not called JDF may be converted.

  In this embodiment, the software manufacturer of the application 12 is determined, but the software manufacturer may indicate the manufacturer of the printing device. In addition to the company that develops the application 12, the software manufacturer includes a company that contracts development from the company.

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
40 Postpress section 51 Job receiving section 52 System control section 53 Job data storage section 54 UI control section 56 JDF analysis section 55 Job control section 57 RIP section 58 RIP control section 59 RIP engine 60 Image storage section 61 Printer control section 62 Conversion table 63 JDF converter

JP 2012-238188 A JP 2013-089992 A

Claims (10)

An information processing apparatus capable of communicating with a plurality of drawing data creating means for creating drawing data used for image formation in a printing apparatus,
An acquisition means for acquiring print setting information and print data used by the drawing data creating means for creating the drawing data; a converting means for converting the setting information into apparatus setting information in a format handled by the information processing apparatus;
Analyzing the information contained in the apparatus setting information, selecting the drawing data creation means, and outputting the apparatus setting information and the print data to the drawing data creation means in a manner corresponding to the selected drawing data creation means An information processing apparatus comprising: creation means control means. The creation means control means controls the drawing data creation means by a control procedure stored in advance for the selected drawing data creation means.
The information processing apparatus according to claim 1. The conversion means analyzes the setting information and includes designation information for designating the drawing data creation means in the apparatus setting information,
The creation means control means detects the designation information included in the apparatus setting information by analyzing information included in the apparatus setting information, and selects the drawing data creation means designated by the designation information.
The information processing apparatus according to claim 2. The creation means control means detects information for selecting the drawing data creation means by analyzing information included in the apparatus setting information, and selects the drawing data creation means.
The information processing apparatus according to claim 2. Each of the plurality of drawing data creation means is prepared in advance corresponding to the setting information and the creation source of the print data,
The creation means control means analyzes the information included in the apparatus setting information to identify the creation source, and selects the drawing data creation means corresponding to the creation source.
The information processing apparatus according to claim 4. Control means for creating control data as the information included in the apparatus setting information using the apparatus setting information and the print data;
The control means creates the control data in the same format regardless of the drawing data creation means that the creation means control means analyzes and selects the control data.
The information processing apparatus according to claim 1. The control means outputs the control data to the creation means control means,
The control means outputs the control data to the creation means control means in the same procedure regardless of the drawing data creation means that the creation means control means analyzes and selects the control data. The information processing apparatus according to claim 6. When the drawing data creation means selected by the creation means control means has a sequence for controlling drawing processing for one page,
The creation means control means instructs the drawing data creation means to draw on a page basis,
When the drawing data creation means selected by the creation means control means does not have a sequence for controlling drawing processing for one page,
The creation means control means instructs the drawing data creation means to draw in a drawing unit requested by the drawing data creation means;
The information processing apparatus according to any one of claims 1 to 7. An information processing method performed by an information processing apparatus capable of communicating with a plurality of drawing data creating means for creating drawing data used for image formation in a printing apparatus,
An acquisition means for acquiring print setting information and print data used by the drawing data creation means for creating the drawing data;
A converting means for converting the setting information into apparatus setting information in a format handled by the information processing apparatus;
The creation means control means analyzes the information included in the apparatus setting information, selects the drawing data creation means, and sets the apparatus setting information and the print data in a manner according to the selected drawing data creation means. Outputting to drawing data creating means;
An information processing method characterized by comprising: In an information processing device that creates drawing data using print setting information and print data,
A conversion step of converting the setting information into device setting information in a format handled by the information processing device;
Analyzing the information contained in the apparatus setting information, selecting one drawing data creating means from a plurality of drawing data creating means, and the apparatus setting information and the printing in a manner corresponding to the selected drawing data creating means A creation means control step for outputting data to the drawing data creation means;
A program that executes

Images