JP2018156171A - Control program, program, image formation output system, process execution control device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently execute a print workflow even when a format of job data differs between an HWF server and a DFE.SOLUTION: A program for setting process setting information transmitted to an image formation output control device that controls execution of image formation output according to the process setting information including information for setting process content for executing the image formation output in a process execution control device that controls execution of a plurality of processes, executes: a unique process information extraction step of extracting the unique process information from the process setting information including the unique process information indicating the process content unique to the image formation output control device; a display control step of displaying a setting screen for setting a process setting value of the extracted unique process information; and a process setting value reflection step of reflecting the set process setting value in command information to be transmitted to cause the image formation output control device to execute the image formation output.SELECTED DRAWING: Figure 20

Description

  The present invention relates to a control program, a program, an image formation output system, and a process execution control device.

  A method for defining and controlling all processes related to the generation of printed materials is used by an information transmission format called JDF (Job Definition Format) or JMF (Job Messaging Format). According to this method, it is possible to collectively control different types of printers such as an offset printer and a digital printer. Such a system is called an HWF (Hybrid Work Flow) system, and a server that controls such a system is called an HWF server.

  In such an HWF system, when the output is executed by each of the offset printer and the digital printer based on the same print data, the same result may be obtained with no difference in font, color, layout, etc. Desired. Therefore, an offset printer and a digital printer share a RIP (Raster Image Processor) engine that outputs raster data, which is data that is finally referred to in print output, based on the print data.

  Such an RIP engine is mounted on the above-described HWF server, and in the case of output by an offset printer, raster data generation processing (hereinafter referred to as “RIP processing”) is performed by the RIP engine on the HWF server. On the other hand, in the case of digital printers, a configuration called DFE (Digital Front End) generally receives print data, performs RIP processing, and causes the printer engine to execute print output.

  That is, when a digital printer is used in the HWF system, a method is adopted in which the DFE receives data from the HWF server, and the printer engine of the digital printer is controlled by the DFE to execute print output. Therefore, as described above, the RFE engine shared with the offset printer is mounted on the DFE.

  In such an HWF system, it is possible to cause the HWF server to execute print settings when performing print output based on the same print data. At this time, the HWF server acquires information necessary for performing print settings such as functions of the DFE and the configuration of the post-processing apparatus connected to the DFE as device information, and a UI (User Interface) for performing the print settings. ) Is displayed.

  Also, the HWF system can connect a plurality of DFEs to one HWF server. Therefore, the DFE and the digital printer may be additionally connected for the purpose of using the functions installed in the DFE or for the purpose of improving the throughput in print output.

  At this time, since the versions of the DFE already connected to the HWF server and the additionally connected DFE are different, the job data format may be different between the HWF server and the DFE. In contrast, even if the job format is different between the upstream and downstream applications of the print workflow, that is, between the application installed in the HWF server and the application installed in the DFE, the print output is performed. A technique for enabling execution is known (see, for example, Patent Document 1).

  In Patent Literature 1, job data received by the DFE from the HWF server is converted into job data that can be interpreted by the DFE, so that differences in job formats can be dealt with.

  However, in Patent Document 1, there is a case where the HWF server cannot interpret job data that can be interpreted in an additionally connected DFE, that is, a description of JDF that is extended so as to be interpretable in the additionally connected DFE. For this reason, it is not possible to make settings related to the functions installed in the additionally connected DFE from the HWF server.

  In addition, in order to reflect the JDF description expanded so that it can be interpreted in the additionally connected DFE to the job data, the job is once transmitted from the HWF server to the DFE and saved, and the saved job is edited on the DFE. This will reduce the efficiency of the print workflow.

  The present invention has been made to solve such problems, and an object of the present invention is to efficiently execute a print workflow even when the job data format differs between the HWF server and the DFE. To do.

  In order to solve the above problems, according to one aspect of the present invention, there is provided information for setting a processing content for executing image forming output based on command information received from a processing execution control device that controls execution of a plurality of processes. A control program for setting the processing setting information transmitted to the image forming output control device that controls execution of the image forming output according to the processing setting information including the processing content unique to the image forming output control device. Specific processing information generation step for generating the processing setting information, and a transmission control step for transmitting the processing setting information to the processing execution device. A unique process information extraction step for extracting the unique process information from the process setting information, and a setting for setting a process setting value of the extracted unique process information. A display control step for displaying a screen, and a processing setting value reflecting step for reflecting the set processing setting value in command information transmitted to the image forming output control device in order to execute the image forming output. The processing execution control device is executed.

  According to the present invention, even when the job data format is different between the HWF server and the DFE, the print workflow can be efficiently executed.

It is a figure which shows the operation | use form of the system which concerns on embodiment of this invention. It is a block diagram which shows the hardware constitutions of the information processing apparatus which concerns on embodiment of this invention. It is a figure which shows the JDF information which concerns on embodiment of this invention. It is a block diagram which shows the function structure of the HWF server which concerns on embodiment of this invention. It is a figure which shows the example of the workflow information which concerns on embodiment of this invention. It is a block diagram which shows the function structure of DFE which concerns on embodiment of this invention. It is a figure which shows the example of the conversion table which concerns on embodiment of this invention. It is a figure which shows the example of the RIP parameter which concerns on embodiment of this invention. It is a block diagram which shows the function structure of the RIP engine which concerns on embodiment of this invention. It is a block diagram which shows the function structure of the RIP engine which concerns on embodiment of this invention. It is a sequence diagram which shows the whole operation | movement of the system which concerns on embodiment of this invention. It is a figure which shows the information of the division | segmentation request | requirement which concerns on embodiment of this invention. It is a figure which shows the device information which concerns on embodiment of this invention. It is a figure which shows the job setting UI which concerns on embodiment of this invention. It is a flowchart which shows the flow of the process which displays job setting UI based on the device information which concerns on embodiment of this invention. It is a figure which shows the device information which concerns on embodiment of this invention. It is a figure which shows the job setting UI which concerns on embodiment of this invention. It is a figure which shows the JDF information in which the process setting value of the expansion tag which concerns on embodiment of this invention was reflected. It is a figure which shows the device information which concerns on embodiment of this invention. It is a figure which shows the job setting UI which concerns on embodiment of this invention. It is a figure which shows the device information which concerns on embodiment of this invention. It is a figure which shows the job setting UI which concerns on embodiment of this invention. It is a flowchart which shows the process in DFE which concerns on embodiment of this invention. It is a flowchart which shows the RIP process which concerns on embodiment of this invention.

  Embodiments of the present invention will be described below with reference to the drawings. In the present embodiment, an image forming output system capable of controlling both printers via the same server in a system in which offset printers and digital printers coexist will be described. Such a system is called an HWF (Hybrid Work Flow) system. In the case of operating a digital printer in such a system, in this embodiment, an HWF system equipped with a DIP (Digital Front End) that controls the digital printer and a RIP (Raster Image Processor) engine shared by the server. An example will be described.

  FIG. 1 is a diagram illustrating an operation mode of the HWF system according to the present embodiment. As shown in FIG. 1, the system according to this embodiment includes a digital printer 1, an offset printer 2, a post-processing device 3, HWF servers 4a and 4b (hereinafter collectively referred to as “HWF server 4”), a client terminal 5a, 5b (hereinafter collectively referred to as “client terminal 5”) is connected via a network.

  The digital printer 1 is a printer that performs image formation output without using a plate, such as an electrophotographic method or an inkjet method, and includes a DFE 100, a digital engine 150, and an inline finisher 160. The DFE 100 functions as an image forming output control device that is a control unit for causing the digital engine 150 to perform print output and the inline finisher 160 to perform post-processing. The digital engine 150 functions as an image forming apparatus, and the inline finisher 160 functions as a post-processing apparatus. Therefore, the DFE 100 includes a RIP (Raster Image Processor) engine for generating raster data that is image data to be referred to when the digital engine 150 executes print output. Raster data is drawing information.

  The offset printer 2 is a printer that performs image formation output using a plate, and includes a CTP (Computer To Plate) 200 and an offset engine 250. The CTP 200 is a device that generates a plate based on raster data. When the plate is generated by the CTP 200, the offset engine 250 can perform offset printing.

  The post-processing device 3 is a device that performs post-processing such as punching, stapling, bookbinding, and the like on a recording medium printed and output by the digital printer 1 and the offset printer 2. The HWF server 4 is a server in which HWF software for managing everything from job data including image data to be printed out to printout and post-processing is installed. The HWF server 4 manages the various processes described above based on information generated in an information format called JDF (Job Definition Format) (hereinafter referred to as “JDF information”). That is, the HWF server 4 functions as a process execution control device.

  When performing print output by offset printing using the offset printer 2, the HWF server 4 generates raster data using an RIP engine mounted therein and transmits the raster data to the CTP 200. Therefore, the RWF engine is mounted on the HWF server 4.

  On the other hand, when printing output is performed by the digital printer 1, data is transmitted to the DFE 100. Since the DFE 100 is equipped with the RIP engine as described above, the HWF server 4 can cause the digital printer 1 to execute print output by transmitting print data before RIP processing to the DFE 100.

  Here, print output based on the same print data may be executed in each of the digital printer 1 and the offset printer 2. In such a case, if the print output results of the two are different, the user receiving the output product will feel uncomfortable. Therefore, it is preferable that the print output results in the digital printer 1 and the offset printer 2 are the same.

  Differences in print output by different devices are mainly caused by RIP processing. Therefore, by using the RIP engine in which the processing is shared by the digital printer 1 and the offset printer 2, the difference between the output results of both can be minimized.

  In other words, the RIP engine installed in the HWF server 4 in the present embodiment is a RIP engine that supports both the digital printer 1 and the offset printer 2 and has a process that can be shared. The DFE 100 is equipped with a RIP engine that is common to the RIP engine mounted on the HWF server 4.

  With such a configuration, a common RIP engine is mounted on the HWF server 4 and the DFE 100. Therefore, when printing output is executed by the digital printer 1, the RIP processing by the HWF server 4 and the RIP processing by the DFE 100 can be combined.

  The client terminal 5 is an information processing terminal for an operator who uses the system to operate the HWF server 4 and is realized by a general PC (Personal Computer) or the like. The operator operates the client terminal 5 to display a GUI (Graphical User Interface) for operating the HWF server 4, and inputs data, sets the above-described JDF information, and the like. JDF information is processing setting information.

  Next, a hardware configuration of an information processing apparatus such as the DFE 100, the HWF server 4, and the client terminal 5 according to the present embodiment will be described with reference to FIG. As shown in FIG. 2, the information processing apparatus according to the present embodiment includes the same configuration as a general server, a PC (Personal Computer), or the like. That is, the information processing apparatus according to the present embodiment includes a CPU (Central Processing Unit) 10, a RAM (Random Access Memory) 20, a ROM (Read Only Memory) 30, an HDD (Hard Disk Drive) 40, and an I / F 50. Connected through. Further, an LCD (Liquid Crystal Display) 60 and an operation unit 70 are connected to the I / F 50.

  The CPU 10 is a calculation means and controls the operation of the entire information processing apparatus. The RAM 20 is a volatile storage medium capable of reading and writing information at high speed, and is used as a work area when the CPU 10 processes information. The ROM 30 is a read-only nonvolatile storage medium and stores a program such as firmware. The HDD 40 is a non-volatile storage medium that can read and write information, and stores an OS (Operating System), various control programs, application programs, and the like.

  The I / F 50 connects and controls the bus 80 and various hardware and networks. The LCD 60 is a visual user interface for the user to check the state of the information processing apparatus. The operation unit 70 is a user interface such as a keyboard and a mouse for a user to input information to the information processing apparatus. Since the HWF server 4 is operated as a server, user interfaces such as the LCD 60 and the operation unit 70 can be omitted.

  In such a hardware configuration, the software control unit is configured by the CPU 10 performing calculations according to a program stored in the ROM 30 or a program loaded into the RAM 20 from a storage medium such as the HDD 40 or an optical disk. A functional block for realizing the functions of the DFE 100, the HWF server 4, and the client terminal 5 according to the present embodiment is configured by a combination of the software control unit configured as described above and hardware.

  Next, the above-described JDF information will be described. FIG. 3 is a diagram illustrating an example of JDF information. As shown in FIG. 3, the JDF information includes “job information” regarding job execution, “edit information” regarding raster data, and “finishing information” regarding post-processing. It also includes information on “RIP status”, “RIP device designation”, and “device designation”.

  As shown in FIG. 3, the “job information” includes information such as “number of copies”, “number of pages”, and “RIP control mode”. “Number of copies” is information for designating the number of copies of the printed matter to be output. “Number of pages” is information for designating the number of pages of a printed material. “RIP control mode” indicates a control mode of RIP processing, and “page mode”, “sheet mode”, and the like are designated.

  “Edit information” includes “orientation information”, “printing surface information”, “rotation”, “enlargement / reduction”, “image position”, “layout information”, “margin information”, and “crop mark information”. . “Orientation information” is information for designating the printing orientation, such as “vertical” or “horizontal”. “Print surface information” is information for designating a print surface such as “double-sided” or “single-sided”.

  “Rotation” is information for designating the rotation angle of the image to be output. “Enlargement / reduction” is information for designating a scaling factor of an image to be output. “Offset” of “Image position” is information for specifying an offset of an image to be output. “Position adjustment information” is information for designating a processing adjustment value for position adjustment of an output target image.

  “Custom imposition arrangement” of “layout information” is information specifying the arrangement of the custom surface. “Number of pages” is information for designating the number of pages per sheet. For example, when two pages are collected on one sheet, “2 in 1” is designated. “Page order information” is information specifying information related to the order of pages to be printed. “Creep position adjustment” is information for specifying a processing set value relating to the adjustment of the creep position.

  “Margin information” is information for specifying processing setting values related to margins such as fit boxes and gutters. “Center crop mark information” of “Crop mark information” is information for specifying a processing setting value related to the center crop mark. “Corner / Crop / Mark Information” is information for designating processing setting values for corner / crop / mark.

  “Finishing information” includes “Collate information”, “staple / bind information”, “punch information”, “folding information”, “trim”, “output tray information”, “input tray information”, “cover sheet information” including. “Collate information” is information for designating whether printing is performed in units of pages or in units of documents when a plurality of copies of a document are printed.

  “Staple / bind information” is information for specifying processing related to stapling / binding. “Punch information” is information for designating processing relating to punching. “Folding information” is information for specifying processing related to folding. “Trim” is information for specifying processing related to trimming.

  “Output tray information” is information for designating an output tray. “Input tray” is information for designating an input tray. “Cover / sheet information” is information for designating processing relating to a cover / sheet.

  “RIP status” is execution state information indicating whether or not each RIP internal process, which is each process included in the RIP process, has been executed. In FIG. 3, RIP internal processing items such as “Preflight”, “Normalize”, “Font”, “Layout”, “Mark”, “CMM”, “Trapping”, “Calibration”, “Screening” Is described. Then, the status of the processing state for each item is described. In FIG. 3, “NotYet” indicating unprocessed is set, and when each process is executed, it is updated to “Done”.

  “RIP device designation” is information for designating whether each RIP internal process is executed on the HWF server 4 side or the DFE 100 side. For each item of RIP internal processing similar to “RIP status”, either “HWF server” or “DFE” is set. When “DFE” is set, a process of generating a plurality of RIP engines or raster data mounted on the DFE 100, such as “DFE (engine A)” and “DFE (external processing unit 121)”, is performed. Information specifying one of the modules to be executed is included.

  “Device designation” is information for designating a device that executes a print job. In the example of FIG. 3, “digital printer” is designated. The JDF information includes various information in addition to the information shown in FIG. Such information will be described in detail in the following description.

  The JDF information shown in FIG. 3 is generated when the operator displays the GUI of the HWF server 4 via the client terminal 5 and sets various items in the GUI. The RIP engine mounted on the HWF server 4 or the DFE 100 performs RIP processing based on such JDF information. Further, the post-processing device 3 performs post-processing based on such JDF information.

  When a job is submitted to the HWF server 4 from an external software or system, the job may be submitted with JDF information attached. Details of the processing in such a case will be described later.

  Next, the functional configuration of the HWF server 4 according to the present embodiment will be described with reference to FIG. As shown in FIG. 4, the HWF server 4 includes an HWF controller 400 and a network I / F 401. The network I / F 401 is an interface for the HWF server 4 to exchange information with other devices via the network.

  The HWF controller 400 manages acquisition of data to be printed, creation of a print job, management of a workflow, distribution of jobs to the digital printer 1 and the offset printer 2, and the like. A process in which job data to be printed is input to the HWF server 4 and acquired by the HWF controller 400 is a submission process in the present system. The HWF controller 400 is configured by installing dedicated software in the information processing apparatus. This software is HWF software.

  In the HWF controller 400, the system control unit 410 controls the entire HWF controller 400. Therefore, the system control unit 410, when realizing each function of the HWF controller 400 described above, gives an instruction to each unit of the HWF controller 400 to execute processing. The data receiving unit 411 receives print job data from another system, or receives job data submitted by an operator's operation.

  A UI (User Interface) control unit 412 controls an operation by an operator via the client terminal 5. A GUI for operating the HWF server 4 is displayed on the client terminal 5, and the UI control unit 412 acquires operation information for the GUI displayed on the client terminal 5 via the network.

  The UI control unit 412 notifies the system control unit 410 of operation information acquired via the network in this way. The display of the GUI on the client terminal 5 is realized by software installed in the client terminal 5 in advance or information provided from the UI control unit 412 to the client terminal 5 via the network. Accordingly, the UI control unit 412 functions as a display control unit that executes a display control step for causing the client terminal 5 to display a UI that is execution status information indicating the execution status of the process.

  The operator selects job data to be submitted by manipulating the GUI displayed on the client terminal 5. Thereby, the client terminal 5 transmits job data to the HWF server 4, and the data receiving unit 411 acquires the job data. The system control unit 410 registers the job data acquired by the data reception unit 411 in the job data storage unit 414.

  When job data is transmitted from the client terminal 5 to the HWF server 4, job data is generated at the client terminal 5 based on the document data or image data selected at the client terminal 5 and then transmitted to the HWF server 4. . The job data is command information in a PDL (Page Description Language) format such as PDF (Portable Document Format) or PostScript.

  In addition, the data to be printed may be transmitted from the client terminal 5 to the HWF server 4 in the data format dedicated to the application or the general image data format. In that case, the system control unit 410 causes the job control unit 413 to generate job data based on the acquired data. The job control unit 413 generates job data based on data to be printed by the function of the RIP engine 420.

  Note that the print target data registered in the job data storage unit 414 is PDL information as described above. This PDL information is not only primary data generated based on the print target data, but also halfway. There may be intermediate data that has been processed. These pieces of information are used as output target image information. Examples of the case where the intermediate data is stored in the job data storage unit 414 include the case where the job data is registered in the HWF server 4 in the intermediate data state in addition to the state in the middle of the processing already started in the HWF server 4. There can be. Hereinafter, when “PDL information” is set, it indicates primary data that has not been subjected to RIP processing, and when “intermediate data” is set, data in the middle of processing in which RIP processing has been executed halfway is indicated. Show.

  Further, as described above, the JDF information described with reference to FIG. 3 is set and generated by an operator's operation on the GUI displayed on the client terminal 5. Alternatively, when a job is submitted to the HWF server 4 from an external software or system, it is given in advance. The JDF information acquired in this way is received as job data by the data receiving unit 411 together with the PDL information. The system control unit 410 registers the JDF information and PDL information acquired in this way in the job data storage unit 414 in association with each other.

  In the present embodiment, the case where JDF information is used as attribute information indicating the content of a job has been described as an example. However, this is only an example, and other formats such as PPF (Print Production Format) information may be used.

  Further, the system control unit 410 can divide the received job data for each print region such as a page unit based on an operator's operation on the GUI displayed on the client terminal 5. Each of the divided job data is registered in the job data storage unit 414 as divided individual job data.

  For each job for which division is specified, when an output destination device is selected by an operator's operation on the GUI displayed on the client terminal 5, the selection result is associated with the job data in the job data storage unit 414. Saved. As an output destination selection mode, for example, there may be a selection mode such as the digital printer 1 for the cover portion and the offset printer 2 for the body.

  The device information management unit 416 performs management by acquiring device information that is information on other devices included in the system, such as the digital printer 1, the offset printer 2, and the post-processing device 3, and storing it in the device information storage unit 417. . The other device information includes a network address assigned when the device is connected to the network and device function information. The device function information includes, for example, a printing speed, usable post-processing functions, an operation state, and the like. Details of the device information will be described later.

  The device information communication unit 415 periodically acquires device information of other devices included in the system via the network I / F 401. Thus, the device information management unit 416 periodically updates the device information stored in the device information storage unit 417. Therefore, even if the device information of another device changes dynamically, the device information storage unit 417 Stored information is kept accurate.

  The workflow control unit 418 determines the execution order of each process when processing job data registered in the job data storage unit 414 on the system, and stores the information in the workflow information storage unit 419. The execution order of each process determined in the workflow is determined in advance. In order to maintain the order, the process is controlled to proceed to the next process when the previous process is completed.

  That is, what is stored in the workflow information storage unit 419 is workflow information in which the respective processes that can be executed in the HWF system are combined in the designated order. FIG. 5 is a diagram illustrating an example of workflow information. On the other hand, parameters when each process is executed are specified in the JDF information as described above. In the workflow information storage unit 419, workflow information set based on an operator's operation on the GUI displayed on the client terminal 5 is registered in advance.

  The execution instruction for the job data registered in the HWF server 4 is notified to the system control unit 410 via the UI control unit 412 based on the operator's operation on the GUI displayed on the client terminal 5. As a result, the system control unit 410 selects the output destination device described above.

  As described above, in the aspect of selecting an output destination device on the GUI displayed on the client terminal 5, the system control unit 410 selects an output destination device according to the designated content. In addition, a mode in which selection is automatically performed based on a comparison between job contents and device characteristics is also possible.

  When an output destination device is automatically selected based on a comparison between job contents and device characteristics, the system control unit 410 acquires information on available devices from the device information management unit 416. When the output destination device is determined in this way, the system control unit 410 adds information indicating the determined output destination device to the JDF information.

  After determining the output destination device, the system control unit 410 instructs the workflow control unit 418 to execute a job. At this time, the workflow information registered in advance in the workflow information storage unit 419 based on the operator's operation may be used, or new workflow information may be generated based on the contents set according to the operator's operation. .

  When the workflow control unit 418 receives an execution instruction from the system control unit 410, the workflow control unit 418 instructs the job control unit 413 to execute each process according to the specified execution order according to the specified workflow information or newly generated workflow information. That is, the workflow control unit 418 functions as a process execution control unit.

  Upon receiving the execution instruction, the job control unit 413 inputs the above-described PDL information and JDF information to the RIP engine 420 to execute the RIP process. The JDF information includes information indicating which of the HWF server 4 and the DFE 100 executes each of a plurality of RIP internal processes performed by the RIP engine.

  The job control unit 413 refers to the RIP process distribution information in the information included in the JDF information, and if the process instructed by the workflow control unit 418 is a process to be executed in the HWF server 4, the RIP engine 420 Causes the specified process to be executed. The RIP engine 420 executes RIP processing based on parameters specified in the JDF information in accordance with instructions from the job control unit 413.

  The RIP engine 420 that has executed the RIP process in this manner updates the RIP status of the RIP process that has executed the process. As a result, the status of the RIP internal process executed by the HWF server 4 among the plurality of RIP internal processes is changed to “Done”. The RIP engine 420 functions as a control-side drawing information generation unit.

  The RIP execution result data generated by executing the RIP process is any of PDL information, intermediate data, and raster data. Although these differ in the contents of the RIP internal processing, intermediate data is generated based on data that was initially PDL information as the processing proceeds, and finally raster data is generated. The RIP execution result data is stored in the job data storage unit 414 in association with the job being executed.

  When one RIP internal process is completed, the RIP engine 420 notifies the job control unit 413 of the completion, and the job control unit 413 notifies the workflow control unit 418. Thereby, the workflow control unit 418 starts control of the next process according to the workflow information.

  When the content of the job received from the workflow control unit 418 is a request for another system, the job control unit 413 inputs job data in a form corresponding to the other system to the job transmission / reception unit 421, and Send it. In the case of transmission of job data to the offset printer 2, the print target data is converted into raster data and then transmitted as job data.

  On the other hand, when transmitting job data to the digital printer 1, the job control unit 413 designates the same RIP engine corresponding to the RIP engine 420 among the plurality of RIP engines included in the DFE 100 and sends it to the job transmission / reception unit 421. Enter job data. As a result, the job transmitting / receiving unit 421 transmits the job data to the DFE 100 by designating the same RIP engine corresponding to the RIP engine 420.

  The job transmission / reception unit 421 transmits job data obtained by packaging PDL information or intermediate data and JDF information to the DFE 100. As a transmission mode of job data, PDL information or intermediate data may be external resource data, and a URL indicating a storage location of PDL information or intermediate data may be described in JDF information. In this case, the URL that receives the JDF information accesses the URL, and acquires PDL information or intermediate data.

  Next, a functional configuration of the DFE 100 according to the present embodiment will be described with reference to FIG. The DFE 100 receives job data from the HWF server 4 and performs control of the received job, execution control of RIP processing, and control of the digital engine 150. The HWF server 4 causes the digital engine 150 to execute print output by transmitting job data to the DFE 100. That is, the DFE 100 functions as a server for providing a digital print function to the HWF server 4.

  The job control function provided by the DFE 100 is a control function for a series of operations such as job data reception, JDF information analysis, raster data creation, and print output by the digital engine 150. The execution control of the RIP process is a control for causing the RIP engine to execute the RIP process for generating raster data based on information generated by analyzing the JDF information and the PDL information.

  The information generated by the analysis of the JDF information is information obtained by extracting information used for the RIP processing from the JDF information described in FIG. 3 and converting the information into a format decipherable by the DFE 100. It is called “attribute”. By executing the RIP process with reference to the job attributes in the DFE and the PDL information, intermediate data and raster data are created.

  The control function of the digital engine 150 is a function that causes the digital engine 150 to transmit raster data and a part of the above-described job attributes in the DFE to execute print output. These functions are realized by the blocks shown in FIG. Each block shown in FIG. 6 is realized by the CPU 10 performing arithmetic processing according to a program loaded in the RAM 20 or a program stored in the ROM 30 and operating other hardware as described in FIG.

  The DFE 100 has a plurality of RIP engines mounted therein. This is installed corresponding to the RIP engine of another device that may transmit a job to the DFE 100 in the HWF system. In the present embodiment, since different RIP engines are included in the plurality of HWF servers 4a and 4b, the DFE 100 is equipped with a plurality of RIP engines corresponding to the respective RIP engines.

  The job receiving unit 111 includes an individual job receiving unit 112. The individual job receiving unit 112 receives job data from the HWF server 4 via the network I / F 101. The individual job receiving unit 112 is provided corresponding to each of a plurality of RIP engines installed in the DFE 100.

  As described above, when transmitting job data from the HWF server 4 to the DFE 100, a corresponding RIP engine is designated and transmitted. Therefore, in the job receiving unit 111, the individual job receiving unit 112 corresponding to the RIP engine specified in the JDF information receives the job data.

  Note that job data input to the DFE 100 can be input from the HWF server 4 via a network, or via a portable storage medium such as a USB memory. In this embodiment, a case where JDF information is included in job data will be described as an example. However, when JDF is not included, the job reception unit 111 creates dummy JDF information and the job data includes the dummy JDF. Give information.

  The individual job receiving unit 112 functions as a virtual printer in which job contents are set in advance, in addition to the case where the individual job receiving unit 112 is provided corresponding to each RIP engine described above. In other words, the RIP engine installed in the DFE 100 and the individual job receiving unit 112 in which the job contents are set are provided, and by specifying any one of the plurality of individual job receiving units 112, the job can be executed with the preset contents. It can be executed.

  The system control unit 113 stores the job data received by the individual job reception unit 112 in the job data storage unit 114 or passes it to the job control unit 116. When the DFE 100 is set to store job data, the system control unit 113 stores the job data in the job data storage unit 114. If the JDF information describes whether or not to store in the job data storage unit 114, the system control unit 113 follows the description.

  The case where job data is stored in the job data storage unit 114 is, for example, a case where the print content is previewed in the DFE 100. In this case, the system control unit 113 obtains print target data included in the job data, that is, PDL information and intermediate data from the job data storage unit 114, generates preview data, and transfers the preview data to the UI control unit 115. Accordingly, the UI control unit 115 causes the display 102 to display a preview of the print content.

  When generating preview data, the system control unit 113 passes the data to be printed to the job control unit 116 and requests generation of preview data. The job control unit 116 passes the data to be printed to the RIP unit 118 to generate preview data, and passes the generated preview data to the system control unit 113.

  Also, when the operator changes the JDF information in the DFE 100, the job data is stored in the job data storage unit 114. In this case, the system control unit 113 acquires JDF information from the job data storage unit 114 and passes it to the UI control unit 115. As a result, the JDF information of the job data is displayed on the display 102, and the operator can change it by operation.

  When the operator changes the JDF information by operating the DFE 100, the UI control unit 115 receives the change content and notifies the system control unit 113 of the change. The system control unit 113 updates the received change content by reflecting it in the JDF information, and stores the updated JDF information in the job data storage unit 114.

  When the system control unit 113 receives a job execution instruction, the system control unit 113 transfers the job data stored in the job data storage unit 114 to the job control unit 116. The job execution instruction is input from the HWF server 4 via the network or input by an operator operation on the DFE 100. For example, when the job execution time is set in the JDF information, the system control unit 113 delivers the job data stored in the job data storage unit 114 to the job control unit 116 when the set time comes.

  The job data storage unit 114 is a storage area for storing job data as described above, and is realized by the HDD 40 described with reference to FIG. In addition, a storage device connected to the DFE 100 via a USB interface or the like, or a storage device connected via a network may be used.

  The UI control unit 115 receives information displayed on the display 102 and an operator's operation on the DFE 100 as described above. In the above-described JDF information editing operation, the UI control unit 115 interprets the JDF information and displays the contents of the print job on the display 102.

  The job control unit 116 is an execution control unit that performs control related to job execution based on a job execution instruction from the system control unit 113. Specifically, the control performed by the job control unit 116 is JDF analysis processing by the JDF analysis unit 117, RIP processing by the RIP unit 118, and control processing of the digital engine 150 and the inline finisher 160 by the printer control unit 123.

  Upon receiving a job execution instruction from the system control unit 113, the job control unit 116 inputs JDF information included in the job data to the JDF analysis unit 117 and makes a JDF conversion request. The JDF conversion request is a request for processing for converting JDF information described in the format of the JDF information generation source into a format recognizable by the RIP unit 118.

  The JDF analysis unit 117 converts the JDF information described in the generation source format into a format that can be recognized by the RIP unit 118 as described above. The JDF analysis unit 117 holds a conversion table therein, and in accordance with the conversion table, the RIP unit 118 extracts necessary information from the information included in the JDF information and converts the description format. As a result, the above-described job attributes within DFE are generated.

  FIG. 7 is a diagram illustrating an example of a conversion table held by the JDF analysis unit 117 according to the present embodiment. As shown in FIG. 7, the conversion table according to the present embodiment is information in which a description format in JDF information and a description format in job attributes in DFE are associated with each other. For example, the “number of copies” information described in FIG. 3 is described as “A: Amount” in the actual JDF information, and is converted into a description of “number of copies” when generating the job attribute in DFE.

  The job attributes in the DFE are generated by the processing of the JDF analysis unit 117 using the conversion table as shown in FIG. The information described in the job attributes within DFE is, for example, “job information”, “edit information”, “finishing information”, etc. shown in FIG.

  Also, the JDF analysis unit 117 sets “RIP control mode” in the job attributes within DFE when generating the job attributes within DFE. In “RIP control mode”, information for setting “page mode”, “sheet mode” and the like is set. The JDF analysis unit 117 assigns the “RIP control mode” according to the type of the individual job reception unit 112 that has received the job data, the contents of the job, the HWF software that constitutes the HWF server 4 that is the transmission source of the job data, and the like.

  In the present embodiment, the setting of aggregate printing in a print job is handled in “page mode”. Details of the “RIP control mode” will be described later.

  The job control unit 116 generates “RIP parameters” based on the job attributes in the DFE generated by the JDF analysis unit 117, and passes RIP parameters to the RIP control unit 119 of the RIP unit 118 to perform RIP processing. Let it run. As a result, the RIP unit 118 executes RIP processing based on the RIP parameters.

  FIG. 8 is a diagram showing the contents of RIP parameters according to the present embodiment. The RIP parameters according to the present embodiment include “input / output data type”, “data read information”, and “RIP control mode” as the initial information. “Input / output data type” designates the type of input / output data such as “JDF”, “PDL”, and the like. The designation format includes a text format, an extension of image data, intermediate data, and the like in addition to “JDF”, “PDL”, and the like.

  The “data read information” is information on how to specify the read position and write position of input / output data and the specified position. “RIP control mode” is information of “page mode” and “sheet mode”. In addition, the information at the beginning includes unit information used in the RIP parameter and data compression method information.

  “Input / output image information” includes “output image information”, “input image information”, and “image handling information”. “Information about output image” includes information such as format, resolution, size, color separation, color shift, and page orientation of output image data. The “information about the input image” includes information such as the format, resolution, page range, and color setting of the input image data. “Information relating to image handling” includes information such as an offset of an enlargement / reduction algorithm, an object area, and an offset of a halftone.

  “PDL related information” is information related to PDL information targeted by the RIP parameter, and includes information on “data area”, “size information”, and “data arrangement method”. Note that the PDL information here is data to be printed in a job, and includes intermediate data. “Data area” designates area information in which PDL information is stored. “Size information” specifies the data size of the PDL information. “Data arrangement method” designates a data arrangement method in the memory of PDL information such as “little endian” and “big endian”.

  As shown in FIG. 8, the RIP parameters include “RIP control mode”. The RIP control unit 119 controls the RIP engine 120 according to the “RIP control mode”. Therefore, the sequence is determined according to the “RIP control mode”. As described above, “page mode” and “sheet mode” are set in the “RIP control mode”.

  The “page mode” is a process for generating raster data by executing RIP processing for each of a plurality of pre-combination pages collected on one sheet. “Sheet mode” is a process of generating Raster data collected on one sheet by executing RIP processing for each of a plurality of pages collected on one sheet.

  Further, the job control unit 116 sets “RIP engine identification information” in the RIP parameter. “RIP engine identification information” is information for identifying each of the plurality of RIP engines 120 included in the RIP unit 118. In the present embodiment, the same RIP engine corresponding to the RIP engine 420 mounted on the HWF server 4 is used in the DFE 100.

  Therefore, the JDF information includes information specifying the individual job receiving unit 112 as described above, and job data is received by the individual job receiving unit 112 specified by the information specifying the individual job receiving unit 112. Is done. The individual job receiving unit 112 corresponds to one of the RIP engines 120, and adds identification information of the corresponding RIP engine 120 to the received JDF information. The job control unit 116 adds the above-described “RIP engine identification information” to the RIP parameter based on the identification information of the RIP engine 120 added to the JDF information.

  In the RIP unit 118, the RIP control unit 119 controls the RIP engine 120, and causes the RIP engine 120 to execute RIP internal processing based on the input RIP parameters to generate raster data. Therefore, the RIP control unit 119 functions as an output side drawing information generation control unit that causes the RIP engine 120 that is the output side drawing information generation unit to generate raster data used in the image forming apparatus.

  The image storage unit 122 is a storage unit that stores raster data generated by the RIP engine 120. The image storage unit 122 is realized by the HDD 40 described with reference to FIG. In addition, a storage device connected to the DFE 100 via a USB interface or the like, or a storage device connected via a network may be used.

  The printer control unit 123 is connected to the digital engine 150 and the inline finisher 160. Therefore, the printer control unit 123 reads out raster data stored in the image storage unit 122 and transmits the raster data to the digital engine 150 to execute print output. Further, by obtaining finishing information included in the job attributes within DFE from the job control unit 116, control for finishing processing executed by the inline finisher 160 is performed.

  The printer control unit 123 can acquire information about the digital engine 150 and the inline finisher 160 by exchanging information between the digital engine 150 and the inline finisher 160. For example, in the case of the CIP4 standard, a DevCaps tag for transmitting / receiving device specification information to / from a printer is defined as a JDF information standard. Also known is a method for collecting printer information using a communication protocol called SNMP (Simple Network Management Protocol) and a database called MIB (Management Information Base).

  The device information management unit 124 manages device information that is information on the DFE 100 itself, the digital engine 150, and the inline finisher 160. The device information management unit 124 includes information on the RIP engine 120 included in the RIP unit 118, information on the individual job reception unit 112 configured in the job reception unit 111, detailed information on post-processing executed by the inline finisher 160, and the like. The device information is generated including the unique processing information. Therefore, the device information management unit 124 functions as a unique process information generation unit that executes a unique process information generation step.

  In the present embodiment, detailed information on post-processing executed by the inline finisher 160 is described in the JDF format. This detailed information is information that is converted into a description format in the job attributes in the DFE based on the description format in the JDF information by the conversion table held by the JDF analysis unit 117.

  The device information communication unit 125 executes a transmission control step for exchanging device information with the HWF server 4 via the network I / F 101 in accordance with specifications such as MIB and JMF (Job Messaging Format). A transmission control unit. Thereby, the device information communication unit 415 of the HWF server 4 acquires device information from the DFE 100. As a result, in the GUI displayed on the client terminal 5, information on the RIP engine 120 included in the DFE 100 and information on the individual job reception unit 112 are reflected.

  When the digital engine 150 and the inline finisher 160 are controlled by the printer control unit 123 in the DFE 100 and the print output is completed, the system control unit 113 recognizes this via the job control unit 116. Then, the system control unit 113 notifies the HWF server 4 of a print job completion notification via the job reception unit 111. As a result, the job transmission / reception unit 421 of the HWF server 4 receives a job completion notification.

  In the HWF server 4, the job transmission / reception unit 421 transfers a job completion notification to the job control unit 413, and the job control unit 413 notifies the workflow control unit 418 of job completion. The transmission of job data from the HWF server 4 to the DFE 100 is originally executed by the workflow control unit 418 according to the workflow information.

  When the workflow control unit 418 recognizes the completion of the job by the DFE 100, the workflow control unit 418 controls the execution of the next process according to the workflow information. As a process set next to the print output by the DFE 100, there is a post-process by the post-processing device 3 such as an outline finisher.

  Next, the functional configuration of the RIP engine according to the present embodiment will be described. FIG. 9 is a diagram illustrating a functional configuration of the RIP engine 120 when JDF analysis processing is performed by the JDF analysis unit 117. As described above, the RIP engine 120 is a software module that generates Raster data by executing RIP internal processing based on the RIP parameters described in FIG. As the RIP engine, for example, APPE that is a PDF printing engine provided by Adobe Systems is used as a base.

  As shown in FIG. 9, the RIP engine 120 includes a control unit 201 and other parts. Portions other than the control unit 201 are expansion units that can be expanded by vendors. The control unit 201 executes RIP processing by using various functions included as an extension unit. Further, in order to use the extended function of the extended part, JDF information described in a vendor-specific format in which the extended part is extended is added to the job data.

  The input unit 202 receives an initialization request or an RIP processing execution request, and notifies the control unit 201 of the request. When the initialization request is made, the above-described RIP parameters are also input to the control unit 201. Upon receiving the initialization request, the control unit 201 inputs the simultaneously received RIP parameters to the RIP parameter analysis unit 203. Then, the RIP parameter analysis result is acquired by the function of the RIP parameter analysis unit 203, and the order in which the respective extension units included in the RIP engine 120 are operated in the RIP process is determined. Further, the format of data generated as a result of these processes determines any of raster images, preview images, PDF, intermediate data, and the like.

  In addition, when the control unit 201 receives an RIP process execution request from the input unit 202, the control unit 201 operates each unit of the extension unit according to the processing order determined when the initialization request is received. The preflight processing unit 204 checks the validity of the contents of the input PDL data. When an invalid PDL attribute is found, the control unit 201 is notified. Upon receiving this notification, the control unit 201 notifies the external modules such as the RIP control unit 119 and the job control unit 116 via the output unit 213.

  The attribute information confirmed by the preflight processing is information that may cause a situation in which processing by other modules included in the RIP engine 120 becomes impossible, such as whether or not a non-corresponding font is specified. It is.

  The normalization processing unit 205 converts the input PDL data into PDF when it is PostScript instead of PDF. The mark processing unit 206 develops the graphic information of the designated mark and superimposes it on the designated position in the image to be printed.

  The font processing unit 207 takes out the font data, converts the font into an embedded PDL font, and performs outline processing. A CMM (Color Management Module) processing unit 209 converts the color space of an input image into CMYK (Cyan, Magenta, Yellow, blackK) based on a color conversion table described in an ICC (International Color Consortium) profile. The ICC profile is color ICC information and device ICC information.

  The trapping processing unit 210 performs a trapping process. Trapping is a process of expanding each color area to fill the gap in order to prevent gaps from occurring in the boundary when there are misalignments between adjacent color areas that touch the boundary. It is processing to do.

  The calibration processing unit 211 adjusts the variation in the color balance due to the temporal variation of the output device and individual differences in order to increase the accuracy of color conversion by the CMM processing unit 209. Note that the processing by the calibration processing unit 211 may be executed outside the RIP engine 120.

  The screening processing unit 212 performs a halftone dot generation process in consideration of the final output. Note that the processing by the screening processing unit 212 may be executed outside the RIP engine 120 in the same manner as the processing by the calibration processing unit 211. The output unit 213 transmits the RIP result to the outside. The RIP result is one of a raster image, preview image, PDF, and intermediate data determined at the time of initialization.

  The rendering processing unit 218 performs rendering processing for generating raster data based on input data. Of the processing units illustrated in FIG. 9, the processing by the mark processing unit 206 and the font processing unit 207 may be executed simultaneously by the rendering processing unit 218.

  Next, the functional configuration of the RIP engine 120 when not accompanied by JDF analysis processing by the JDF analysis unit 117 will be described with reference to FIG. As described above, the case where the JDF analysis processing by the JDF analysis unit 117 is not accompanied is a case where RIP internal processing is distributed between the HWF server 4 and the DFE 100. Therefore, the RIP engine 420 mounted on the HWF server 4 has the same configuration as the RIP engine 120 shown in FIG.

  As shown in FIG. 10, the functional configuration of the RIP engine 120 without JDF analysis processing by the JDF analysis unit 117 is almost the same as the configuration described in FIG. 9. Only the parts different from FIG. 9 will be described below. The part other than the control unit 201 is an extension unit as in FIG.

  When receiving the initialization request from the input unit 202, the control unit 201 in the example of FIG. 10 acquires JDF information together with the initialization request. Then, the control unit 201 analyzes the JDF information and the PDL information using the function of the job attribute analysis unit 214, and similarly to the case of FIG. 9, the processing order of each extension unit and the format of data generated as a result of the processing To decide.

  In particular, in the case of the RIP engine 120 installed in the DFE 100, the data format of the processing result is often raster data for input to the printer control unit 123. On the other hand, in the case of the RIP engine 420 mounted on the HWF server 4, the data format of the processing result differs depending on the distribution mode of processing between the HWF server 4 and the DFE 100. Therefore, the control unit 201 in the RIP engine 420 determines the data format of the processing result such as PDL information and intermediate data based on the analysis result by the job attribute analysis unit 214.

  Further, the control unit 201 analyzes the RIP status information included in the JDF information by using the function of the RIP status analysis unit 215, and confirms whether or not there is already executed RIP internal processing. If there is an already executed RIP internal process, the corresponding extension is excluded from the process target.

  Note that the RIP status analysis unit 215 can analyze the PDL information and execute the same processing as well as analyzing the RIP status included in the JDF information. In the case of PDL information, attribute information such as parameters disappears for already executed RIP internal processes, so it is possible to determine an unexecuted RIP internal process based on the remaining attribute information.

  The layout processing unit 217 performs imposition processing. The RIP status management unit 216 rewrites the RIP status corresponding to the RIP internal processing executed by each expansion unit to “Done” according to the control of the control unit 201. The output unit 213 transmits the RIP result to the outside of the engine. The RIP result is data in a data format determined at the time of initialization.

  The rendering processing unit 218 shown in FIG. 10 also performs rendering processing for generating raster data based on input data, as in FIG. In addition to the processing by the mark processing unit 206 and the font processing unit 207 among the processing units illustrated in FIG. 10, the processing by the layout processing unit 217 may be executed simultaneously by the rendering processing unit 218.

  Further, as described above, depending on the “RIP device designation” information included in the JDF information of the job data, it is mounted inside the DFE 100 such as “DFE (Engine A)” or “DFE (Engine B)”. There are cases where a plurality of RIP engines 120 are used properly. Since the control unit 201 cannot entrust processing to an extension unit of another RIP engine, the job control unit 116 determines the entrustee of these processes.

  As described above, the job control unit 116 adds “RIP engine identification information” to the RIP parameter. At this time, a different RIP parameter is generated for each RIP process in which a different RIP engine is designated. In the case of the example in FIG. 3, the RIP parameters for “Engine A” for which execution of “font” and “layout” is designated, the RIP parameters for “Engine B” for which execution of “Mark” is designated, and RIP parameters for “Engine A” for which execution of subsequent processing is designated are generated.

  Then, the job control unit 116 requests the RIP unit 118 to perform RIP processing in order for each generated RIP parameter in accordance with the order of RIP internal processing. As a result, “Engine A” and “Engine B” are selectively used to execute RIP internal processing.

  Then, the job control unit 116 designates the RIP engine 120 and transmits job data. On the other hand, “RIP status” information can be referred to as a method for causing the RIP engine 120 to execute only the designated process in the duplicated job data. That is, only the specified process can be executed by setting the status of only the process item to be executed to “NotYet” and setting the other process to “Done”.

  Note that, as described above, in the system according to the present embodiment, the RIP engine 120 that is common to the RIP engine 420 mounted on the HWF server 4 is mounted on the DFE 100. Here, the common RIP engine is at least a part related to the generation of raster data. Therefore, the RIP engine 420 and the RIP engine 120 do not share all the processing units shown in FIGS. 9 and 10.

  Next, the operation of the system according to the present embodiment will be described with reference to FIG. FIG. 11 is a sequence diagram showing the operation of the HWF system according to the present embodiment. FIG. 11 shows an example in which print output is executed by the digital printer 1. As shown in FIG. 11, in the HWF server 4, the device information communication unit 415 acquires device information from the DFE 100 and the CTP 200 via the network, and the device information management unit 416 registers information in the device information storage unit 417 ( S1101). The process of S1101 is periodically executed.

  On the other hand, the client terminal 5 transmits a job registration request to the HWF server 4 when a job data registration operation is performed by an operator's operation on the system GUI (S1102). In the HWF server 4, the UI control unit 412 acquires a job registration request. Thereby, the data receiving unit 411 acquires job data in accordance with the control of the system control unit 410 (S1103).

  When the job data is acquired by the data receiving unit 411, the system control unit 410 controls the job control unit 413 to convert the format of the acquired job data into the PDL format (S1104). The job data converted in this way is registered in the job data storage unit 414. In the GUI in which a job registration operation is performed in S1102, in addition to an interface for specifying data to be registered by a file path or the like, an input unit for specifying each item of information included in the JDF described in FIG. Is displayed.

  Further, through the processing of S1101, the HWF server 4 acquires information on the type of the RIP engine installed in the DFE 100. Therefore, in the input field for designating the “RIP device designation” information shown in FIG. 3 included in the GUI of the client terminal 5, which RIP engine 120 is to be executed when the DFE is executed is selected. It becomes possible.

  Further, when a job data division operation is performed by an operator's operation on the system GUI, the client terminal 5 transmits a job division request to the HWF server 4 (S1105). FIG. 12 is a diagram illustrating an example of information included in the job division request transmitted in S1105. As shown in FIG. 12, in addition to information indicating the job to be divided, information specifying the content of division is transmitted in the job division request. The information indicating the content of the division is information in which a device that executes print output is specified in units of pages.

  In the HWF server 4 that has received the job division request, the system control unit 410 divides the job in units of pages according to the division contents and generates separate jobs for the division target job specified in the information shown in FIG. (S1106). At this time, the device designated for each division range is used as the “device designation” information shown in FIG. 3 in the JDF information. Jobs divided and generated in this way are stored in the job data storage unit 414 as individual jobs.

  Further, when a workflow generation operation is performed by an operator's operation on the system GUI, the client terminal 5 transmits a workflow generation request to the HWF server 4 (S1107). In the workflow generation request, information for specifying the contents of the workflow as shown in FIG. 5 and information for specifying a job to be processed according to the workflow are transmitted.

  In the HWF server 4 that has received the workflow generation request, the system control unit 410 inputs the information received together with the request to the workflow control unit 418. As a result, the workflow control unit 418 generates new workflow information based on the received information, stores the new workflow information in the workflow information storage unit 419, and associates the workflow with the job specified in the request (S1108). The association between the workflow and the job is executed by adding an identifier for identifying the workflow to the JDF information, for example.

  After such processing, when a job execution operation is performed by an operator's operation on the system GUI at the client terminal 5, the client terminal 5 transmits a job execution request to the HWF server 4. Note that the operations of S1102 to S1109 may be executed according to different operations, or a job registration request, a job division request, a workflow generation request, and a job execution request may be performed by a single operation.

  In the HWF server 4 that has received the job execution request, the system control unit 410 acquires the specified job data from the job data storage unit 414 based on the information for specifying the job data received together with the request (S1110). . In addition, the system control unit 410 acquires the latest information on the device specified in the acquired job data from the device information management unit 416, and sets the device information for the job (S1111).

  Thereafter, the system control unit 410 delivers the job data to the workflow control unit 418 and starts execution of the workflow (S1112). The workflow control unit 418 acquires workflow information associated with the acquired job data from the workflow information storage unit 419, and executes processing according to the workflow information.

  In the workflow process, first, an in-server process to be executed by the RIP engine 420 mounted on the HWF server 4 is executed (S1113). In step S <b> 1113, the job control unit 413 causes the RIP engine 420 to execute processing as described above under the control of the workflow control unit 418.

  Thereafter, when the workflow process reaches the process in the DFE 100, the job control unit 413 controls the job transmission / reception unit 421 to transmit job data to the DFE 100 according to the control of the workflow control unit 418 (S1114). In step S <b> 1114, the job control unit 413 specifies the individual job reception unit 112 corresponding to the information specified in the JDF information from the plurality of individual job reception units 112.

  When any one of the plurality of individual job receiving units 112 is specified when transmitting job data to the DFE 100, the appropriate individual job receiving unit 112 in the DFE 100 receives the job data. When job data is input to the DFE 100, as described above, processing for generating raster data is executed in the RIP engine 120 of the DFE 100, and output processing by the digital engine 150 is executed (S1115).

  In the DFE 100, when the designated processing is completed, the job receiving unit 111 notifies the HWF server 4 of completion (S1116). Upon receiving the completion notification from the DFE 100 via the job transmission / reception unit 421, the job control unit 413 notifies the workflow control unit 418 of completion. As a result, the workflow control unit 418 makes a post-processing request to the post-processing device 3 to execute the post-processing specified in the workflow after the control by the DFE 100 (S1117).

  In step S <b> 1117, the job control unit 413 controls the job transmission / reception unit 421 according to the control of the workflow control unit 418 and makes a post-processing request to the post-processing device 3. By such processing, the operation of the system according to the present embodiment is completed.

  In the present embodiment, post-processing can be performed by the inline finisher 160 and the post-processing device 3. Since the DFE 100 is connected to the inline finisher 160, detailed information about post-processing performed by the inline finisher 160 can be grasped. Therefore, in the present embodiment, post-processing executed by the inline finisher 160 is handled as processing in which control is executed inside the DFE.

  As described above, an operator using the HWF system operates the client terminal 5 to display a GUI for operating the HWF server 4, inputs data, sets JDF information, and sends job data to the DFE 100. Send. In the GUI displayed on the client terminal 5, parameters for performing RIP processing in the DFE 100 can be set.

  At this time, the RIP engine 420 mounted on the HWF server 4 and the RIP engine 120 mounted on the DFE 100 may have different versions. In such a case, since the HWF server 4 cannot interpret the parameter relating to the RIP process executed only by the DFE 100, the parameter may not be set from the GUI displayed on the client terminal 5.

  At this time, once the job data is transmitted to the DFE 100 and the JDF information of the job data is edited by the DFE 100, the operator of the HWF system can execute a desired print output. However, if the operator of the HWF system knows the details of the RIP process executed only by the DFE 100, or if the RIP process executed only by the DFE 100 is a simple process such as a staple process, the printing of the HWF system is performed. It will reduce efficiency.

  Therefore, in the present embodiment, the setting relating to the RIP process executed only by the DFE 100 can be executed in the HWF server 4 so that the print workflow can be executed efficiently in the HWF system. Hereinafter, with reference to the drawings, a description will be given of a process in the HWF server 4 for setting related to the RIP process executed only in the DFE 100 in the present embodiment.

  The main reason why the setting related to RIP processing executed only by the DFE 100 cannot be executed by the HWF server 4 is that the device information of the DFE 100 includes a description of JDF information that cannot be interpreted by the HWF server 4. First, device information of the DFE 100 according to the present embodiment will be described with reference to FIG.

  FIG. 13 shows device information of the DFE 100 according to the present embodiment. The device information is created by JMF and describes the specifications of the version of JDF information that the DFE 100 supports. Based on the device information received from the DFE 100, the HWF server 4 can grasp the tags of functions that can be specified in the DFE 100, and the configuration of the digital engine 150 and the inline finisher 160 and the functions that can be executed by the tags of these functions. .

  The device information management unit 124 generates device information based on detailed information which is information indicating details of functions executed in the managed DFE 100, digital engine 150, and inline finisher 160. Therefore, the system control unit 410 of the HWF server 4 determines whether or not the inline finisher 160 is connected to the DFE 100 based on whether or not JDF information for the post-processing function is described in the device information.

  For example, when the JDF information for executing the staple function is described in the device information, the system control unit 410 can determine that the inline finisher 160 that executes the staple process is connected to the DFE 100.

  As shown in FIG. 13, the start tag indicating the start of device information describes that the device information is the above-described CIP4-compliant JMF. Furthermore, the start tag includes a tag “A”, and the tag “A” belongs to a namespace identified by a URI (Uniform Resource Identifier) “www.hhh.com/schema/aaa”. , It is shown that this is an extended tag of JDF information extended without conforming to CIP4. Therefore, in this embodiment, all tags starting with “A” included in the JDF information are extension tags.

  “Device list information” defines a set of devices processed by JDF information. “Device specification information” is one of the elements defined in “device list information”, and is information described for each device. In FIG. 13, the DFE 100 is regarded as one device and is described as “Device01”. The individual job receiving unit 112 may be regarded as one device, and “device specification information” may be described.

  In “device specification information”, “Device01”, that is, a function executable by the DFE 100 is described using the tag “DevCaps” or “DevCap” described above. “DevCap” is one of the elements defined in “DevCaps”, and is a tag that defines the specifications of the child elements of the element specified by “DevCaps”.

  In addition, in the element or attribute specified by the “DevCap” tag, “NumberState”, “EnumerationState”, or “BooleanState” can be used as a tag that specifies the value type of the attribute whose name is specified. “NumberState” designates a numeric type, “EnumerationState” designates an enumerated type, and “BooleanState” designates a value type of an attribute whose name is designated by a binary type.

  “AllowedValueList” indicates a range of values that can be specified in the attribute whose name is specified. In the case of “Enumeration State”, values are sequentially described as “Top Left”, and in the case of numeric type, the description is the same as “Enumeration State”, or the lower and upper limits are set as “1 to 4”. Is described.

  “HasDefault” and “DefaultValue” specify a default value that can be specified in the attribute whose name is specified. As for these values, when the corresponding attribute is not included in the JDF information included in the job data input to the DFE 100, the processing setting value designated by “DefaultValue” is described in the JDF information. This is for generating dummy JDF information.

  When “HasDefault” = “false”, there is no default processing setting value, and when the JDF information is edited by the operator's operation, the edited JDF information is directly reflected in the job.

  The fact that the system control unit 410 can interpret the device information shown in FIG. 13 will be sequentially described. Based on the device information shown in FIG. 13, the system control unit 410 has two attributes “A: Rotate” and “A: BindingEdge” in the element “LayoutParallationParams” that specifies imposition-related job attributes in the DFE 100. It is interpreted that it can be specified.

  Further, in the DFE 100, the system control unit 410, “A: Rotate” is an attribute that designates the rotation angle of the image, and can designate a processing setting value within a range of 1 to 4 as a numerical value. "A: BindingEdge" is an attribute for designating the binding width of the paper, and can be designated as either "Top" or "Left". The default processing setting value is "Top". Further, it is interpreted that “Layout Layout Params” can specify two types of child elements “InsertSheet” related to the insertion sheet.

  Furthermore, the system control unit 410 can specify attributes such as “SheetType”, “A: BannerSheet”, and “SheetUsage” in the first child element “InsertSheet”, and “SheetType” specifies the type of inserted paper It is an attribute and can only specify the value “JobSheet” and has no default processing setting value. “A: BannerSheet” can only specify the processing setting value “true”, and the default processing setting value. “SheetUsage” can be specified as either “Trailer” or “Header”, and is interpreted as an attribute having no default processing setting value.

  In addition, the system control unit 410 can specify the attributes “SheetType” and “SheetFormat” in the second child element “InsertSheet”, and “SheetType” is an attribute that specifies the type of insertion sheet. Only the processing setting value “SheeterSheet” can be specified and does not have a default processing setting value. “SheetFormat” is an attribute for specifying the content to be printed on the insertion sheet, and is “Blank” or “ It is interpreted that any one of “Duplicate” can be specified and does not have a default processing setting value.

  Further, the system control unit 410 can specify an attribute “A: Amount” for “ComponentLink”, which is an element associated with “Usage = Output”, and “A: Amount”. "" Can be specified as a numerical value in the range of 1 to 32767, and is interpreted as having 1 as the default processing setting value.

  The system control unit 410 of the HWF server 4 acquires the device information received from the DFE 100 from the device information storage unit 417 via the device information management unit 416. Then, the system control unit 410 causes the UI control unit 412 to display a UI for setting the processing setting value in the attribute of the JDF information included in the device information. The UI displayed on the client terminal 5 by the UI control unit 412 is a setting screen (job setting UI) for performing settings related to processing when outputting print output command information from the HWF server 4 shown in FIG. ).

  FIG. 14 is a diagram showing a job setting UI according to the present embodiment. The job setting UI shown in FIG. 14 is displayed in a grouping or in the same hierarchy for functions related to each other in order to improve user convenience. In the job setting UI illustrated in FIG. 14, for example, there are four groups of “basic”, “layout”, “color”, and “post-processing”, and “rotation”, “binding end”, “ The function setting “Insert paper” is included and displayed.

  As shown in FIGS. 13 and 14, the device information also has a hierarchical structure similar to the job setting UI. For this reason, the hierarchical structure of the device information and the job setting UI is usually similar to some extent. The contents of “Layout Preparation Params” of the device information of FIG. 13 are reflected in the “layout” group of the job setting UI of FIG.

  As described above, in the HWF system, in order to improve the operation efficiency, parameters related to functions executed by the DFE 100 can be set from the job setting UI displayed on the client terminal 5 connected to the HWF server 4. it can. At this time, in order to confirm how the parameters set from the job setting UI by the operation of the operator affect the print result, a preview for displaying the print result is important.

  When the preview is performed, the system control unit 410 can determine only the device information received from the DFE 100 if the name of the function is specified by the JDF information. However, it may not be possible to determine what each element of the function specified by the JDF information included in the device information received from the DFE 100 means.

  For example, when it is known that the system control unit 410 can specify a processing setting value in the range of 1 to 4 with respect to “A: Rotate”, it cannot be determined how the execution result of the job specifying 1 will be. . Therefore, the job execution result cannot be reflected in the preview data generated by the HWF server 4. At this time, in order to reflect the job execution result in the preview data when 1 is specified, the system control unit 410 must be able to interpret the JDF specification used in the DFE 100.

  For example, when “1” is specified in “A: Rotate”, if the system control unit 410 can interpret that 0 degree rotation is indicated, the job setting UI shown in FIG. 14 is based on the device information shown in FIG. Can be reflected in the preview displayed.

  When the system control unit 410 can interpret the JDF specification used in the DFE 100, the system control unit 410 sets a process setting that is a setting value related to processing when outputting print output command information based on the operation of the operator. It is a processing setting value reflecting unit that acquires a value from the UI control unit 412 and executes a processing setting value reflecting step for reflecting the processing setting value in the JDF information. Then, the JDF information reflecting the processing setting value and the PDL information are associated with each other and registered in the job data storage unit 414, and the job is executed. The job is executed according to the processing flow of the entire HWF system described with reference to FIG.

  However, when a plurality of DFEs 100 are connected to the HWF server 4, the DFEs 100 using the JDF specification that cannot be interpreted by the system control unit 410 may be included. On the other hand, in the present embodiment, tag information that can be interpreted only by the DFE 100 included in the device information received from the DFE 100 including the unique JDF specification that cannot be interpreted by the system control unit 410 of the HWF server 4; That is, information on the processing content that is uniquely executed in the DFE 100 is acquired and the job setting UI is displayed.

  Next, the flow of processing for displaying the job setting UI based on the device information will be described with reference to the drawings. FIG. 15 is a flowchart showing a flow of processing for displaying a job setting UI based on device information according to the present embodiment.

  The system control unit 410 extracts and acquires version information of the DFE 100 from the device information received from the DFE 100 using the “A: Version” tag (S1501). If the version of the DFE 100 is a version that can be interpreted by the system control unit 410 based on the acquired version information (S1502 / YES), the system control unit 410 further analyzes the device information received from the DFE 100 to obtain a detailed DFE 100. Device information is acquired (S1503). The version of the DFE 100 that can be interpreted by the system control unit 410 corresponds to, for example, a case where the version of the DFE 100 is smaller than that of the HWF server 4.

  When the DFE 100 is a version that cannot be interpreted by the system control unit 410, the system control unit 410 extracts the device specifications of each element from the device information received from the DFE 100 using the “DevCaps” tag or the “DevCap” tag. (S1504). Therefore, the system control unit 310 functions as a unique process information extraction unit that executes a unique process information extraction step.

  Next, the system control unit 410 indicates which version of the JDF specification added to the DFE 100 is based on the value of the “D: CapVersion” tag or the “A: AddVersion” tag of the child element. Information is acquired (S1505). Then, the system control unit 410 determines whether or not the JDF specification version of the DFE 100 is a version corresponding to the system control unit 410 (S1506).

  When the JDF specification version of the DFE 100 is a version corresponding to the system control unit 410 (S1506 / YES), the system control unit 410 further analyzes the device information received from the DFE 100 to obtain detailed device information of the DFE 100. For example, element or attribute information (name, process setting value that can be specified, default process setting value, etc.) is acquired (S1507), and the acquired device information of the DFE 100 is stored in the device information storage unit 417.

  On the other hand, when the version of the JDF specification of the DFE 100 is a version that is not compatible with the system control unit 410 (S1506 / NO), the system control unit 410 extracts only interpretable tags and analyzes the device information. If there is an element that cannot be previewed, information indicating the non-preview function is added and stored in the device information storage unit 417 (S1508).

  In step S1504, the system control unit 410 executes the processing from step S1405 on all elements or attributes extracted by the “DevCaps” tag or the “DevCap” tag (S1509 / NO). The system control unit 410 determines whether or not all elements extracted by the “DevCaps” tag or “DevCap” tag are compatible with the system control unit 410 (S1509), and based on the result. The job setting UI is displayed on the UI control unit 412.

  The UI control unit 412 displays a job setting UI based on the determination result of S1509 received from the system control unit 410 (S1510). At this time, if the device information includes information indicating that it is a non-preview function, the UI control unit 412 keeps the item for changing the processing setting of the function as described in the device information. Reflect and display on the job setting UI.

  For example, JDF specification functions that cannot be interpreted are displayed on the job setting UI according to the hierarchical structure of the device information. In addition, the UI control unit 412 displays the job setting UI without reflecting it in the preview even if the processing setting value is changed for the function indicated to be a non-preview function.

  Next, a display mode of the job setting UI will be described with reference to the drawings based on device information using the JDF specification that cannot be interpreted by the HWF server 4. FIG. 16 is a diagram illustrating device information using the JDF specification that cannot be interpreted by the HWF server 4 according to the present embodiment. In the following description, it is assumed that the system control unit 410 can interpret the JDF specification version 2.0 in the DFE 100, but cannot interpret the JDF specification version 2.1 in the DFE 100.

  “A: Version” and “A: AddVersion” included in the device information illustrated in FIG. 16 are examples of extension tags of JDF information that are added in the JDF specification of the DFE 100 and describe version upgrade of the DFE 100. The system control unit 410 interprets the processing content corresponding to each of these extension tags, and executes processing control based on the interpretation. An extension tag that can be interpreted by the system control unit 410 can be added when the JDF specification of the HWF server 4 is upgraded.

  In FIG. 16, “A: Version” is an element indicating version information of the DFE 100, and “A: AddVersion” indicates version information of the upgraded DFE 100, that is, a version before the DFE 100 is upgraded. The system control unit 410 interprets that it is an element. Note that “A: AddVersion” is not an essential element, and if there is no element that designates “A: AddVersion”, the system control unit 410 follows the designation of the parent element.

  From the device information of the DFE 100 illustrated in FIG. 16, the system control unit 410 adds “LayoutParameterParams” and child elements or attributes “A: Rotate”, “A: BindingEdge”, and “InsertSheet” in version 2.0. , To interpret that a new attribute “A: ExtendAttribute” and a new element “A: ExtendElement” were added in version 2.1.

  At this time, “A: ExtendAttribute” and “A: ExtendElement” are unique process setting information that is a new attribute or a new element added in the DFE 100 of version 2.1, that is, unique process information. Therefore, the system control unit 410 cannot interpret information on what processing is executed in the DFE 100 by “A: ExtendedAttribute” and “A: ExtendedElement” shown in the region C and the region D of FIG. .

  However, the system control unit 410 determines that “A: ExtendAttribute” and “A: ExtendElement” are version 2.1 DFE100 according to the processing setting values specified in the elements “A: Version” and “A: AddVersion”. It can be interpreted that this is a JDF specification added to.

  Further, for example, “A: ExtendedAttribute” is an attribute included in “LayoutParallationParams”, so that the system control unit 410 sets “A: It can also be interpreted as to which functions of the version 2.0 DFE 100 "ExtendAttribute" and "A: ExtendElement" are related.

  FIG. 17 is a diagram showing a job setting UI displayed by the UI control unit 412 based on the device information shown in FIG. In the device information of FIG. 16, “A: ExtendAttribute” and “A: ExtendElement” are tags of elements included in “LayoutPreparationParams”. Accordingly, the UI control unit 412 displays the job setting UI by including “A: ExtendedAttribute” and “A: ExtendedElement” in the item “layout” as shown in FIG.

  However, as described above, the system control unit 410 cannot interpret the print result depending on the processing setting values specified by “A: ExtendedAttribute” and “A: ExtendedElement”. For this reason, the UI control unit 412 according to the present embodiment displays “A: ExtendedAttribute” and “A: ExtendedElement” as a “non-preview function” on the job setting UI according to the hierarchical structure of the device information. Prevent system operators from getting confused.

  Therefore, the operator of the HWF system can set the function displayed on the job setting UI as the “non-preview function”, but cannot check the preview reflecting the setting on the HWF server 4. However, if the operator knows what processing is executed by the element displayed on the job setting UI as the “non-preview function”, or if it is a simple function such as punching the edge of the paper, the preview It is possible to predict the print output result and set the processing set value without performing the above.

  For example, “A: ExtendAttribute” and “A: ExtendElement” are in the same hierarchy, “A: ExtendAttribute” has “A: attr”, and “A: attr” is the value of “Val1” or “Val2”. Can take. Accordingly, the UI control unit 412 displays these process setting values so as to be set as shown in FIG.

  Then, based on the processing setting value set from the job setting UI in FIG. 17, the system control unit 410 includes the JDF information whose value is specified in the extension tag in the job data and transmits the job data to the DFE 100. FIG. 18 is a diagram showing JDF information in which the processing setting value for the extension tag according to the present embodiment is reflected.

  In the JDF information shown in FIG. 18, the process setting value designated as “5” in “A: ExtendAttribute” and the process setting value designated as “Val2” in “A: ExtendElement” are reflected.

  Then, the system control unit 410 acquires the processing setting value from the UI control unit 412, reflects the processing setting value in the JDF information, associates the JDF information reflecting the processing setting value with the PDL information, and stores the job data. The job is registered in the unit 414 and executed. Note that the job is executed according to the processing flow described with reference to FIG.

  As described above, in the present embodiment, even if the function that cannot confirm the preview reflecting the process setting value from the job setting UI on the HWF server 4, the process setting value is set from the HWF server 4. By generating job data, the print workflow can be performed efficiently.

  FIG. 19 is a diagram illustrating device information to which auxiliary information, which is information indicating processing contents executed by the extension tag displayed on the job setting UI, is added. In the job setting UI of FIG. 17, other elements are displayed in Japanese. On the other hand, for the extension tag element, the name of the JMF description tag included in the device information is displayed as it is. Therefore, it is difficult for the operator to understand what the function of the expansion tag displayed on the job setting UI is.

  Therefore, as shown in FIG. 19, an element “A: AuxiliaryInfo” for designating auxiliary information related to an extension tag and its elements “Lang”, “Name”, “Description”, and the like are described in the device information in the DFE 100. Thus, the auxiliary information of the expansion tag can be displayed to the operator of the HWF system.

  Note that “Name” is a function name, “Description” is a description of the function, and “Lang” is a tag that specifies a language for displaying “Name” and “Description” on the job setting UI. In FIG. 19, it is assumed that the system control unit 410 can interpret the function of each tag of “A: AuxiliaryInfo”, “Lang”, “Name”, and “Description”.

  FIG. 20 shows a job setting UI that displays the value of “Description” when the name of the extension tag is replaced with the contents described in “Name” of FIG. 19 and the name is moved over the mouse.

  Since the system control unit 410 cannot interpret the extension tag due to the version upgrade of the DFE 100, even if the name or description of an attribute or element in a specific language is received by the “Name” and “Description” tags, It cannot be converted. Therefore, it is necessary to enable language designation by the “Lang” element and designation of a plurality of “A: Auxiliary Info”.

  For example, the language information set in the HWF server 4 is added to the JMF information requesting acquisition of device information from the HWF server 4 and transmitted to the DFE 100. The DFE 100 may return an “A: AuxiliaryInfo” tag, which is an expansion tag for supporting the language information, to the HWF server 4 by including the device information in the device information.

  As described above, even when the system control unit 410 cannot interpret the function of the extension tag, the UI control unit 412 does not change the process setting value specified by each element of the “Lang” tag, the “Name” tag, and the “Description” tag. The job setting UI can be displayed on the client terminal 5 based on the above, and the auxiliary tag auxiliary information can be presented to the operator.

  The HWF server 4 is set as a language for displaying a UI indicating the operation of the HWF server 4 among the languages indicated by the value designated by the “Lang” tag when there are a plurality of languages set. The auxiliary tag auxiliary information may be displayed in the job setting UI using the selected language.

  The UI control unit 412 displays the auxiliary tag auxiliary information on the job setting UI based on the information described in the area surrounded by the two-dot chain line in FIG. For example, based on the information described in the area 18B and the area 18C, the UI control unit 412 selects “the value of Y that is a parameter related to the function XX” when the parameter Y is moused over. Is displayed on the job setting UI.

  In addition, when displaying the job setting UI, the UI control unit 412 displays a display that the parameter Y is “a parameter related to the function XX and selects the value of Y” in a pop-up format or a dialog format. May be.

  FIG. 21 is a diagram showing device information including hierarchy designation information that is a description for designating which hierarchy of the job setting UI to display the setting of the extension tag. In consideration of operational efficiency, it is desirable that the expansion tag setting screen is combined with related functions. However, the hierarchical structure of the job setting UI in the HWF server 4 and the hierarchical structure of the device information are basically not completely equal.

  In the job setting UI of FIG. 14, groups of elements for performing settings such as “color” and “post-processing” are displayed, but “Color” and “Finishing” are within the JDF specification range that can be interpreted by the system control unit 410. There is no hierarchy specification information indicating the attribute or element that applies to the tag. For example, “post-processing” is a group in which hierarchical designation information such as “StitchingParams” that is an attribute for performing stapling processing and tags such as “HoleMakingParams” that is an attribute for performing punching processing are collected.

  As described above, it may not be possible to determine which elements of the job setting UI are included in the hierarchy displayed as a group by only the device information. In contrast, in the present embodiment, as shown in the device information in FIG. 21, an “A: Group” tag for designating a hierarchy to be displayed is added to the extension tag. When the DFE 100 interprets the hierarchical structure of the job setting in the job data received from the HWF server 4, the hierarchy specifying information is added by specifying the hierarchy in which the extension tag should be included by using the “A: Group” tag. , And is transmitted to the HWF server 4 as device information.

  In the device information of FIG. 21, the attribute “A: ExtendedAttribute” and the element “A: ExtendedElement” are specified by the “A: Group” tag as elements included in the same group hierarchy as “Layout”, and “DigitalPrintingParams” The element “A: ExtendColor” newly included in “” is designated as an element included in the same group hierarchy as “Color”.

  When the device information in FIG. 21 is received from the DFE 100, the UI control unit 412 has the same “A: ExtendAttribute” and “A: ExtendElement” as the “layout” group corresponding to “Layout” as shown in FIG. The job setting UI is displayed by including “A: Extended Color” in the same hierarchy as the “color” group corresponding to “Color”.

  Further, based on the information described in the areas C and D surrounded by the one-dot chain line in FIG. 21, the UI control unit 412 can set “ExtendAttribute” to “designate in the range of 0 to 10,000”. A job setting UI in which “ExtendElement” can specify “Val1 or Val2 and the default value is Val1” is displayed. Thus, even if the system control unit 410 of the HWF server 4 cannot understand the function of the extension tag, the job setting UI in which the extension tag is arranged in an appropriate hierarchy can be displayed.

  As described above, in the present embodiment, the setting of the processing setting value related to the function that cannot be interpreted by the HWF server 4 and executed by the DFE 100 is displayed on the client terminal 5 connected to the HWF server 4. This can be done from the job setting UI. At this time, the processing setting value set from the job setting UI by the operation of the operator is transmitted to the DFE 100 as job data by the job transmission / reception unit 421, and the DFE 100 executes RIP processing according to the received job data.

  Next, in-DFE processing executed by the DFE 100 based on job data received from the HWF server 4 in S1115 of FIG. 11 will be described with reference to the flowchart of FIG. As shown in FIG. 23, first, the individual job receiving unit 112 specified when the job data is transmitted from the HWF server 4 receives the job data (S2301). When receiving the job data, the individual job receiving unit 112 updates the JDF information so that the individual settings set for itself are reflected in the job data (S2302).

  The job data received by the individual job receiving unit 112 is input to the system control unit 113. The system control unit 113 stores the input job data in the job data storage unit 114 according to the setting, and performs a preview process or the like via the UI control unit 115 according to the operation of the operator.

  The system control unit 113 inputs job data to the job control unit 116 at the job execution timing in the DFE 100 such as an operator's operation or reaching the set execution time. The job control unit 116 inputs job data to the JDF analysis unit 117 and generates job attributes within DFE (S3203).

  Then, the job control unit 116 generates RIP parameters as described in FIG. 8 (S2304). Further, when generating the RIP parameter, the job control unit 116 inputs necessary information to the RIP unit 118 to execute the RIP process. Thus, first, the RIP control unit 119 performs the parameter conversion described above (S2305).

  Then, the RIP control unit 119 designates the converted parameter and causes the RIP engine 120 to execute the RIP process (S2306). Thereby, raster data is created by the RIP engine 120. When raster data is generated by the RIP engine 120, the RIP unit 118 stores the generated raster data in the image storage unit 122 (S2307), and ends this processing.

  Next, the RIP process in S2306 of FIG. 23 will be described with reference to FIG. As shown in FIG. 24, first, the control unit 201 executes an initialization process based on an initialization request to the input unit 202 (S2401). In S2401, in the case of the example of FIG. 9, the RIP parameter analysis unit 203 receives and analyzes the RIP parameter, and as described above, an extension unit that executes processing among the respective extension units included in the RIP engine 120, Determine the order. In addition, the format of data generated as a result of processing is determined.

  In the case of the example of FIG. 10, the job attribute analysis unit 214 receives and analyzes JDF information and PDL information, and determines an extension unit for executing processing and the order thereof. In addition, the format of data generated as a result of processing is determined. Subsequently, in the example of FIG. 10, the control unit 201 causes the RIP status analysis unit 215 to perform status analysis.

  In the status analysis, the RIP status analysis unit 215 refers to the “RIP status” shown in FIG. 3 and selects one item of RIP internal processing (S2402). If the status is “Done” (S2403 / YES), the corresponding extension unit is excluded from the execution target extension units determined in S1401 (S2404). On the other hand, if “NotYet” (S2403 / NO), no particular processing is performed.

  The RIP status analysis unit 215 repeats the process for all the RIP internal process items until the process from S2202 is completed (S2405 / NO). After the RIP status analysis unit 215 completes the processing from S2402 for all the RIP internal processing items (S2405 / YES), when the input unit 202 acquires the RIP processing execution request (S2406 / YES), the control unit 201 Causes the extension units to execute processing in order (S2407).

  In S2407, processing is requested only for the extension units determined in the processing of S2401 and not excluded by the processing of S2404. Further, processing is requested in accordance with the processing order determined in S2401. When the processing is executed by the extension unit and raster data is generated, the output unit 213 outputs the processing result (S2408). By such processing, the processing by the RIP unit 118 is completed.

  In the present embodiment, only the case of the RIP engine 120 shown in FIG. 10 has been described. This is because if the HWF server 4 and the DFE 100 share RIP processing, it is necessary to perform status analysis. That is, when the RWF process is shared between the HWF server 4 and the DFE 100, it is necessary to exclude the RIP process already executed by the HWF server 4 on the DFE 100 side.

  Therefore, when the RIP processing is shared between the HWF server 4 and the DFE 100, the JDF analysis by the JDF analysis unit 117 is performed on the DFE 100 side, the status analysis is performed by the RIP status analysis unit 215, and the necessary RIP internal processing is performed. May be judged.

  In the processing described above, an input device that can transmit a print job to each of the plurality of individual job reception units 112 can be assigned in advance. In such a case, the DFE 100 refers to the device information of the HWF server 4 and the input device that is the transmission source of the print job, and determines the individual job reception unit 112 that inputs the print job.

1 Digital Printer 2 Offset Printer 3 Post-Processing Device (Nearline Finisher)
4, 4a, 4b HWF server 5, 5a, 5b Client terminal 10 CPU
20 RAM
30 ROM
40 HDD
50 I / F
60 LCD
70 Operation unit 80 Bus 100 DFE
101 Network I / F
DESCRIPTION OF SYMBOLS 102 Display 111 Job receiving part 112 Individual job receiving part 113 System control part 114 Job data storage part 115 UI control part 116 Job control part 117 JDF analysis part 118 RIP part 119 RIP control part 120 RIP engine 121 External processing part 122 Image storage part 123 Printer Control Unit 124 Device Information Management Unit 125 Device Information Communication Unit 150 Digital Engine 160 Inline Finisher 200 CTP
DESCRIPTION OF SYMBOLS 201 Control part 202 Input part 203 RIP parameter analysis part 204 Preflight processing part 205 Normalization processing part 206 Mark processing part 207 Font processing part 209 CMM processing part 210 Trapping processing part 211 Calibration processing part 212 Screening processing part 213 Output part 214 Job attribute Analysis unit 215 RIP status analysis unit 216 RIP status management unit 217 Layout processing unit 218 Rendering processing unit 400 HWF controller 401 Network I / F
410 System control unit 411 Data reception unit 412 UI control unit 413 Job control unit 414 Job data storage unit 415 Device information communication unit 416 Device information management unit 417 Device information storage unit 418 Workflow control unit 419 Workflow information storage unit 420 RIP engine 421 Job Transmitter / receiver

JP2015-194994A

Claims (7)

An image for controlling execution of the image forming output according to processing setting information including information for setting processing contents for executing image forming output based on command information received from a processing execution control device that controls execution of a plurality of processes A control program for setting the processing setting information transmitted to the forming output control device,
A unique process information generating step that includes unique process information indicating process details unique to the image formation output control device, and generates the process setting information;
A transmission control step of transmitting the process setting information to the process execution control device;
Is executed by the image forming output control device,
A unique process information extracting step for extracting the unique process information from the process setting information;
A display control step for displaying a setting screen for setting a processing setting value of the extracted unique processing information;
A process setting value reflecting step of reflecting the set process setting value in command information transmitted to the image forming output control device in order to execute the image forming output;
Is executed by the process execution control device. In the unique processing information generation step,
Including auxiliary information for displaying the processing content executed by the unique processing information on the setting screen, generating the processing setting information,
In the display control step,
The control program according to claim 1, wherein the auxiliary information can be displayed on the setting screen. In the display control step,
The control program according to claim 2, wherein the auxiliary information is displayed in a language set as a language for displaying the setting screen in the processing execution control device. In the unique processing information generation step,
Including hierarchy designation information for designating a hierarchy in which the unique process information is displayed on the setting screen, and generating the process setting information,
In the display control step,
2. The control program according to claim 1, wherein a process setting value of the unique process information is displayed so as to be set on a hierarchy of the setting screen designated based on the hierarchy designation information. The process setting information transmitted to the image forming output control apparatus that controls the execution of the image forming output in accordance with the process setting information including information for setting the processing content for executing the image forming output controls the execution of a plurality of processes. A program for setting in the processing execution control device,
A unique process information extraction step for extracting the unique process information from process setting information including unique process information indicating the process content unique to the image formation output control device;
A display control step for displaying a setting screen for setting a processing setting value of the extracted unique processing information;
A process setting value reflecting step for reflecting the set process setting value in command information transmitted to cause the image forming output control apparatus to execute the image forming output;
A program characterized by having executed. The image formation according to process setting information including a process execution control device that controls execution of a plurality of processes, and information that sets processing contents for executing image formation output based on command information received from the process execution control device An image forming output system including an image forming output control device for controlling execution of output,
The image forming output control device includes:
A unique processing information generation unit that includes unique processing information indicating processing content unique to the image forming output control device, and generates the processing setting information;
A transmission control unit for transmitting the process setting information to the process execution control device;
Including
The process execution control device includes:
A unique process information extraction unit that extracts the unique process information from the process setting information;
A display control unit for displaying a setting screen for setting a processing setting value of the extracted unique processing information;
A process setting value reflecting unit for reflecting the set process setting value in the command information;
Including
The image forming output control device includes:
A drawing information generation unit that generates drawing information based on the command information in which a processing setting value of the unique processing information is reflected in a drawing information generation unit that generates drawing information that is information of an image to be formed and output. When,
An image forming output system comprising: The process setting information transmitted to the image forming output control apparatus that controls the execution of the image forming output according to the process setting information including information for setting the processing content for executing the image forming output is set as one of a plurality of processes. A process execution control device for
A unique process information extracting unit that extracts the unique process information from process setting information including unique process information indicating the process content unique to the image formation output control device;
A display control unit for displaying a setting screen for setting a processing setting value of the extracted unique processing information;
A process setting value reflecting unit that reflects the set process setting value in command information transmitted to cause the image forming output control apparatus to execute the image forming output;
A process execution control device comprising: