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

Abstract

PROBLEM TO BE SOLVED: To execute, even when an HWF server cannot execute processing on fonts in print data, offset printing and output by using the fonts included in the print data.SOLUTION: There is provided an image processing system sequentially executing a plurality of pieces of determined processing, and comprising an HWF server 4 that controls the execution of the plurality of pieces of processing and a DFE 100 that controls the execution of formation and output of images, wherein the DFE 100 includes a RIP engine 120 that is provided corresponding to a RIP engine 420 inside the HWF server 4, and the DFE 100 performs processing of dealing with fonts that cannot be used in the HWF server 4.SELECTED DRAWING: Figure 15

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, the font data installed in the offset printer and the digital printer may be different. In such a case, if the output is executed based on the same print data, there is a possibility that a print result will be different, and a printed matter different from the intention of the creator of the document or the operator who instructed printing may be produced.

  As a technology for performing print output using the same font, if there is an unusable font in the print data, print output using the same font is executed by causing the device that can use the font to execute a print job. In other words, a method for avoiding a difference in printing results has been proposed (see, for example, Patent Document 1).

  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.

  In such a system, the font installed in the HWF server that generates data to be transferred to the CTP may be different from the font installed in the DFE. In such a case, there is a difference between the font processing result by the RIP engine installed in the HWF server and the font processing result by the RIP engine installed in the DFE, and it is difficult to obtain the intended image formation output result. . In the technique of Patent Document 2, since RIP processing of print data is executed only by a digital printer, in the case of offset printing, it is necessary to perform RIP processing by an HWF server, and the technique of Patent Document 1 cannot be applied.

  SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems. In an image processing system in which a plurality of different types of image forming apparatuses are collectively managed by a management apparatus, the font processing of print data is managed by the management apparatus. It is an object of the present invention to execute RIP processing in a management apparatus using a font included in print data even when the process cannot be executed.

  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 An image forming output control device that controls execution of output, the processing execution control device including: a processing execution control unit that controls execution of the plurality of processes; and an image forming apparatus as one of the plurality of processes. A control-side drawing information generation unit that generates drawing information, which is information to be referred to upon image formation output, based on output target image information, which is image information of an image formation output target, and an image forming apparatus that executes image formation output On the other hand, there is information on the character form specified by the drawing information transmitting unit that transmits the generated drawing information and the character form specifying information that specifies the character form included in the output target image information. A character information processing requesting unit for requesting the image forming output control device to process character information included in the output target image information when the control-side drawing information generating unit cannot be used; and the image forming output control The apparatus controls execution of an image forming output based on the command information received by the image forming output control device and an output side drawing information generating unit which is a drawing information generating unit corresponding to the control side drawing information generating unit The form of the character information included in the image information of the output target based on the information of the character form specified by the execution control unit and the character form specifying information included in the image information of the output target in response to the request A character form processing unit that performs processing related to the character information and a control-side drawing information generation unit based on the image information of the output target that has undergone processing related to the form of the character information. And generates drawing information.

  SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems. In an image processing system in which a plurality of different types of image forming apparatuses are collectively managed by a management apparatus, the font processing of print data is managed by the management apparatus. It is an object of the present invention to execute RIP processing in a management apparatus using a font included in print data even when the process cannot be executed.

It is a figure which shows the operation | use form of the system which concerns on embodiment of this invention. It is a block diagram which shows the hardware constitutions of the information processing apparatus which concerns on embodiment of this invention. It is a figure which shows the JDF information which concerns on embodiment of this invention. It is a block diagram which shows the function structure of the HWF server which concerns on embodiment of this invention. It is a figure which shows the example of the workflow information which concerns on embodiment of this invention. It is a block diagram which shows the function structure of DFE which concerns on embodiment of this invention. It is a figure which shows the example of the conversion table which concerns on embodiment of this invention. It is a figure which shows the example of the RIP parameter which concerns on embodiment of this invention. It is a block diagram which shows the function structure of the RIP engine which concerns on embodiment of this invention. It is a block diagram which shows the function structure of the RIP engine which concerns on embodiment of this invention. It is a sequence diagram which shows the whole operation | movement of the system which concerns on embodiment of this invention. It is a figure which shows the information of the division | segmentation request | requirement which concerns on embodiment of this invention. It is a 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 sequence diagram which shows the operation | movement of the process corresponding to the unusable font which concerns on embodiment of this invention. It is the figure which illustrated the composition of the font data concerning the embodiment of the present invention. It is the figure which illustrated the composition of the job data concerning the embodiment of the present invention. It is a flowchart which shows judgment of the font process which concerns on embodiment of this invention. Explanatory drawing which shows the execution example which allocates a font process to DFE which concerns on embodiment of this invention. Explanatory drawing which shows the execution example which allocates a font process to DFE which concerns on embodiment of this 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. When a digital printer is operated in such a system, a DIP (Digital Front End) that controls the digital printer and a RIP (Raster Image Processor) engine shared by the server are mounted. It is one of.

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

  The digital printer 1 is a printer that performs image formation output without using a plate, such as an electrophotographic method or an inkjet method, and includes a DFE 100 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.

  In such a system configuration, when the HWF server 4 performs RIP processing and causes the offset printer 2 to execute print output, processing when a font that cannot be used by the HWF server 4 is specified in the print data is as follows: This is one of the gist according to the present embodiment. In such a case, the HWF server 4 according to the present embodiment requests font processing from the DFE 100, and performs RIP processing using the result.

  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 a configuration similar to that of 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.

  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.

  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. That is, the workflow control unit 418 functions as a process execution control unit.

  Upon receiving the execution instruction, the job control unit 413 inputs the above-described PDL information and JDF information to the RIP engine 420 to execute the RIP process. The JDF information includes information indicating which of the 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.

  Here, the present embodiment is characterized in processing when font data specified as a form of character information included in job data cannot be used in the HWF server 4. In such a case, the job control unit 413 receives a notification from the RIP engine 420 indicating that character information cannot be drawn using the specified font data, and requests the DFE 100 to perform font processing accordingly. Such processing is one of the gist according to the present embodiment. Details will be described later.

  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. Accordingly, the job transmission / reception unit 421 functions as a drawing information transmission unit.

  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 has a plurality of RIP engines mounted therein. This is installed corresponding to the RIP engine of another device that may transmit a job to the DFE 100 in the HWF system. In the present embodiment, since 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 that is 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.

  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, control processing of the digital engine 150 by the printer control unit 122, and font processing by the character information editing processing unit 125. It is.

  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 JDF information standard. Also known is a method for collecting printer information using a communication protocol called SNMP (Simple Network Management Protocol) and a database called MIB (Management Information Base).

  The device information management unit 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.

  The character information editing processing unit 125 analyzes and edits font data in the job data input to the DFE 100, and performs font embedding processing and outline processing. The intermediate data that has been subjected to font embedding processing and outline processing by the character information editing processing unit 125 is transmitted to the HWF server 4 by the system control unit 113 in accordance with job data at the time of input.

  In font processing, font data including all character data that can be displayed in the font (hereinafter referred to as glyph data) is referred to. Therefore, the font data corresponds to character form designation information. The font embedding process performed by the character information editing processing unit 125 is a process in which an identifier for identifying information related to the size and shape of the font included in the font data is embedded in the PDF information. When the font embedding process is performed in this way, the font data embedded in the PDF information is referred to when the character is drawn. Accordingly, there is no need to refer to font data on the computer that performs the drawing process, so that there is no difference in print output.

  In the font outline processing performed by the character information editing processing unit 125, first, glyph data of a font to be visualized when drawing a character is extracted. Then, based on the extracted glyph data, the outline of the character is divided into a number of line segments, and each line segment is converted into a Bezier and placed on the page of the image. Therefore, the outline font data is image data of a character outline composed of a set of end points and control points of a large number of line segments, and is handled as image data arranged at a specific position on the page.

  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.

  Here, as described above, the present embodiment has a feature in processing when the font data specified as the form of the character information included in the job data is a non-compatible font in the HWF server 4. In the present embodiment, the preflight processing unit of the RIP engine 420 performs notification to the RIP engine 420 that processing with the specified font is impossible when the font data is not supported by the HWF server 4. To do. Such processing is one of the gist according to the present embodiment. Details will be described later.

  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.

  A font processing unit 207 extracts font data, performs embedding processing of fonts into PDL, and 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. 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).

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

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

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

  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 (S1303 / YES), or when the JDF conversion is completed and the job attribute within DFE is generated, the job control unit 116 generates a 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.

  As described above, 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, the devices that execute each of the RIP internal processes are managed by the information of “RIP device designation” as shown in FIG. Then, when the RIP process is executed in the DFE 100, the RIP internal process that has already been executed is excluded based on the “RIP status” information. With such a system configuration, RIP processing that has not been executed by the HWF server 4 can be continuously executed by the DFE 100.

  In the present embodiment, the RIP engine 420 and the RIP engine 120 are shared. Therefore, in the font processing in the RIP processing of the HWF server 4 and the DFE 100, only whether or not the font processing can be executed is different depending on the difference of font data installed in each device.

  Depending on the difference between the font data installed in the HWF server 4 and the DFE 100, the RFE processing of the font used for the data to be printed can be performed in the DFE 100, but the RWF processing cannot be performed in the HWF server 4. is there. Therefore, there is a possibility that a printed matter different from the intention of the creator of the document or the operator who instructed printing can be produced by the offset print output.

  In the HWF system according to the present embodiment, when the font data used for the print data is mounted on the DFE 100, the DFE 100 is caused to execute the font processing of the print data not mounted on the HWF server 4. Then, the print data subjected to font processing from the DFE 100 is returned to the HWF server 4, and the HWF server 4 causes the CTP 200 to execute offset print output based on the acquired print data. In other words, the HWF server 4 causes the DFE 100 to execute font processing that cannot be processed. Therefore, even if the print data used for the offset print output includes a font that cannot be processed by the HWF server 4, the DFE 100 is caused to execute the font process on behalf of the DFE 100. Therefore, it is possible to represent the font used for the input print data in the printed matter.

  Hereinafter, with reference to FIG. 15, the operation of the DFE 100 corresponding to the unusable font will be described. FIG. 15 is a sequence diagram illustrating an operation when the HWF server 4 causes the DFE 100 to execute font processing on behalf of the DFE 100. In the HWF server 4, the job control unit 413 causes the RIP engine 420 to execute RIP processing in order to generate offset print output data to be transmitted to the CTP 200. At this time, if the print data includes a font that cannot be processed by the HWF server 4, the preflight processing unit of the RIP engine 420 detects a font error (S1501). At this time, the RIP engine 420 does not update the RIP status of “font”. That is, the RIP status of “font” is controlled to the “Not Yet” state, and the font processing is not executed in the RIP engine 420. In this embodiment, the preflight processing unit of the RIP engine 420 that performs processing for detecting a font error functions as an editability determination unit that determines whether font data can be edited and notifies the result by updating the RIP status. Therefore, when the RIP status of “font” is not updated in the RIP engine 420 and is in the “Not Yes” state, the job control unit 413 adds an execution instruction for processing for handling unusable fonts to the job data and updates it. .

  The RIP execution result data generated by the RIP processing by the RIP engine 420 is at least intermediate data for which the font RIP processing has not been completed. The intermediate data and the JDF information in which the font cannot be edited by the preflight processing unit in the processing of S1501 are handled as job data by the job control unit 413. The job control unit 413 updates the “RIP device designation” of the JDF information by designating the DFE 100 in which the designated font is mounted, and inputs job data to the job transmission / reception unit 421. The job data input by the job control unit 413 is transmitted to the DFE 100 designated by “RIP device designation” by the job transmission / reception unit 421. Therefore, the job control unit 413 functions as a character information processing request unit.

  In this embodiment, when the job data transmission destination DFE 100 is specified, the DFE 100 in which the font used in the print data is mounted must be specified as the transmission destination. Therefore, the device information communication unit 415 exchanges device information with the device information communication unit 124 of the DFE 100, and acquires information about fonts installed in the DFE 100. Device information exchange between the device information communication unit 415 and the DFE 100 is periodically performed. FIG. 16 is a diagram illustrating device information of the DFE 100.

  As illustrated in FIG. 16, the device information of the DFE 100 includes a description indicating that the respective fonts “AAA, BBB, CCC, DDD, EEE...” Are mounted. The job control unit 413 controls the RIP engine 420 so as to refer to the device information of the DFE 100 acquired by the device information communication unit 415. In the present embodiment, the following description will be made on the assumption that the device information of the DFE 100 includes a description indicating that a font that cannot be edited by the HWF server 4 exists.

  When the workflow control unit 418 receives job data including an execution instruction for processing for handling unusable fonts, the workflow control unit 418 adds processing for handling unusable fonts to generate new workflow information, and creates a workflow information storage unit. It stores in 419. The workflow information stored at this time is associated with a job that performs processing for handling unusable fonts, and is transmitted to the DFE 100 that the job control unit 413 previously designated as the job data transmission destination (S1502).

  When the job receiving unit 111 receives job data for processing to handle an unusable font (S1503), the system control unit 113 starts a workflow according to the workflow information included in the received job data. In accordance with the workflow, the job control unit 116 causes the character information editing processing unit 125 to execute a process for handling unusable fonts (S1504). The outline processing is executed by the character information editing processing unit 125 corresponding to the unusable font. Details of processing for handling these unusable fonts will be described later.

  The job data including the intermediate data for which the character information editing processing unit 125 has handled the unusable font is transmitted to the HWF server 4 by the system control unit 113 (S1505).

  When the job data including intermediate data that has been processed for the unusable font is received (S1506), the system control unit 410 instructs the workflow control unit 418 to execute the job according to the workflow information included in the received job data. Do. The workflow control unit 418 instructs the job control unit 413 to execute each process. Each process at this time includes at least a process in which the HWF server 4 generates raster data to be offset printed by the CTP 200. Accordingly, the job control unit 413 inputs the job data to the RIP engine 420, and causes the RIP process whose RIP status is “Not Yes” to be executed (S1507).

  The intermediate data processed in S1507 is data in which all character codes are outlined. Therefore, it is possible to avoid the font error described above and generate raster data in the form of designated font data. When the RIP processing by the RIP engine 420 is completed, raster data is generated and the RIP status of the job data is updated to “Done” in all categories.

  The raster data generated in this way is transmitted to the CTP 200 by the job transmission / reception unit 421 (S1508), and is offset printed by the offset engine 250. This completes the processing for handling unusable fonts in the DFE 100.

  As described above, in the present embodiment, when a font error occurs during the RIP processing of job data in the HWF server 4, job data is stored in the DFE 100 in which the font used for the job data is mounted. Send. The DFE 100 that has received the job data performs font processing on behalf of the job data based on the job data. According to such a configuration, even if a font that cannot be processed by the HWF server 4 is used for print data, if the DFE 100 can process the font, the print data can be offset. .

  In the above embodiment, the case where outline processing is performed on the DFE 100 side has been described as an example of processing for handling unusable fonts. In this case, even when offset printing is performed, part of the RIP processing can be outsourced to the DFE 100, and the processing load on the HWF server 4 can be reduced.

  On the other hand, if the font data can be received from the DFE 100, the HWF server 4 can also perform outline processing. In such a case, in S1504 of FIG. 15, not the outline processing but font data embedding processing in job data is performed.

  FIG. 17 is a diagram illustrating job data transmitted to the HWF server 4 after the font data embedding process by the DFE 100 is performed. Font data is information external to job data that is originally mounted on a device that performs print output, is referred to when raster data is generated, and is used to visualize character information. In the present embodiment, the DFE 100 performs processing for handling unusable fonts, and the processed job data is transmitted to the HWF server 4. Therefore, font data is embedded in the job data transmitted to the HWF server 4 as shown in FIG. With such a configuration, job data is transferred. Therefore, since it is not necessary to refer to the font data mounted on the HWF server 4 when generating raster data used for offset print output in the HWF server 4, it is possible to prevent a difference in print output.

  Furthermore, in the present embodiment, it is possible to dynamically control whether font data is embedded or outlined in the processing for handling unusable fonts. Hereinafter, with reference to FIG. 18, the control of the processing contents in the processing for handling unusable fonts will be described.

  In the processing for handling unusable fonts according to the present embodiment, it is determined whether to perform embedding processing or outlining processing according to the processing load state of the HWF server 4 or DFE 100 (S1801). When there are many processes in the DFE 100, the character information editing processing unit 125 executes the font data embedding process of the PDF information included in the job data received in S1503 (S1802). On the other hand, when there are few processes in DFE100 (S1801 / No), the character information edit process part 125 outline-processes the font data of the PDF information contained in the job data received by S1503 (S1803).

  In FIG. 18, when another print job is executed in the DFE 100, it may be determined that the processing load on the DFE 100 is heavy. When the network traffic of the HWF system is high, font embedding processing is performed to reduce the amount of communication with the DFE 100. In these processes, based on the device information acquired by the device information management unit 416, it is determined whether the job control unit 413 causes the character information editing processing unit 125 to execute either font data embedding processing or outline processing. In addition, referring to information on the number of pages to be processed from job data that is processed to handle unusable fonts, when processing a predetermined number of pages (for example, 15 pages) or more to unusable fonts, the DFE 100 You may judge that there are many processes in.

  Furthermore, in the job data, when the font data is prohibited from being embedded in the font data, the outline processing may be executed when the above-described font data such as Thai or Arabic is used. Since Thai and Arabic represent a single character by combining several characters, the amount of layout data used to lay out the characters included in the font data and represent them as characters is larger than in other languages. large. Therefore, when the amount of layout data included in the font data is larger than a predetermined value (for example, 70 MB), it is possible to control to execute the outline processing. In the present embodiment, the font data subjected to the outline processing is image data of a set of end points and control points of a large number of line segments, and is handled as image data arranged at specific positions on the page. In this way, the outline processing is executed, and the processing for handling unusable fonts in the character information editing processing unit 125 is completed.

  Further, the font data subjected to the embedding process is added to the PDF information (S1804), and the processing for handling the unusable font by the character information editing processing unit 125 is completed.

  In FIG. 15, the mode in which the character information editing processing unit 125 performs the processing for handling the unusable font has been described, but the font processing unit 207 also has the same manner as the character information editing processing unit 125. Processing for handling unusable fonts can be executed.

  As described above, in the HWF system according to the present embodiment, a common RIP engine is mounted on the HWF server 4 and the DFE 100. Therefore, when a font error is confirmed during the RIP process in the HWF server 4, the subsequent RIP process can be continuously executed by the DFE 100 in which the font in which the error is confirmed is mounted. Further, as described above, since the HWF server 4 and the DFE 100 are mounted in common with at least the processing unit related to the generation of raster data, the RIP processing of the font interrupted by the HWF server 4 is performed on the DFE 100. Can be run on behalf of. Accordingly, it is possible to perform offset printing using the same font as the font in the print data input from the client terminal 5 as raster data.

  As described above, since the font processing unit 207 and the character information editing processing unit 125 have a function of executing processing for handling the same unusable fonts, the processing for handling unusable fonts shown in FIG. The processing can be executed similarly in the processing unit 207. When the font processing unit 207 executes processing for handling unusable fonts, JDF information whose “font” RIP parameter is “Not Yet” is transmitted to the DFE 100 as part of the job data. For this reason, the font processing unit 207 can simultaneously execute processing for handling unusable fonts and other RIP processing included in the same job data, and transmit the RIP processed data to the HWF server 4. Accordingly, the font processing unit 207 and the character information editing processing unit 125 function as a character form processing unit.

  On the other hand, the job receiving unit 111 is provided with a function of a receiving unit dedicated to handling unusable fonts as one of the individual job receiving units 112, and the character information editing processing unit 125 uses the unusable fonts based on the received job. It is also possible to execute processing corresponding to. In such a case, the job for handling the unusable font is executed outside the RIP engine 120. Therefore, RIP processing for digital printing and processing for handling unusable fonts can be performed in parallel.

  The present invention can also be applied to a case where there are a plurality of digital printers 1 on which fonts that cannot be processed by the HWF server 4 exist. In such a case, the DFE 100 that is the output destination of processing for handling unusable fonts may be specified according to the job execution status in each digital printer 1. FIG. 18 and FIG. 19 show execution examples when outputting processing for handling unusable fonts in accordance with job execution statuses of a plurality of digital printers 1. In FIGS. 19 and 20, the time required to execute each job process is visually indicated by the horizontal width of each frame.

  In an HWF system configured to include a plurality of digital printers 1, processing executed by each unit configuring the RIP engine 120 is performed. For example, in the outlining processing executed by the character information editing processing unit 125 or the font processing unit 207, the size of the outlining data increases as the size of the print data increases. Therefore, there is a possibility that the outline processing or the transmission of PDF data after the outline processing will affect the print completion time of other jobs in the DFE. In the present embodiment, among the plurality of DFEs 100 in which the fonts included in the print data are mounted, the DFE 100 that can secure the time required to process the job for handling the unavailable fonts is transferred to the unavailable fonts. Send the job data for the corresponding process.

  In the execution example illustrated in FIG. 19, the device information management unit 416 acquires the job execution status information of the digital printers 1 a, 1 b, and 1 c in a time zone after the reference time. Then, the job control unit 413 requests the DFE 100 of the digital printer 1c capable of completing the processing for handling the unusable font earliest after the reference time based on the acquired information to perform the processing for handling the unusable font. At the reference time, the digital printer 1a is processing job A, and the digital printer 1b starts processing the job B that has been reserved and input, although there is no job being processed. Therefore, if job data for processing for handling unusable fonts is transmitted to the DFE 100 of the digital printer 1a or 1b, there is a risk of delaying other print jobs. For this reason, the job control unit 413 transmits job data corresponding to the unusable font to the digital printer 1c. In this way, by controlling the transmission destination of the job for handling the unusable font, it is possible to execute the handling process for the unusable font while preventing delay of the print job in the HWF system.

  In the execution example shown in FIG. 20, the job control unit 413 distributes a job for handling unusable fonts to the digital printer 1a having the slowest processing speed, and assigns it to the DFE 100 of the digital printers 1b and 1c having a relatively high processing speed. On the other hand, normal print jobs are distributed. In this way, the job control unit 413 controls the transmission destination of the job for handling the unusable font, so that the unusable font handling process is prevented from causing a delay with respect to a normal print job executed in the HWF system. Can be executed.

  As described above, in the present embodiment, the DFE 100 that is the transmission destination of the job for the processing corresponding to the unusable font is designated according to the required time and processing speed of other jobs executed by the digital printer 1. For this reason, the processing for handling unusable fonts and normal print jobs are scheduled without the outline processing or the transmission of PDF data after the outline processing affecting the print completion time of other jobs in the DFE. It is possible to execute. When the transmission destination of processing for handling unusable fonts is determined in this way, for example, it is possible to cause only the processing for handling unusable fonts to be executed by the DFE 100 that is in a state where printing cannot be performed due to toner replacement or the like. Thus, the efficiency of print output can be increased.

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 125 Character information editing processing 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 Transceiver

JP 2011-16344 A

Claims (11)

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 an image formation output control device that controls execution of image formation output based on image formation output command information received from the process execution control device;
The process execution control device includes:
A process execution control unit that controls execution of the plurality of processes;
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 drawing information transmitting unit that transmits the generated drawing information to an image forming apparatus that executes image forming output;
When the character form information specified by the character form specifying information for specifying the character form included in the output target image information is not usable in the control drawing information generating unit, the output target image information A character information processing requesting unit that requests the image forming output control device to process the included character information,
The image forming output control device includes:
An output side drawing information generation unit which is a drawing information generation unit corresponding to the control side drawing information generation unit;
An execution control unit that controls execution of image formation output based on the command information received in the image formation output control device;
In response to the request, a character that performs processing related to the character information form included in the output target image information based on the character form information specified by the character form specification information included in the output target image information A form processing unit;
The control-side drawing information generation unit generates the drawing information based on the image information to be output on which processing related to the form of the character information has been performed.   The character form processing unit converts, as processing related to the form of the character information, character information included in the image information to be output and identifier information for identifying the character into information on the character form. The image processing system according to claim 1, wherein:   The character form processing unit adds character form information included in the image information to be output to the image information to be output as processing related to the form of the character information. The image processing system described.   The character form processing unit converts, as processing related to the form of the character information, information on an identifier for identifying a character that is character information included in the image information to be output into information on the character form, And the function of adding the character form information included in the image information to be output to the image information to be output, and selecting either one according to the state of the image processing system. The image processing system according to claim 1.   The character form processing unit adds the character form information included in the output target image information to the output target image information when the load state of the image forming output control device is equal to or greater than a predetermined value. The image processing system according to claim 4, wherein the image processing system is selected.   The character form processing unit adds a character form information included in the output target image information to the output target image information when a network load state in the image processing system is equal to or greater than a predetermined value. The image processing system according to claim 4, wherein the image processing system is selected.   7. The character information processing request unit determines a destination to request processing of the character information based on a load state of the plurality of image forming output control devices. Image processing system.   The character information processing request unit determines a destination for requesting processing of the character information based on a speed of image formation output in an image forming apparatus controlled by each of the plurality of image formation output control apparatuses. The image processing system according to any one of claims 1 to 6. In an image processing system that executes a plurality of predetermined processes in order, a function for controlling execution of the plurality of processes and causing an image formation output control device that controls execution of image formation output to execute image formation output and image formation A processing execution control device having a function of transmitting drawing information referred to when executing output to an image forming apparatus,
A process execution control unit that controls execution of the plurality of processes;
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 drawing information transmitting unit that transmits the generated drawing information to an image forming apparatus that executes image forming output;
When the character form information specified by the character form specifying information for specifying the character form included in the output target image information is not usable in the control drawing information generating unit, the output target image information A character information processing requesting unit that requests the image forming output control device to process the included character information,
The control-side drawing information generation unit
The image forming output control device corresponds to an output side drawing information generation unit that generates the drawing information based on output target image information acquired from the processing execution control device,
The drawing information is generated based on the image information of the output target acquired in the image formation output control device by executing processing related to the form of the character information in the image formation output control device in response to the request. The process execution control apparatus characterized by the above-mentioned. Image processing for performing image formation output by sequentially executing the plurality of processes by a process execution control device that controls execution of a plurality of predetermined processes and a plurality of image formation output control devices that control execution of image formation output A method,
The process execution control device and the image formation output control device, as one of the plurality of processes, use drawing information, which is information that the image formation device refers to when performing image formation output, as image formation output target image information. Each has a drawing information generation unit that generates based on output target image information,
The drawing information generation unit on the processing execution control device side corresponds to the drawing information generation unit on the image formation output control device side,
The process execution control device
Controlling execution of the plurality of processes;
When the character form information specified by the character form specifying information for specifying the character form included in the output target image information is not usable in the control drawing information generating unit, the output target image information Requesting the image forming output control device to process the included character information;
The image forming output control apparatus determined as the destination to which the request is transmitted is
In response to the request, based on the character form information designated by the character form designation information contained in the output target image information, processing related to the character information form included in the output target image information,
The control-side drawing information generation unit generates the drawing information based on the image information to be output on which processing related to the form of the character information has been performed. In an image processing system that executes a plurality of predetermined processes in order, a function for controlling execution of the plurality of processes and causing an image formation output control device that controls execution of image formation output to execute image formation output and image formation A control program for realizing a function of transmitting drawing information referred to when executing output to an image forming apparatus,
A process execution control unit that controls execution of the plurality of processes;
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 drawing information transmitting unit that transmits the generated drawing information to an image forming apparatus that executes image forming output;
When the character form information specified by the character form specifying information for specifying the character form included in the output target image information is not usable in the control drawing information generating unit, the output target image information A character information processing requesting unit that requests the image forming output control device to process the included character information in the information processing device;
The control-side drawing information generation unit
The image forming output control device corresponds to an output side drawing information generation unit that generates the drawing information based on output target image information acquired from the processing execution control device,
The drawing information is generated based on the image information of the output target acquired in the image formation output control device by executing processing related to the form of the character information in the image formation output control device in response to the request. A control program characterized by that.