JP6477359B2 - Image processing system, process execution control device, image processing method, and control program - Google Patents

Description

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

  A method of defining and controlling all processes related to the generation of a printed material is used by an information format called JDF (Job Definition 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. However, each of the offset printer and the digital printer is provided with a RIP (Raster Image Processor) engine that generates raster data, which is data that is finally referred to in print output, based on the print data. As a result, since different RIP engines are used, there may be a difference in print results.

  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, and then a CTP (Computer Toe) that creates a version for the offset printer. Data is transferred to (Plate).

  On the other hand, in the case of a digital printer, a configuration called DFE (Digital Front End) generally receives print data, performs RIP processing, and causes the printer engine to execute print output. Therefore, it is required that the processing result by the RIP engine for generating data to be transferred to the CTP and the processing result by the RIP engine installed in the DFE are as identical as possible.

  Also, in a system related to printing, not limited to the HWF system, a print job that has been executed once may be stored and reused for similar print output. A method has been proposed for improving convenience when performing print output based on resources stored on a network (see, for example, Patent Document 1).

  In Patent Document 1, when the format of information included in a network resource specified by a URL or the like is a predetermined format such as PDF, a confirmation dialog as to whether or not to perform print output is displayed. Convenience has been improved.

  Regarding the difference in the print results described above, the RIP engine mounted on the HWF server and the RIP engine mounted on the DFE are made to correspond to each other so that the same result can be obtained with any RIP engine. Can be solved. On the other hand, when each of the HWF server and the DFE is configured as an information processing apparatus as described above, it is necessary to make the location for storing the print job more efficient with respect to the above-described reuse of the print job.

  Since the print job is first input to the HWF server in principle, if the print job is stored in the HWF server, it is possible to cause both the offset printer and the digital printer to perform reprinting. In this case, the DFE storage area is not used effectively, and the storage area on the HWF server side is compressed.

  On the other hand, it is conceivable to save the print job on the DFE side, but if the print job is also saved on the HWF server side, the same print job will be saved twice on the system and stored. The use of the area becomes inefficient. In contrast, if the print job on the HWF server side is deleted and the print job is stored only on the DFE side, the inefficient use of the storage area described above can be eliminated.

  However, in the case where the print job is stored only on the DFE side, the print job stored in a certain DFE is reused to execute the print job via another DFE based on the control of the HWF server. , Network traffic increases. That is, when a print job is reused by the method described in Cited Document 1, the print job is downloaded from the DFE in which the print job is stored to the HWF server, and then the print job is transmitted to another DFE. As a result, network traffic increases.

  In addition, the remaining capacity of storage devices mounted on each device included in the system, such as an HWF server or DFE, varies according to the operation of the system. For this reason, the determination as to whether the print job is stored in either the HWF server or the DFE as described above should be determined according to the operation status of the system. The work burden is large.

  SUMMARY An advantage of some aspects of the invention is that a system is configured when a print job is stored and reused in a system that manages a plurality of image forming apparatuses and performs print output. The purpose is to efficiently operate the storage capacity of each device and reduce network traffic when reusing print jobs.

  In order to solve the above problems, one aspect of the present invention is an image processing system that sequentially executes a plurality of predetermined processes, a process execution control device that controls execution of the plurality of processes, and image formation A plurality of image forming output control devices for controlling execution of output, wherein the processing execution control device controls the execution of the plurality of processes according to command information, and one of the plurality of processes. A control-side drawing information generation unit that generates drawing information, which is information that the image forming apparatus refers to when forming an image, based on output target image information that is image information of an image formation output target; A command information management unit that manages command information in association with information indicating a storage destination of output target image information that is image information output in the command information, and a plurality of the image formation output controls Output target image information from a storage destination device that is a storage destination of the output target image information to an execution destination device that is another image formation output control device and causes the image forming device to execute image formation output. An image acquisition control unit that controls transfer based on the command information that has already been executed, and the image formation output control device is a drawing information generation unit corresponding to the control side drawing information generation unit, An output-side drawing information generation unit that generates the drawing information based on output target image information, and an execution control unit that causes the image forming apparatus to execute image formation output based on the drawing information generated by the output-side drawing information generation unit And the instruction information management unit determines a storage destination of the output target image information related to the instruction information based on a state of each of the storage destination device and the execution destination device. It decides to change al the execution destination device, and updates the information indicating the storage destination of the output target image data.

  According to the present invention, when a print job is stored and reused in a system that manages a plurality of image forming apparatuses and performs print output, the storage capacity of each apparatus constituting the system is efficiently operated, Network traffic when reusing print jobs can be reduced.

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 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. It is a figure which shows the content of the job data which concern on embodiment of this invention. It is a figure which shows the reference table of the job data which concerns on embodiment of this invention. It is a sequence diagram showing an aspect of a job data reuse operation according to an embodiment of the present invention. It is a sequence diagram showing an aspect of a job data reuse operation according to an embodiment of the present invention.

  Embodiments of the present invention will be described below with reference to the drawings. In this embodiment, an image processing system capable of controlling both printers via the same server in a system in which an offset printer and a digital printer are mixed will be described. Such a system is called an HWF (Hybrid Work Flow) system.

  The HWF system according to the present embodiment includes a RIP (Raster Image Processor) engine that is shared by a server and a DFE (Digital Front End) that controls the digital printer when the digital printer is operated. When a print job input to the system is saved and reused in any of the devices that make up the system, storage capacity is efficiently used and network traffic is reduced when the print job is reused. This is the gist of the present embodiment.

  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 the present embodiment includes a digital printer 1a, 1b, an offset printer 2, a post-processing device 3, an HWF server 4a, 4b (hereinafter referred to as “HWF server 4”), a client terminal. 5a and 5b (hereinafter collectively referred to as “client terminal 5”) are connected via a network.

  The digital printers 1 a and 1 b (hereinafter collectively referred to as “digital printer 1”) are printers that perform image formation output without using a plate, such as an electrophotographic method and an inkjet method, and include a DFE 100 and a digital engine 150. The DFE 100 functions as an image formation output control device that is a control unit for causing the digital engine 150 to execute print output. The digital engine 150 functions as an image forming 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, and bookbinding on the paper printed out 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 submission of 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 of 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. Such a configuration is one of the gist according to the present embodiment.

  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, the hardware configuration of information processing apparatuses 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, a 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 (not shown). A functional block that realizes 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 specifying a position adjustment value of an image to be output.

  “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 value related to the adjustment of the creep position.

  “Margin information” is information for designating values related to margins such as fit boxes and gutters. “Center crop mark information” of “Crop mark information” is information for specifying a value related to the center crop mark. “Corner crop mark information” is information for designating a value related to a 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 is updated to “Done” when each process is executed.

  “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, information specifying any of a plurality of RIP engines installed in the DFE 100 is included, such as “DFE (Engine A)”.

  “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.

  By adding such JDF information to the image data to be printed, a print job in the system according to the present embodiment is generated. Such a print job is accompanied by various parameter settings as shown in FIG. 3, and a certain amount of work by the user is required for generation. Accordingly, when performing the same print output, the burden on the user can be reduced by storing and reusing a print job that has been generated once and executed.

  Therefore, in the system according to the present embodiment, the print job is stored in either the HWF server 4 or the DFE 100. One of the essences according to this embodiment is to prevent the use of a storage area efficiently during the storage of such a print job and the generation of unnecessary traffic during the reuse of the print job.

  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 a job 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.

  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, for example, data in PDL (Page Description Language) format such as PDF (Portable Document Format) and PostScript.

  In addition, the print target data 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 contents 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 job data divided in this way 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.

  When new job data is registered in the job data storage unit 414 in this way, the system control unit 410 causes the job management unit 430 included in the job control unit 413 to generate a job data reference table. The job data reference table is information indicating a list of job data stored in the HWF system and information indicating an apparatus in which each job data is stored. Managing job data using this job data reference table is one of the gist according to the present embodiment. Details will be described later.

  The device information management unit 416 manages information by acquiring 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 them 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.

  The device information communication unit 415 periodically acquires information on other devices included in the system via the network I / F 401. As a result, the device information management unit 416 periodically updates the information of other devices stored in the device information storage unit 417, so that even if the information of other devices changes dynamically, the device information storage unit The information stored in 417 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. Each process defined in the workflow has its execution order determined in advance, and in order to maintain the order, the process is controlled to proceed to the next process when the previous process is completed.

  In other words, what is stored in the workflow information storage unit 419 is workflow information obtained by combining the respective processes that can be executed in the HWF system 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 in accordance with the specified execution order according to the specified workflow information or newly generated workflow information. In other words, the workflow control unit 418 and the job control unit 413 function as a process execution control unit in conjunction with each other.

  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 plurality of RIP internal processes performed by the RIP engine is executed by the HWF server 4 or the DFE 100.

  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 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 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 includes a network I / F 101, a display 102, and a DFE controller 110, and a plurality of RIP engines are mounted inside the DFE controller 110. 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 a plurality of different RIP engines are included in the plurality of HWF servers 4a and 4b, a plurality of RIP engines are mounted on the DFE 100 corresponding to the respective RIP engines.

  The job receiving unit 111 includes a plurality of individual job receiving units 112 therein. The individual job receiving unit 112 receives job data from the HWF server 4 via the network I / F 101. The plurality of individual job reception units 112 correspond to a plurality of RIP engines installed in the DFE 100, respectively. The individual job receiving unit 112 functions as an individual receiving unit.

  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 designated RIP engine receives job data.

  The job data can be input to the DFE 100 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 receiving unit 111 creates a dummy JDF and assigns JDF information to the job data. .

  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. That is, the RIP engine installed in the DFE 100 and the individual job receiving unit 112 in which the job content is set are provided, and the job is executed with the preset content by designating one of the individual job receiving units 112. It becomes possible.

  One of the possible settings in the individual job receiving unit 112 according to the present embodiment is “pass-through mode”. This “pass-through mode” does not perform JDF information analysis processing by the JDF analysis unit 117, which is a JDF information analysis function provided separately from the RIP engine in the DFE 100, and executes JDF information analysis in the RIP engine. Mode.

  With such a function, it is possible to use JDF information in a format not supported by the JDF analysis unit 117, or to use a RIP engine that is difficult to provide a JDF analysis function outside the RIP engine in the HWF server 4 and the DFE 100. It becomes. In the present embodiment, the above-described “pass-through mode” is used when the RIP engine 420 mounted on the HWF server 4 and the RIP engine 120 mounted on the DFE 100 share processing. The same RIP engine 120 corresponding to the RIP engine 420 is used as the output side drawing information generation unit.

  When the RIP process is distributed to the HWF server 4 and the DFE 100, it is preferable that the HWF server 4 and the DFE 100 are not considered as much as possible and are executed as a series of processes. Therefore, when data that has been processed halfway in the HWF server 4 is input to the DFE 100, the same JDF analysis processing as when unprocessed job data is input is omitted, and processing is continued as processing in the HWF server 4. Preferably it is performed.

  In the present embodiment, since the same RIP engine corresponding to the HWF server 4 and the DFE 100 is mounted, it is possible to suitably realize such control of RIP processing. In such a case, since it is preferable that the data processed by one RIP engine is directly transferred to the other RIP engine, such control is preferably realized by the “pass-through mode” described above. I can do it.

  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 contents to reflect the target JDF information, and stores the updated JDF information in the job data storage unit 114.

  Furthermore, in this embodiment, job data is stored in the job data storage unit 114 even when job data is stored in the DFE 100 for reuse of job data. In this case, the system control unit 113 acquires a job data storage request via the network and causes the job data storage unit 114 to store the job data in accordance with the request.

  Further, when storing job data in the job data storage unit 114, the system control unit 113 stores the job data reference table in the job management unit 130. In addition, the system control unit 113 refers to the job management unit 130 when print output is executed based on job data acquired from another DFE 100, regardless of whether or not the job data is stored in the job data storage unit 114. Remember the table.

  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 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 includes JDF analysis processing by the JDF analysis unit 117, RIP processing by the RIP unit 118, and control processing of the digital engine 150 by the printer control unit 122.

  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. That is, the JDF analysis unit 117 functions as a processing setting information conversion unit.

  On the other hand, when “pass-through mode” is specified as described above, the job control unit 116 inputs the JDF information included in the job data acquired from the system control unit 113 to the RIP unit 118 as it is. The designation of “pass-through mode” is described in the JDF information by the individual job receiving unit 112, for example. In addition, when “pass-through mode” is designated by the individual job receiving unit 112, designation of “page mode” and “sheet mode” is also described according to the designated RIP engine 120.

  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”, “page mode”, “sheet mode”, and the like are 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 referred to 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”.

  On the other hand, in the “pass-through mode”, the job control unit 116 generates RIP parameters based on JDF information and PDL information or intermediate data. In this case, information for referring to the corresponding JDF information item is set in each item constituting the RIP parameter.

  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.

  In the case of “pass-through mode”, “pass-through mode” is designated in “RIP control mode”. However, this is an example, and “pass-through mode” may be described in an item other than “RIP control mode”.

  Further, the job control unit 116 sets “RIP engine identification information” in the RIP parameter. “RIP engine identification information” is information for identifying a 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 as such. 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 this way.

  In the RIP unit 118, the RIP control unit 119 controls a plurality of RIP engines 120, and executes RIP internal processing based on the input RIP parameters to generate raster data. Here, the RIP control unit 119 according to the present embodiment has a function to cope with the possibility that the system according to the present embodiment may receive print jobs from a plurality of different HWF servers 4.

  Different types of HWF servers 4 may have different data handling methods in print jobs. For example, the difference is “RIP control mode” such as “page mode” and “sheet mode” described above. In the case of the RIP engine 120 corresponding to the “page mode”, the data of the original page corresponding to the number of aggregations is specified in order for the aggregation printing.

  On the other hand, in the case of the RIP engine 120 corresponding to the “sheet mode”, all the data of the original page before aggregation is designated and the RIP process is executed. That is, the parameter designation method for the RIP engine 120 is different. Such a difference is not limited to the “RIP control mode”. For example, it occurs due to differences in the format and handling method of the original data, such as handling the margins of the original data.

  In order to deal with such a difference, the RIP control unit 119 according to the present embodiment performs a conversion process of a parameter designated for the RIP engine 120 in accordance with the RIP engine 120 that executes the RIP process. For example, when data corresponding to “page mode” is input to the RIP engine 120 corresponding to “sheet mode”, the parameter described in “page mode” is converted to “sheet mode”. The function of the RIP engine 120 will be described in detail later.

  The image storage unit 121 is a storage unit that stores raster data generated by the RIP engine 120. The image storage unit 121 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 122 is connected to the digital engine 150 and reads out raster data stored in the image storage unit 121 and transmits the raster data to the digital engine 150 to execute print output. Further, finishing information included in the job attributes within DFE is acquired from the job control unit 116, thereby performing control for finishing processing.

  The printer control unit 122 can acquire information of the digital engine 150 itself by exchanging information with the digital engine 150. For example, in the case of the CIP4 standard, a standard called DevCaps for transmitting / receiving device specification information to / from a printer is defined as a standard for JDF information. 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 123 manages device information that is information on the DFE 100 itself and the digital engine 150. The device information includes information on the RIP engine 120 included in the RIP unit 118 and information on the individual job reception unit 112 configured in the job reception unit 111. The information of the individual job receiving unit 112 includes the above-described “pass-through mode” information.

  The device information communication unit 124 exchanges 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). 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 is controlled by the printer control unit 122 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. 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 processing set next to the print output by the DFE 100, for example, post-processing by the post-processing device 3 is available.

  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.

  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. In addition, the format of data generated as a result of these processes determines any of a raster image, preview image, 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. The trapping process is to expand each color area so that the gap is filled in order to prevent gaps from occurring in the boundary part when there is a positional deviation 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 shown 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 by 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 the 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 122. 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 processing results 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 processing unit, the corresponding extension unit is excluded from the processing 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, a plurality of RIPs mounted in the DFE 100 such as “DFE (Engine A)” and “DFE (Engine B)” may be used. The engine 120 may be used properly. Since the control unit 201 cannot entrust processing to an extension unit of another RIP engine, it is processed by the job control unit 116.

  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 internal 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 processing order within the RIP. As a result, “Engine A” and “Engine B” are selectively used to execute RIP internal processing.

  At this time, as a method for executing only the designated process in each engine, information on “RIP status” can be referred to. That is, only the designated 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”.

  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. At least processing units related to raster data generation, such as the mark processing unit 206, the font processing unit 207, the layout processing unit 217, and the rendering processing unit 218, may be shared. Note that the processing unit related to the generation of raster data is shared in a minimum configuration, and may be shared for other processing units.

  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. Accordingly, 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. As a result, as described above, the job reference table is registered by the job management unit 430. Here, since the job data is stored in the HWF server 4, the HWF server 4 is designated as an apparatus in which the job data is stored.

  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 GUI of the client terminal 5, in the input field for designating “RIP device designation” information shown in FIG. 3, it is possible to select which RIP engine is to be executed when the DFE is executed. 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 “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 specifying the contents of the workflow as shown in FIG. 5 and information 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 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).

  In S1111, information on the remaining capacity of the storage area in the DFE 100 of the designated device, that is, the digital printer 1a or 1b is also acquired. Based on the acquired information, the job management box 123 determines the storage location of the job data requested to be executed. For example, the usage rate of the storage capacity in the HWF server 4 is compared with the usage rate of the storage capacity in the DFE 100 that is the job data transmission destination, and the lower usage rate is determined as the job data storage destination. If the transmission destination of the job data is determined as the storage destination by such determination, the information is described in the JDF information.

  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, RIP processing and output processing by the digital engine 150 are executed in the DFE 100 (S1115). As described above, when the DFE 100 that is the job data transmission destination is determined as the job data storage destination, the job data is stored in the DFE 100 based on the command described in the JDF information.

  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). When job data is stored on the DFE 100 side, the system control unit 113 deletes corresponding job data from the job data storage unit 114. At this time, the data deleted from the job data storage unit 114 is only data related to an output target image having a relatively large data capacity among various data constituting the job data. Details will be described later.

  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.

  Next, the intra-DFE processing in S1115 of FIG. 11 will be described with reference to the flowchart of FIG. As shown in FIG. 13, first, the individual job receiving unit 112 designated when transmitting job data from the HWF server 4 receives the job data (S1301). When the individual job receiving unit 112 receives the job data, the individual job receiving unit 112 updates the JDF information so that the individual setting set for itself is reflected in the job data (S1302).

  The above-mentioned “pass-through mode” setting is also reflected in S1302. The job data reflecting the individual settings 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 refers to the input job data and confirms whether or not it is in the pass-through mode (S1303). As a result, when the mode is not the pass-through mode (S1303 / NO), the job control unit 116 inputs job data to the JDF analysis unit 117 and generates job attributes within DFE (S1304).

  As a result of the confirmation in S1303, when it is in the pass-through mode (S1304 / YES), or when the JDF conversion is completed and the job attribute within DFE is generated, the job control unit 116 generates the RIP parameter (S1305). If it is not the pass-through mode, the RIP parameters as described in FIG. 8 are generated in S1305. On the other hand, in the pass-through mode, RIP parameters including information other than “input / output image information” among the information shown in FIG. 8 are generated, and JDF information is referred to for other portions.

  When the job control unit 116 generates the RIP parameter, the job control unit 116 inputs necessary information to the RIP unit 118 to execute the RIP process. Thereby, first, the RIP control unit 119 performs the parameter conversion described above (S1306). Then, the RIP control unit 119 designates the converted parameter and causes the RIP engine 120 to execute the RIP process (S1307). Thereby, raster data is created by the RIP engine 120.

  In step S1305, as described above, RIP parameters are generated for each RIP engine based on the “RIP device designation” information shown in FIG. In step S1307, RIP processing is sequentially executed for each generated RIP parameter to generate raster data.

  When raster data is generated and acquired from the RIP unit 118, the job control unit 116 inputs the raster data to the printer control unit 122, and causes the digital engine 150 to execute print output (S1308). By such processing, the processing within DFE is completed.

  Next, the RIP process in S1307 of FIG. 13 will be described with reference to FIG. As shown in FIG. 14, first, the control unit 201 executes an initialization process based on an initialization request to the input unit 202 (S1401). In S1401, 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 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 (S1402). If the status is “Done” (S1403 / YES), the corresponding extension unit is excluded from the execution target extension units determined in S1401 (S1404). On the other hand, if “NotYet” (S1403 / NO), no particular processing is performed.

  The RIP status analysis unit 215 repeats the processing until the processing from S1402 is completed for all the RIP internal processing items (S1405 / NO). After the RIP status analysis unit 215 completes the processing from S1402 for all the RIP internal processing items (S1405 / YES), when the input unit 202 acquires the RIP processing execution request (S1406 / YES), the control unit 201 Causes each extension unit to execute processing in order (S1407).

  In S1407, processing is requested only for the extension units determined in the processing of S1401 and not excluded by the processing of S1404. Further, processing is requested according to the processing order determined in S1401. When the processing is executed by the extension unit in this way and raster data is generated, the output unit 213 outputs a processing result (S1408). By such processing, the processing by the RIP unit 118 is completed.

  In the present embodiment, the case of the processing of S1402 to S1405, that is, the case where the status analysis processing is executed only in the case of the example of FIG. 10, that is, the case of the RIP engine 120 corresponding to the pass-through mode is taken as an example. Yes. This is based on the fact that the status analysis process is required when the HWF server 4 and the DFE 100 share the RIP process as described above.

  In such a case, using the same RIP engine installed in the HWF server 4 and the DFE 100, the RIP process is executed as a series of processes without being aware of the boundary between the two. Accordingly, it is preferable that the data processed by the RIP engine 420 in the HWF server 4 is directly input to the RIP engine 120 in the DFE 100, and a pass-through mode that does not pass through the JDF analysis unit 117 provided outside the RIP engine is suitable.

  However, this is merely an example, and even when the mode is not the pass-through mode, if the RIP process is shared between the HWF server 4 and the DFE 100, it is necessary to perform status analysis. That is, when RIP processing is shared between the HWF server 4 and the DFE 100, it is necessary to exclude RIP processing already executed in the HWF server 4 on the DFE 100 side.

  Therefore, even if the RIP engine 120 does not support the pass-through mode, the RIP status analysis unit 215 may be provided in order to share the RIP processing between the HWF server 4 and the DFE 100. In other words, even if the HWF server 4 and the DFE 100 share the RIP processing, it is necessary to perform the status analysis by the RIP status analysis unit 215 after performing the JDF analysis by the JDF analysis unit 117 on the DFE 100 side. RIP internal processing may be determined.

  In the HWF system according to the present embodiment, the RIP engine 120 corresponding to the RIP engine 420 mounted on the HWF server 4 is mounted on the DFE 100. Therefore, there is a difference between the raster data of the print job processed by the RIP engine 420 for output by the offset printer 2 and the raster data of the print job processed by the RIP engine 120 for output by the digital printer 1. Does not occur. Accordingly, it is possible to reduce the difference in printing results between different types of image forming apparatuses.

  In addition, since a plurality of HWF servers 4 are provided, various data having different parameter designation formats for RIP processing are input. In this case, it is necessary to change the parameter designation mode according to each format, and a mode in which such a function is assigned to the job control unit 116 shown in FIG. 6 is conceivable. However, since the job control unit 116 is related to other modules that are major elements in the DFE 100, such as the system control unit 113 and the printer control unit 122, when the function of the job control unit 116 is expanded, the entire system The impact on

  In contrast, in the DFE 100 according to the present embodiment, the RIP control unit 119 performs parameter conversion based on control from the job control unit 116. That is, the RIP control unit 119 functions as a control value conversion unit. Therefore, the adverse effects caused by the function expansion of the job control unit 116 as described above are eliminated, and the function expansion of the RIP control unit 119 can cope with a new parameter designation format without greatly affecting the entire system. Is possible.

  Next, job data storage and reuse modes according to the present embodiment will be described. FIG. 15 is a diagram illustrating a configuration of job data according to the present embodiment. As shown in FIG. 15, the job data according to the present embodiment includes “JDF information” described in FIG. 3, “PDL information” and “Contents information” which are image information to be output for image formation.

  “Contents information” is information on a mark added to an image in mark processing in the RIP engine processing and information on an ICC (International Color Consortium) profile. Of the information shown in FIG. 15, “PDL information” and “Contents information” are used as actual data having a relatively large amount of information. Therefore, as described above, when job data is deleted from the job data storage unit 114 in the HWF server 4, “PDL information” and “Contents information” are deleted.

  FIG. 16 is a diagram showing an example of a job data reference table according to the present embodiment. As shown in FIG. 16, in the reference table according to the present embodiment, “system job reference information” and “real job reference information” are associated with “job ID” that uniquely identifies job data in the HWF system. It has been.

  “System job reference information” is information indicating a job data storage location in the HWF server 4. “Real job reference information” is information indicating a storage location of job data including “PDL information” and “Contents information” described in FIG. The job data stored in the job data storage unit 414 and managed as shown in FIG. 16 is already executed job data. Accordingly, the job management unit 430 that holds information as shown in FIG. 16 functions as a command information management unit.

  As described with reference to FIG. 15, even when job data is stored on the DFE 100 side, only “PDL information” and “Contents information” are deleted from the information included in the job data on the HWF server 4 side. "JDF information" is left. Therefore, regardless of the presence / absence of “PDL information” and “Contents information”, job data is stored in the HWF server 4 and the storage destination is “system job reference information”.

  “Real job reference information” is the same as “system job reference information” when real data is stored in the HWF server 4. On the other hand, when storing job data on the DFE 100 side, the “real job reference information” is information for designating a storage area on the DFE 100 side.

  As shown in FIG. 1, in the HWF system according to the present embodiment, a plurality of HWF servers 4 are provided. Therefore, the input of job data is either the HWF server 4a or the HWF server 4b. The reference table shown in FIG. 16 is managed by the job management unit 430 in each of the HWF server 4a and the HWF server 4b. The job data input to the system is managed in the HWF server 4 to which the job data is input. The Rukoto.

  Next, as an aspect of reusing job data in the HWF system according to the present embodiment, an aspect in which image formation output is performed via another DFE 100 based on job data stored in a certain DFE 100 will be described. FIG. 17 is a sequence diagram showing an operation when the job data storage destination is not changed in such a case.

  As shown in FIG. 17, first, the client terminal 5 transmits a job reference request to the HWF server 4 in response to an operator's operation on the system GUI (S1701). In the HWF server 4 that has received the job reference request, the system control unit 410 acquires information from the job management unit 430 and the job data storage unit 414, generates a job list, and transmits it to the request source (S1702). As a result, a list of job data managed in the HWF server 4 is displayed in the system GUI displayed on the client terminal 5.

  The client terminal 5 transmits a job execution request by reusing a managed job to the HWF server 4 in response to an operator's operation on the displayed job data list (S1703). In step S1703, information for specifying a job to be executed by reusing job data and information for specifying a device that executes the job and performs image formation and output are included.

  The information specifying the job is, for example, “Job ID” shown in FIG. The information for designating the device is information for designating the digital printers 1a and 1b shown in FIG. In the following description, the DFE included in the digital printer 1a is referred to as DFE 100a, and the DFE included in the digital printer 1b is referred to as DFE 100b. An example will be described in which the DFE 100a is specified as a device that executes a job, that is, an execution destination device, and job data including actual data is stored as a storage destination device by the DFE 100b.

  In the HWF server 4 that has received the job execution request, the system control unit 410 acquires job data from the job data storage unit 414 based on the designated “job ID”. Then, the job data is transmitted together with the job execution request to the DFE 100a designated as the execution destination device, similarly to S1114 of FIG. 11 (S1704).

  Here, the job data transmitted in step S1704 has only the “JDF information” with the actual data deleted as described in FIG. Instead of actual data, “real job reference information” shown in FIG. 16 is embedded. The embedding of the “real job reference information” in the job data may be performed by the job management unit 430 according to the deletion of the real data, or may be performed by the system control unit 410 in S1704 of FIG.

  In the DFE 100a that has received the job data and the job execution request, in-DFE processing is executed in the same manner as in S1115 of FIG. Here, when the job control unit 116 executes a process in charge of the process in the DFE, it recognizes that “real job reference information” is embedded instead of real data. As a result, the system control unit 113 requests the HWF server 4 for actual data based on the “real job reference information” (S1705).

  In the HWF server 4 that has received the request for actual data, the job management unit 430 compares the remaining storage capacity of each device, and determines whether to change the storage destination of the actual data based on the comparison result. Is performed (S1706). In step S <b> 1706, the job management unit 430 uses the device information management unit 416 to acquire the remaining storage areas of the DFE 100 a that is the job execution device and the DFE 100 b that is the storage device of the actual data, triggered by a request for actual job data. To do.

  In this embodiment, the case where the movement of actual data is determined based on the remaining capacity of the storage medium in the DFEs 100a and 100b will be described as an example. However, the present invention is not limited to this, and at least the devices of the DFEs 100a and 100b. It can be determined based on the state of As a result, the storage destination of the actual data can be changed in real time according to the operation mode of each device in the system, and the system control can be made more efficient.

  When acquiring the remaining storage capacity described above, information already stored in the device information storage unit 417 may be used, or the device information communication unit 415 may acquire in real time using the processing of S1706 as a trigger. . Then, the job management unit 430 compares the acquired remaining capacities, and determines whether or not to change the storage destination of actual data.

  When determining the change of the actual data storage destination, it is possible to make a determination based on the usage rate of the storage capacity in the same manner as the determination of the job data storage destination in S1111 of FIG. As a result of such determination, in the example of FIG. 17, the case where the storage destination of the actual data is maintained as the FE 100b is taken as an example.

  When the job management unit 430 completes the data movement determination, in the HWF server 4, the system control unit 410 redirects the actual data acquisition request to the DFE 100b based on the “real job reference information” (S1707). That is, in S1707, the system control unit 410 functions as an image acquisition control unit. In the DFE 100b that has received the actual data acquisition request by redirection, the job management unit 130 receives the actual data acquisition request, and the system control unit 113 acquires the actual data from the job data storage unit 114 in response to the acquisition request.

  Then, under the control of the system control unit 113, the job management unit 130 transmits actual data to the request source DFE 100a (S1708). In addition, the job management unit 130 notifies the HWF server 4 that redirected the request that the transmission of the actual data has been completed (S1709).

  In the DFE 100a that has received the actual data from the DFE 100b, the job control unit 116 acquires the actual data and controls the execution of the job in the same manner as the processing described with reference to FIGS. 13 and 14 (S1710). Then, a completion notification is sent to the HWF server 4 as in S1116 of FIG. 11 (S1711).

  In the HWF server 4 that has received the completion notification, the job management unit 430 that has decided to maintain the actual data storage destination as the FE 100b requests the DFE 100a to delete the received actual data (S1712). . Thereby, in the DFE 100a, the job management unit 130 acquires the deletion request, processes the job data so that the system control unit 113 deletes the job data (S1713), and ends the processing.

  As shown in FIG. 17, in the job data reuse processing according to the present embodiment, as shown in FIG. 16, “real job reference information” is associated with an identifier for uniquely identifying job data in the system. The actual data storage destination is managed. When the stored job data is reused and a job is executed in another DFE 100, the actual data request is redirected based on the “real job reference information”, and the job data is stored from the actual data storage destination. The actual data is sent directly to the execution destination. Therefore, unlike the case where actual data is exchanged via the HWF server 4, it is possible to reduce network traffic.

  Next, a case where the job data storage destination is changed will be described with reference to FIG. As shown in FIG. 18, even when the job data storage destination is changed, the processing is executed in the same manner as S1701 to S1705 in FIG. 17 (S1801 to S1805). Then, as in S1706, the job management unit 430 determines data movement by comparing the remaining amount (S1806). As a result, here, as an example, the actual data storage destination is changed from the DFE 100b to the DFE 100a.

  When it is determined that the data movement determination has been completed and the actual data storage destination is to be moved, the job management unit 430 updates the reference table shown in FIG. 16 to indicate “real job reference information” and DFE 100b. The information is changed to information indicating the DFE 100a (S1807). Then, the system control unit 410 redirects the actual data acquisition request to the DFE 100b based on the “real job reference information” before the change (S1808). In the DFE 100b that has received the actual data acquisition request by redirection, the job management unit 130 receives the actual data acquisition request, and the system control unit 113 acquires the actual data from the job data storage unit 114 in response to the acquisition request.

  Then, under the control of the system control unit 113, the job management unit 130 transmits actual data to the request source DFE 100a (S1809). Further, the job management unit 130 notifies the HWF server 4 that redirected the request that the transmission of the actual data has been completed (S1810).

  In the HWF server 4 that has received the actual data transmission notification from the DFE 100b, the job management unit 430 that has decided to change the storage destination of the actual data to the FE 100a makes an update request for “actual job reference information” to the DFE 100b. (S1811). As a result, in the DFE 100b, the job management unit 130 acquires an update request, changes the “real job reference information” from the information indicating the DFE 100b to the information indicating the DFE 100a, and deletes the actual data via the system control unit 113. This is performed (S1812).

  As described above, in the HWF system according to the present embodiment, when the storage destination of the job data for reuse is changed, the actual data is deleted from the DFE 100 in which the job data has been stored. Even in this case, the job header information including “JDF information” shown in FIG. 15 and the reference table shown in FIG. 16 are left. Therefore, the operator can operate the user interface of the DFE 100 and re-execute the print job based on the reference information stored in the DFE 100, which can improve convenience.

  Further, in the present embodiment, a case will be described as an example where the HWF server 4 transmits a request to delete actual data in response to the actual data transmission completion notification in S1810, and the actual data is deleted in S1812. As a result, it is possible to avoid an error in the processing of S1809 and the actual data not being stored anywhere.

  On the other hand, in the DFE 100a that has received the actual data from the DFE 100b, the job control unit 116 acquires the actual data and controls the execution of the job in the same manner as the processing described in FIGS. 13 and 14 (S1813). Then, similar to S1116 in FIG. 11, a completion notification is sent to the HWF server 4 (S1814).

  In the HWF server 4 that has received the completion notification, the job management unit 430 that has decided to change the storage destination of the actual data to the FE 100a stores the job data including the received actual data in the DFE 100a. A request is made (S1815). Thereby, in the DFE 100a, the job management unit 130 acquires the save request, processes the job data so that the system control unit 113 saves the job data (S1816), and ends the process.

  As described above, in the present embodiment, in response to the completion notification in S1711 or S1814, the HWF server 4 issues a request for deleting or saving actual data to the DFE 100a, and as a result, the actual data is processed in the DFE 100a. . As a result, it is possible to prevent the actual data from being deleted on the system at a timing when the HWF server 4 cannot grasp the actual data.

  As shown in FIG. 18, in the job data reuse process according to the present embodiment, the remaining capacity of the storage capacity is compared between the device storing the job data and the device executing the job. Based on the result, the storage location of the actual data is changed. By performing such processing every time job data is reused, it is possible to efficiently operate the storage capacity of each device constituting the system without increasing the work load on the operator.

  In the present embodiment, each DFE 100 is equipped with the RIP engine 120 corresponding to the RIP engine 420 mounted on the HWF server 4. Therefore, even if the job data stored in one DFE 100 is data that has been subjected to RIP processing halfway when stored in the job data storage unit 114, the problem associated with the execution of job data in another DFE 100 is solved. Is possible. That is, when a job is executed in another DFE 100, it is possible to select an RIP engine corresponding to the RIP engine that has performed RIP processing halfway, and it is possible to eliminate problems caused by differences in the RIP engines.

  In FIGS. 17 and 18, the case has been described as an example in which job data stored in a certain DFE 100 is reused via another DFE 100 and printed out. In addition, the job data stored in the HWF server 4 may be reused for print output. In such a case, the processing is the same as that after S1109 in FIG. 11, and as described with reference to FIG. 11, a determination is made to move actual data between the HWF server 4 and the DFE 100 that executes the job.

  In addition, in the determination in S1706 of FIG. 17 or S1806 of FIG. 18, in addition to the determination between the device that stores the actual data and the device that executes the job, the remaining capacity of the storage capacity of the HWF server 4 is set. It is good also as a comparison object. Thereby, in addition to between the DFEs 100, it is possible to move the storage destination of the actual data to the HWF server 4.

  In the above embodiment, the case where the job management unit 430 and the job management unit 130 manage jobs by storing a reference table as illustrated in FIG. 16 has been described as an example. However, this is merely an example, and it is only necessary that the same job is uniquely identified and managed in the system and that the storage location of the actual data can be referred to for job data that does not include actual data.

  Therefore, in a device that has acquired job data even once, at least “JDF information” is stored together with an identifier for uniquely identifying job data, and “real job reference information” is embedded when actual data is deleted. In this case, the same effect as described above can be obtained. In this case, the job data storage unit 414 holding the job data in which “real job reference information” is embedded functions as an instruction information management unit in conjunction with the job management unit 430.

  In the above embodiment, “page mode” and “sheet mode” have been described as examples of the “RIP control mode”. Here, in the “page mode”, as described above, the RIP control unit 119 transmits the pre-RIP data to the RIP engine 120 for each of a plurality of pre-aggregation pages, and performs the RIP process for each page to be aggregated. To generate raster data in the selected state.

  In addition, a processing mode is also possible in which the RIP control unit 119 transmits all pre-RIP data for a plurality of pre-aggregation pages to the RIP engine 120, and the RIP engine 120 executes the RIP processing while performing imposition processing. is there. Such a processing mode is called a “surface mode”. Even when the “surface mode” is used, the RIP control unit 119 performs the conversion process of the parameter specified for the RIP engine 120 in accordance with the RIP engine 120 that executes the RIP process, as described above. As a result, the same effect as described above can be obtained.

  Further, in the above-described embodiment, the case where the RIP control parameters are converted as an example of the process for dealing with the difference between the “RIP control modes” has been described. In addition, for example, the RIP engine 120 that executes the RIP process may be selected according to the format of the original data.

  In this case, when the RIP control unit 119 obtains the RIP processing target data from the job control unit 116, the RIP control unit 119 refers to the information on the “RIP control mode”. Then, the RIP engine 120 corresponding to the designation of “page mode”, “sheet mode”, “surface mode” or the like is selected, and RIP processing is executed. The function of the RIP control unit 119 can cope with the difference between the parameter designation method in the original data and the corresponding “RIP control mode” of the RIP engine 120 as described above.

  Further, in the system according to the present embodiment, on the assumption that the same RIP engine is mounted on a plurality of devices, each of the RIP internal processing is executed by the information of “RIP device designation” as shown in FIG. Manage the devices to be used. When the RIP process is executed in the DFE 100, the RIP internal process that has already been executed is excluded based on the information of “RIP status”.

  According to such a configuration, the operator can easily change the RIP internal processing handled by each device by changing the information of “RIP device designation”. In this case, since necessary processing is determined based on the information of “RIP status”, only necessary processing is executed in the DFE 100.

  By such processing, when RIP processing is performed in a plurality of devices, it is possible to facilitate the change of the processing that each device is responsible for. Further, when the RIP process is executed by each of the HWF server 4 and the DFE 100, the same image as when the RIP process is executed by only one of them can be generated.

  Further, according to the above embodiment, when RIP internal processing is distributed between the HWF server 4 and the DFE 100, the “pass-through mode” is set, and the information processed in the HWF server 4 is directly input to the RIP engine of the DFE 100. Is done. Since the same RIP engine is installed in the HWF server 4 and the DFE 100, it is possible to continue the RIP process as a series of processes without being aware of the difference between the devices. In such a case, by using the above-described “RIP status” information, it is possible to more suitably realize the dynamic change of the distribution mode when distributing the RIP processing among a plurality of devices.

  Further, according to the above-described embodiment, each individual job reception unit 112 that corresponds to each of the plurality of RIP engines installed in the DFE 100 and that is associated with individual settings such as “pass-through mode” is provided in the DFE 100. Is provided.

  Thereby, on the HWF server 4 side, the same RIP engine corresponding to the RIP engine mounted on the HWF server 4 can be specified by specifying the individual job receiving unit 112. In addition, it is possible to specify that the processing is in the “pass-through mode”. Therefore, it is possible to easily realize the processing by the same RIP engine between the HWF server 4 and the DFE 100 as described above, setting the “pass-through mode”, and the like.

  In the above embodiment, as shown in the “RIP device designation” information in FIG. 3, when RIP processing is executed in the DFE 100, one of a plurality of RIP engines installed in the DFE 100 can be designated. is there. This makes it possible to execute RIP processing by flexibly using the functions installed in each RIP engine.

  Further, in the above embodiment, as described in FIG. 3, as an example, information on “RIP device designation” is provided, and the workflow control unit 418 determines a module to execute processing based on this information. explained. In addition, for example, information corresponding to “RIP device designation” may be described in the workflow information shown in FIG.

  In such a case, since information corresponding to “RIP device designation” is not included in the JDF information, it is not transmitted to the DFE 100 side. As a result, on the DFE 100 side, the RIP engine 420 on the HWF server 4 side cannot determine the designated process, but the DFE 100 side can determine the process to be executed by referring to the “RIP status”. I can do it.

  In addition, it is also possible to analyze the content of data received on the DFE 100 side and determine the RIP processing that has already been executed. However, in this case, since processing for analyzing the input data occurs, it takes time. On the other hand, by using the “RIP status” information, it is possible to quickly execute image formation output without performing such analysis processing.

DESCRIPTION OF SYMBOLS 1 Digital printer 2 Offset printer 3 Post-processing apparatus 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 Image storage part 122 Printer control part 123 Device information management unit 124 Device information communication unit 130 Job management unit 150 Digital engine 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 Transmission / reception unit 430 Job management unit

JP 2004-358800 A

Claims (8)

An image processing system that sequentially executes a plurality of defined processes,
A process execution control device that controls execution of the plurality of processes, and a plurality of image formation output control devices that control execution of the image formation output,
The process execution control device includes:
A process execution control unit that controls execution of the plurality of processes according to instruction information;
As one of the plurality of processes, control-side drawing information generation for generating drawing information, which is information referred to by the image forming apparatus when outputting an image, based on output target image information, which is image information of an image formation output target And
A command information management unit that manages the command information that has already been executed in association with information indicating a storage destination of output target image information that is image information output in the command information;
Among the plurality of image formation output control devices, from the storage destination device that is the storage destination of the output target image information, another image formation output control device that causes the image formation device to execute image formation output An image acquisition control unit that controls the transfer of the output target image information based on the command information that has already been executed,
The image forming output control device includes:
A drawing information generation unit corresponding to the control side drawing information generation unit, and an output side drawing information generation unit that generates the drawing information based on the output target image information;
An execution control unit that causes the image forming apparatus to execute image formation output based on the drawing information generated by the output side drawing information generation unit,
The command information management unit changes the storage destination of the output target image information related to the command information from the storage destination device to the execution destination device based on the state of each of the storage destination device and the execution destination device. An image processing system that determines and updates information indicating a storage location of the output target image information.   The command information management unit determines a storage destination of the output target image information related to the command information based on a comparison result of information on a remaining storage capacity in a storage medium included in each of the storage destination device and the execution destination device. The image processing system according to claim 1, wherein it is determined to change the storage destination device to the execution destination device.   When the command information management unit obtains from the storage destination device a notification indicating that the transmission of the output target image information to the execution destination device is completed, the command information management unit sends the output target image to the storage destination device. The image processing system according to claim 1, wherein deletion of information is requested.   When the instruction information management unit obtains from the execution destination device a notification indicating that execution control of image formation output based on the output target image information has been completed in the execution destination device, 4. The image processing system according to claim 1, wherein storage of the output target image information is requested. 5. The command information is information generated in a state including information on execution of the plurality of processes and the output target image information,
The command information management unit deletes the output target image information from a storage medium in the processing execution control device when storing the output target image information included in the command information in the storage destination device, and outputs the output target image. 5. The image processing system according to claim 1, wherein information indicating the storage destination device in which information is stored is stored in the storage medium in association with the command information. 6. In an image processing system that executes a plurality of predetermined processes, a process execution control device that controls execution of the plurality of processes and causes a plurality of image formation output control devices that control execution of image formation output to execute image formation output Because
A process execution control unit that controls execution of the plurality of processes according to instruction information;
As one of the plurality of processes, control-side drawing information generation for generating drawing information, which is information referred to by the image forming apparatus when outputting an image, based on output target image information, which is image information of an image formation output target And
A command information management unit that manages the command information that has already been executed in association with information indicating a storage destination of output target image information that is image information output in the command information;
Among the plurality of image formation output control devices, from the storage destination device that is the storage destination of the output target image information, another image formation output control device that causes the image formation device to execute image formation output An image acquisition control unit that controls the transfer of the output target image information based on the command information that has already been executed,
The command information management unit changes the storage destination of the output target image information related to the command information from the storage destination device to the execution destination device based on the state of each of the storage destination device and the execution destination device. Determine and update the information indicating the storage location of the output target image information,
The control-side drawing information generation unit corresponds to an output-side drawing information generation unit that generates the drawing information based on the output target image information in the image formation output control device. . An image processing method in an image processing system, comprising: a process execution control device that controls execution of a plurality of defined processes; and a plurality of image formation output control devices that control execution of an image formation output,
The process execution control device includes:
Controlling execution of the plurality of processes in accordance with instruction information;
As one of the plurality of processes, drawing information which is information referred to by the image forming apparatus at the time of image formation output is generated based on output target image information which is information on an image formation output target image,
Managing the instruction information that has already been executed in association with information indicating a storage destination of output target image information that is image information output in the instruction information;
Among the plurality of image formation output control devices, from the storage destination device that is the storage destination of the output target image information, another image formation output control device that causes the image formation device to execute image formation output The transfer of the output target image information to the control based on the command information already executed,
Based on the state of each of the storage destination device and the execution destination device, it is determined to change the storage destination of the output target image information related to the command information from the storage destination device to the execution destination device, and the output target image Update the information indicating the information storage location,
The image forming output control device includes:
In the process execution control device, the drawing information generation unit corresponding to the drawing information generation unit that generates the drawing information generates the drawing information based on the output target image information,
An image processing method for causing an image forming apparatus to execute image forming output based on drawing information generated by the output side drawing information generating unit. In an image processing system that executes a plurality of predetermined processes, a process execution control device that controls execution of the plurality of processes and causes a plurality of image formation output control devices that control execution of image formation output to execute image formation output A control program for controlling
A process execution control unit that controls execution of the plurality of processes according to instruction information;
As one of the plurality of processes, control-side drawing information generation for generating drawing information, which is information referred to by the image forming apparatus when outputting an image, based on output target image information, which is image information of an image formation output target And
A command information management unit that manages the command information that has already been executed in association with information indicating a storage destination of output target image information that is image information output in the command information;
Among the plurality of image formation output control devices, from the storage destination device that is the storage destination of the output target image information, another image formation output control device that causes the image formation device to execute image formation output An image acquisition control unit that controls the transfer of the output target image information to the image based on the command information that has already been executed in the information processing device,
The command information management unit changes the storage destination of the output target image information related to the command information from the storage destination device to the execution destination device based on the state of each of the storage destination device and the execution destination device. Determine and update the information indicating the storage location of the output target image information,
The control-side drawing information generation unit corresponds to an output-side drawing information generation unit that generates the drawing information based on the output target image information in the image formation output control device.