JP6797573B2 - Control device, control method of control device, and program - Google Patents

Description

The present invention relates to a control device, a control method of a control device for executing processing based on the execution data, relating及beauty program.

A printing system is known that controls the execution of printing processing performed by an MFP as a processing execution device based on print data transmitted from DFE (Digital Front End) as an information processing device. In the print process, the DFE performs RIP processing based on the print execution instruction received from the client PC to generate print data including image data and print setting information, and the MFP performs the print data based on the print data transmitted from the DEF. Print. In the printing system, if an error occurs during the execution of the printing process, for example, a communication error between the DFE and the MFP occurs, the printing data transmission process from the DFE to the MFP is interrupted. In such a case, after the communication error between the DFE and the MFP is recovered, the transmission process is restarted from the point of interruption. For example, the DFE acquires the number of print data received by the MFP from the MFP, and the MFP transmits unreceived print data based on the acquired number of print data (see, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2011-040043

However, in the above-mentioned technique of Patent Document 1, when a DFE restart error such as a DFE hang-up occurs, the user himself restarts the DFE, and after the DFE restarts, the user gives an instruction to execute the print process. You need to do it again. That is, in the conventional printing system, when an error requiring the restart of DFE occurs, the user is forced to take more time than necessary to restart the interrupted printing process.

An object of the present invention, without causing over undue effort on the user, the control method of the control apparatus, the control apparatus can resume the interrupted process is to provide a及beauty program.

In order to achieve the above object, the control device of the present invention includes a receiving means for receiving print data from an information processing device , a processing means for executing a decompression process on the print data received by the receiving means, and the above. A control device having a transmission means for transmitting image data generated by executing an expansion process by the processing means to a printing device, and the processing means before the transmission of the image data by the transmission means is completed. The restart of the processing means is executed according to the detection of the predetermined error, and the transmission of the image data whose transmission is not completed due to at least the predetermined error is started according to the restart of the processing means to the printing apparatus. characterized Rukoto which have a control means for controlling to.

According to the present invention, even when it is necessary to restart the processing means such as an error of the processing means for executing the expansion process for the received print data, the cause is a predetermined error without bothering the user. It is possible to start transmission of image data for which transmission has not been completed with .

It is a block diagram which shows roughly the structure of the printing system including DFE as an information processing apparatus which concerns on embodiment of this invention. It is a block diagram which shows schematic structure of DFE in FIG. It is a block diagram which shows schematic structure of the MFP in FIG. FIG. 4A is a block diagram schematically showing the configuration of the software module of the printing system of FIG. 1, FIG. 4A shows the configuration of the software module of the DFE, and FIG. 4B shows the configuration of the software module of the MFP. It is a sequence diagram which shows the procedure of the print job execution processing executed in the printing system of FIG. It is a figure which shows an example of the job management information used in the DFE of FIG. It is a flowchart which shows the procedure of the restart process executed by the monitoring process module of FIG. FIG. 8A is a sequence diagram for explaining a case where DFE is in a non-communication state in the printing system of FIG. 1, and FIG. 8A shows a case where DFE hangs when transferring image data, and FIG. 8B ) Shows the case where the DFE deadlock occurs during the transfer of the image data, and FIG. 8C shows the case where the DFE hangs during the transfer of the image data. It is a flowchart which shows the procedure of the restart process executed by the communication management module of FIG. It is a flowchart which shows the procedure of the job input processing executed by DFE of FIG. It is a sequence diagram which shows the procedure of the print resumption processing executed in the printing system of FIG. It is a sequence diagram which shows the procedure of the print resumption processing executed in the printing system of FIG. It is a flowchart which shows the procedure of the migration process executed by the MFP of FIG.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

In the present embodiment, the case where the present invention is applied to DFE (Digital Front End) as an information processing device will be described, but the application destination of the present invention is not limited to DFE, and for example, data communication with a processing execution device is possible. It may be a device such as a server. Further, in the present embodiment, the case where the present invention is applied to the MFP as the processing execution device will be described, but the application destination of the present invention is not limited to the MFP. For example, it may be an apparatus that acquires execution data from an information processing apparatus including an SFP (Single Function Printer) and an LBP (Laser Beam Printer) and performs processing based on the acquired execution data. Here, the execution data includes, for example, print data used by the MFP for printing.

FIG. 1 is a block diagram schematically showing a configuration of a printing system 100 including a DFE 102 as an information processing device according to an embodiment of the present invention.

In FIG. 1, the printing system 100 includes a client PC 101, a DFE 102, and an MFP 103. The client PC 101 and DFE 102 are connected via the network 104, and the DFE 102 and the MFP 103 are connected via the network 105.

The client PC 101 transmits PDL (Page Description Language) data to the DFE 102 as an execution instruction of the print process. The DFE 102 performs RIP (Raster Image Processor) processing based on the received PDL data, and generates image data such as raster image data that can be read by the MFP 103. Further, the DFE 102 transmits the image data and the print setting information used for the print process to the MFP 103 as print data, respectively. The MFP 103 prints based on the received print data.

FIG. 2 is a block diagram schematically showing the configuration of DFE102 in FIG.

In FIG. 2, the DFE 102 includes a CPU 201, a ROM 202, a RAM 203, an HDD 204, a display unit 205, an operation unit 206, and networks I / F 207 and 208. The CPU 201, ROM 202, RAM 203, HDD 204, display unit 205, operation unit 206, and networks I / F 207 and 208 are connected to each other via the system bus 209.

The CPU 201 comprehensively controls the entire DFE 102. The ROM 202 stores each program or the like executed by the CPU 201. The RAM 203 is used as a work area of the CPU 201 and a temporary storage area of each data of the CPU 201. HDD 204 is a non-volatile storage medium capable of holding data even when power is not supplied, and stores each program and each data. In the present embodiment, the HDD 204 stores the job management information 600 of FIG. 6, which will be described later, which manages a job for executing a print process (hereinafter, referred to as a “print job”). The display unit 205 displays each image. The operation unit 206 includes a keyboard, a mouse, and the like (not shown), and the setting information in the DFE 102 can be set by operating the operation unit 206 of the user. The networks I / F 207 and 208 perform data communication with each device connected to the network 104 and the network 105. In this embodiment, the network I / F 207 receives PDL data from the client PC 101 connected to the network 104. Further, the network I / F 208 transmits print data to the MFP 103 connected to the network 105.

FIG. 3 is a block diagram schematically showing the configuration of the MFP 103 in FIG.

In FIG. 3, the MFP 103 includes a CPU 301, a ROM 302, a RAM 303, an HDD 304, a display unit 305, an operation unit 306, a network I / F 307, a print control unit 308, and a printer unit 309. The CPU 301, ROM 302, RAM 303, HDD 304, display unit 305, operation unit 306, network I / F 307, and print control unit 308 are connected to each other via the system bus 310. The printer unit 309 is connected to the print control unit 308.

The CPU 301 controls the entire MFP 103 in an integrated manner. The ROM 302 stores each program or the like executed by the CPU 301. The RAM 303 is used as a work area of the CPU 301 and a temporary storage area of each data of the CPU 301. The HDD 304 stores each program and each data. The display unit 305 displays a setting screen or the like for making each setting of the MFP 103. The operation unit 306 receives the input information input by the user's operation as each setting information of the MFP 103. The network I / F 307 performs data communication with a device connected to the network 105, for example, DFE 102. The print control unit 308 instructs the printer unit 309 to start printing based on the received print data. The printer unit 309 prints based on an instruction from the print control unit 308.

4A and 4B are block diagrams schematically showing the configurations of software modules 400 and 405 of the printing system 100 in FIG. 1, FIG. 4A shows the configuration of software modules 400 of DFE102, and FIG. 4B shows the configuration of software modules 400 of DFE102. The configuration of the software module 405 of the MFP 103 is shown.

In FIG. 4A, the software module 400 includes a RIP processing module 401 (print data generation means), a communication management module 402, a transmission / reception processing module 403, and a monitoring processing module 404. Each process of the software module 400 is performed by the CPU 201 of the DFE 102 executing the program stored in the ROM 202.

The RIP processing module 401 stores the PDL data acquired from the client PC 101 in the RAM 203, and extracts print setting information from the stored PDL data. Further, the RIP processing module 401 RIP-processes the stored PDL data to generate image data, and transfers the generated image data to the MFP 103 as print data. The communication management module 402 manages the notification regarding the print process between the DFE 102 and the MFP 103 and manages the sequence of the print process of the MFP 103. The transmission / reception processing module 403 manages data communication between the client PC 101 and the MFP 103. The monitoring processing module 404 periodically performs data communication with the RIP processing module 401, and detects an abnormality in the state of the DFE 102. Specifically, the monitoring processing module 404 confirms whether or not the RIP processing module 401 is in a non-communication state such as a hang-up or a deadlock. When the RIP processing module 401 is in a communicable state, the transfer of image data from the DFE 102 to the MFP in the print job cannot be executed, and the print job including the transfer of the image data is interrupted. DFE102 needs to be restarted in order to resume the interrupted print job.

In FIG. 4B, the software module 405 includes a job control module 406 (transmission control means), a print processing module 407, and a transmission / reception processing module 408. Each process of the software module 405 is performed by the CPU 301 of the MFP 103 executing the program stored in the ROM 303.

The job control module 406 stores the print setting information as the print data acquired from the DFE 102 in the RAM 303, and analyzes the print setting information. As a result, preparations are made for storing the image data transmitted from the DFE 102. Specifically, the job control module 406 secures a part of the storage area of the RAM 304 as a primary buffer based on the analysis result of the print setting information. Further, the job control module 406 stores the image data acquired from the DFE 102 in the primary buffer, and instructs the print processing module 407 to execute printing. The print processing module 407 prints based on the print setting information and the image data stored in the RAM 304. The transmission / reception processing module 408 controls data communication with the DFE 102.

FIG. 5 is a sequence diagram showing a procedure of a print job execution process executed by the print system 100 of FIG.

The process of FIG. 5 is performed by the CPU 201 of the DFE 102 executing the program stored in the ROM 202, and the CPU 301 of the MFP 103 executing the program stored in the ROM 303. In the process of FIG. 5, as an example, it is assumed that only one page is printed.

In FIG. 5, first, the CPU 201 acquires the print setting information extracted by the RIP processing module 401, and notifies the communication management module 402 of the instruction to start the print job (step S501). The print setting information includes the name of print data, the paper size used for printing, the number of pages, the number of copies to be printed, and the like. Next, the CPU 201 transmits a print job start notification to the MFP 103 by the communication management module 402 (step S502). When the MFP 103 receives the print job start notification from the DFE 102, the CPU 301 sends a start confirmation notice indicating that the print job start notification has been confirmed to the DFE 102 (step S503), and starts the print job.

In the DFE 102, when the start confirmation notification is received from the MFP 103, the CPU 201 notifies the RIP processing module 401 of the ID information that can identify the print job and the fact that the print job has been started by the MFP 103 (step S504). Next, the CPU 201 sets the print job in the job management information 600 of FIG. 6, which will be described later, which manages the print job (step S505). The job management information 600 includes a job ID 601 and a job name 602. ID information that can identify the print job notified in step S504 is set in the job ID 601, and the name of the print data included in the print setting information is set in the job name 602. When the execution of the print job is completed, the information of the print job is deleted from the job management information 600. Further, the job management information 600 is stored in the HDD 204, which is a non-volatile storage medium, and is retained even if the DFE 102 is restarted. Next, the CPU 201 notifies the print setting information from the RIP processing module 401 to the communication management module 402 (step S506), and transmits the print setting information to the MFP 103 by the communication management module 402 (step S507).

When the MFP 103 receives the print setting information from the DFE 102, the CPU 301 starts preparing to store the image data based on the received print setting information, and when the preparation for storing the image data is completed, the process of step S510 described later is performed. Further, the CPU 301 transmits a reception confirmation notification indicating that the print setting information has been received to the DFE 102 (step S508). In the DFE 102, when the reception confirmation notification is received from the MFP 103, the CPU 201 notifies the RIP processing module 401 from the communication management module 402 that the print setting information has been confirmed by the MFP 103 (step S509). As a result, the RIP processing module 401 performs RIP processing to generate image data, and starts preparing to transfer the image data to the MFP 103. When the preparation for the transfer is completed, the CPU 201 performs the process of step S511 described later by the RIP processing module 401.

On the other hand, in the MFP 103, when the preparation for storage is completed, the CPU 301 transmits a transmission request notification requesting the transmission of image data to the DFE 102 (step S510). When printing a plurality of pages, the CPU 301 transmits a transmission request notification of image data corresponding to each page to the DFE 102.

In the DFE 102, when the preparation for transfer is completed, the CPU 201 sends a transfer preparation completion notification indicating that the preparation for transfer is completed from the RIP processing module 401 to the communication management module 402 (step S511). Next, when the communication management module 402 receives each of the transmission request notification from the MFP 103 and the transfer preparation completion notification from the RIP processing module 401, the CPU 201 transmits a transfer request notification indicating that the image data is transferred to the MFP 103 ( S step 512). When the MFP 103 receives the transfer request notification from the DFE 102, the CPU 301 transmits a transfer permission notification indicating that the transfer of the image data is permitted to the DFE 102 (step S513).

In the DFE 102, when the transfer permission notification is received from the MFP 103, the CPU 201 notifies the transfer start instruction for starting the image data transfer from the communication management module 402 to the RIP processing module 401 (step S514). Next, the CPU 201 transfers the image data from the RIP processing module 401 to the MFP 103 based on the transfer start instruction (step S515). Next, when the transfer of the image data is completed, the CPU 201 notifies the communication management module 402 from the RIP processing module 401 that the transfer of the image data is completed (step S516). Next, the CPU 201 transmits a transfer completion notification indicating that the transfer of the image data is completed to the MFP 103 (step S517). When the MFP 103 receives the transfer completion notification from the DFE 102, the CPU 301 transmits a transfer completion confirmation notification to the DFE 102 indicating that the transfer completion notification has been confirmed (step S518). In the DFE 102, when the transfer completion confirmation notification is received from the MFP 103, the CPU 201 notifies the RIP processing module 401 from the communication management module 402 that the transfer completion confirmation notification has been received (step S519), and ends this process.

For example, if the RIP processing module 401 is in a non-communication state during the transfer of the image data in step S515, the transfer of the image data cannot be executed, and the print job including the transfer of the image data is interrupted. In the conventional printing system, in order to restart the interrupted print job, the user needs to restart the DFE102 by himself / herself, and after the DFE102 is restarted, the user needs to give an instruction to restart the print job. That is, in the conventional printing system, when the RIP processing module 401 is in a non-communication state, the user is forced to take more time than necessary to restart the interrupted print job.

Corresponding to this, in the present embodiment, the monitoring processing module 404 and the communication management module 402 detect an abnormality in the state of the DFE 102, specifically, confirm whether or not the RIP processing module 401 is in a communication disabled state. .. When the RIP processing module 401 is in a non-communication state, the RIP processing module 401 and the communication management module 402 are restarted, and image data is transmitted to the MFP 103 based on the acquired execution status of the MFP 103.

FIG. 7 is a flowchart showing a procedure of the restart process executed by the monitoring process module 404 of FIG.

The process of FIG. 7 is performed by the CPU 201 of the DFE 102 executing the program stored in the ROM 202, and is periodically executed at preset intervals while the DFE 102 is running.

In FIG. 7, first, the CPU 201 transmits a survival confirmation notification for confirming whether or not the RIP processing module 401 is in a non-communication state from the monitoring processing module 404 to the RIP processing module 401 (step S701). Upon receiving the survival confirmation notification, the RIP processing module 401 normally transmits a response notification of the survival confirmation notification to the monitoring processing module 404. On the other hand, when the monitoring processing module 404 is in a non-communication state such as a hang-up, the RIP processing module 401 cannot send the response notification to the monitoring processing module 404. Next, the CPU 201 starts the survival confirmation timer process for measuring the elapsed time from the transmission of the survival confirmation notification by the monitoring processing module 404 (step S702). Next, the CPU 201 determines whether or not the response notification from the RIP processing module 401 has been received (step S703).

As a result of the determination in step S703, when the response notification from the RIP processing module 401 is not received, the CPU 201 determines whether or not a preset period has elapsed since the start of the survival confirmation timer processing, that is, whether or not a timeout has occurred. (Step S704).

As a result of the determination in step S704, when the time-out does not occur, the CPU 201 returns to the process of step S703. On the other hand, as a result of the determination in step S704, when the timeout occurs, the CPU 201 determines that the RIP processing module 401 is in a non-communication state. After that, the CPU 201 sets the recovery flag for setting the restart execution of the RIP processing module 401 and the communication management module 402 to ON. The CPU 201 sets the recovery flag on when the RIP processing module 401 and the communication management module 402 are restarted, and sets the recovery flag off when the RIP processing module 401 and the communication management module 402 are not restarted. To do. Next, the CPU 201 restarts the RIP processing module 401 (step S705) and restarts the communication management module 402 (step S706) (restart) based on the setting of the recovery flag, as shown in FIG. 8A. Execution means), this process is terminated.

As a result of the determination in step S703, when the response notification from the RIP processing module 401 is received, the CPU 201 ends the survival confirmation timer processing (step S707), and returns to the processing in step S701.

FIG. 9 is a flowchart showing a procedure of the restart process executed by the communication management module 402 of FIG.

The process of FIG. 9 is performed by the CPU 201 of the DFE 102 executing the program stored in the ROM 202.

In FIG. 9, first, when the CPU 201 receives the transmission request notification from the MFP 103 shown in step S510 of FIG. 5 (YES in step S901), the progress after receiving the transmission request notification by the communication management module 402. The communication abnormality timer process for measuring the time is started (step S902). Next, the CPU 201 determines, for example, whether or not the transfer preparation completion notification shown in step S511 of FIG. 5 has been received (step S903).

As a result of the determination in step S903, when the transfer preparation completion notification is not received, the CPU 201 determines whether or not a preset period has elapsed, that is, has timed out since the communication abnormality timer processing is started (step S904). .. In the present embodiment, if the transfer of the image data is not completed within a predetermined period after the MFP 103 transmits the transmission request notification, the MFP 103 will be in an error state. In this case, until the reset process such as restarting the MFP 103 is performed, the MFP 103 transitions to a state in which a new print job cannot be accepted (hereinafter, referred to as a “print job unacceptable state”), and the MFP 103 is newly used. Print job cannot be executed.

As a result of the determination in step S904, when the time-out does not occur, the CPU 201 returns to the process of step S903. On the other hand, as a result of the determination in step S904, when the time-out occurs, the CPU 201 determines that the RIP processing module 401 is in a non-communication state. After that, the CPU 201 assumes that the MFP 103 has transitioned to the unacceptable state of the print job, and transmits a recovery request notification for shifting to the acceptable state (executable state) of the print job to the MFP 103 (step S905). ). When the MFP 103, which has transitioned to the unacceptable state of the print job, receives the recovery request notification sent from the DFE 102 in step S905, the execution of the print job cancellation process is started. After that, when the execution of the print job cancellation process is completed, the MFP 103 shifts to the print job acceptable state.

The content of the recovery request notification and the method of canceling the print job are not particularly limited. The recovery request notification may be, for example, notifying the MFP 103 from the DFE 102 that the DFE 102 closes the communication port. The communication port of the DFE 102 is a communication port used by the communication management module 402 to transmit a print control command to the MFP 103. The MFP 102 may start the cancellation process of the print job based on the notification of closing the communication port. That is, the recovery request notification may have both a role of notifying that the communication port is closed and a role of the above-mentioned recovery request notification. Upon receiving the notification indicating that the port has been closed, the MFP 103 starts the process of shifting to the acceptable state of the print job. Alternatively, the recovery request notification may be a notification instructing the MFP 103 to delete the print job. The communication management module 402 may send both a first notification notifying the MFP 103 to close the communication port and a second notification instructing the MFP 103 to delete the print job to the MFP 103.

Next, as shown in FIG. 8B, the CPU 201 notifies the RIP processing module 401 of the restart instruction from the communication management module 402 (step S906). Here, if the recovery flag is already set to on and the RIP processing module 401 and the communication management module 402 are restarted by the processing of FIG. 7 before the processing of step S906, a DFE restart error occurs. It is highly possible that it has been resolved. In this case, in order to suppress the execution of unnecessary restart, the CPU 201 does not have to notify the RIP processing module 401 of the restart instruction as shown in FIG. 8A. After that, as shown in FIG. 8B, the CPU 201 sets the recovery flag on by the RIP processing module 401, and notifies the communication management module 402 of the restart instruction from the RIP processing module 401. After that, the CPU 201 restarts the RIP processing module 401 and the communication management module 402 to end this processing.

As a result of the determination in step S903, when the transfer preparation completion notification is received, the CPU 201 transmits a transfer request notification to the MFP 103 (for example, step S512 in FIG. 5). After that, when the CPU 201 receives the transfer permission notification from the MFP 103 (for example, step S513 in FIG. 5), the CPU 201 ends the communication abnormality timer process (step S907). Next, the CPU 201 notifies the transfer start instruction from the communication management module 402 to the RIP processing module 401 (step S908) (for example, step S514 in FIG. 5). Next, the CPU 201 starts the data transfer abnormality timer process for measuring the elapsed time from notifying the transfer start instruction by the communication management module 402 (step S909). Next, the CPU 201 determines whether or not the RIP processing module 401 has notified that the image data transfer has been completed, as in step S516 of FIG. 5 (step S910).

As a result of the determination in step S910, when the notification that the image data transfer is completed is not notified, the CPU 201 determines whether or not a preset period has elapsed since the data transfer abnormality timer processing is started, that is, whether or not a timeout has occurred. (Step S911).

As a result of the determination in step S911, when the time-out does not occur, the CPU 201 returns to the process of step S910. On the other hand, as a result of the determination in step S911, when the time-out occurs, the CPU 201 determines that the RIP processing module 401 is in a non-communication state. After that, the CPU 201 transmits a recovery request notification to the MFP 103 (step S912). As a result, the MFP 103 shifts to the print job acceptable state when the print job cannot be accepted. Next, the CPU 201 notifies the RIP processing module 401 of the restart instruction (step S913). Here, if the recovery flag is already set to on and the RIP processing module 401 and the communication management module 402 are restarted by the processing of FIG. 7 before the processing of step S913, a DFE restart error occurs. It is highly possible that it has been resolved. In this case as well, the CPU 201 does not have to notify the RIP processing module 401 of the restart instruction in order to suppress the execution of unnecessary restart. After that, the CPU 201 sets the recovery flag on by the RIP processing module 401, and notifies the communication management module 402 of the restart instruction from the RIP processing module 401. After that, the CPU 201 restarts the RIP processing module 401 and the communication management module 402 to end this processing.

As a result of the determination in step S910, when the notification that the image data transfer is completed is notified, the CPU 201 ends the data transfer abnormality timer process (step S914), and for example, as in step S517 of FIG. 5, the transfer completion notification. To the MFP 103. After that, for example, when the transfer completion confirmation notification is received from the MFP 103 as in step S518 of FIG. 5, the CPU 201 notifies the RIP processing module 401 that the transfer completion confirmation notification has been received (step S915) (for example, FIG. 5). Step S519). The CPU 201 ends this process after executing the process of step S915. That is, in the present embodiment, the abnormality of the state of DFE102 is detected by the processing of FIG. 7 by the monitoring processing module 404 and the processing of FIG. 9 by the communication management module 402.

FIG. 10 is a flowchart showing a procedure of job submission processing executed by DFE102 of FIG.

The process of FIG. 10 is performed by the CPU 201 of the DFE 102 executing the program stored in the ROM 202. Further, the process of FIG. 10 is executed after the restart of the RIP processing module 401 and the communication management module 402 (hereinafter, referred to as “restart in DFE102”) executed by the process of FIG. 7 and the process of FIG.

By the way, the DFE 102 uses the job management information 600 to determine whether or not the execution of the print job is completed, but the job management information 600 is a print indicating which process is executed in each print job. The job execution status is not included. Therefore, the DFE 102 cannot give an appropriate resumption instruction of the print job after the restart of the DFE 102 using only the job management information 600. For example, there is a possibility of giving an erroneous instruction to the print job in which the transfer of the image data from the DFE 102 to the MFP 103 is completed, such as executing the transfer of the image data again after restarting the DFE 102.

Corresponding to this, in the present embodiment, the execution status of the print job of the MFP 103 is acquired, and the print job is restarted based on the acquired execution status.

In FIG. 10, first, the CPU 201 performs a connection process with the MFP 103 in order to set data communication with the MFP 103 reset by restarting (step S1001). The connection process includes communication settings for transmitting image data and the like. Next, the CPU 201 confirms the set recovery flag and determines whether or not the recovery flag is set to ON (step S1002).

As a result of the determination in step S1002, when the recovery flag is set to off instead of on, the CPU 201 ends this process. On the other hand, as a result of the determination in step S1002, when the recovery flag is set to ON, the CPU 201 acquires the job management information 600 from the HDD 204 (step S1003). Next, the CPU 201 acquires the execution status of each print job in the MFP 103 from the MFP 103 based on the job ID set in the job management information 600. Specifically, the CPU 201 acquires the job status from the MFP 103 as the execution status of the print job (step S1004). The job status includes "normal output completed", "cancelled", "printing", "waiting for printing process", and "printing suspended". "Normal output completed" indicates that the execution of the print job has been completed, and "Cancelled" indicates that the image data included in the print job has been transferred due to the restart of the DFE 102 by the process of FIG. 7 or the process of FIG. Indicates that has been discontinued. "Printing" indicates that the print job is being printed, and "Waiting for printing" indicates that the print job is waiting for printing. “Printing is interrupted” indicates that printing of the print job is being interrupted, and includes interruption factors such as no paper, jam, and full output destination. Next, the CPU 201 determines whether or not the acquired job state is "cancelled" (step S1005).

As a result of the determination in step S1005, when the acquired job state is "cancelled", the print job in the job state has not completed the transfer of the image data from the DFE 102 to the MFP 103, so that the CPU 201 has the image data. Decide to resume the transfer. That is, the CPU 201 determines the restart of the print job including the transfer of the image data, and sets the print job in the restart print job list (not shown) that manages the print job instructing the restart (step S1006). Next, the CPU 201 performs the process of step S1008 described later.

As a result of the determination in step S1005, when the acquired job status is not "cancelled" but "normal output completed", "printing", "waiting for printing processing", or "printing interrupted". The print job in the job state has at least completed the transfer of image data from the DFE 102 to the MFP 103. That is, since the DFE 102 process in the print job has been completed, the CPU 201 does not set the print job in the restart print job list. After that, the CPU 201 displays the job status of each print job on the display unit 205 (step S1007), and determines whether or not the job status of all the print jobs of the job management information 600 has been confirmed (step S1008).

As a result of the determination in step S1008, when the job status of any of the print jobs in the job management information 600 is not confirmed, the CPU 201 returns to the process in step S1004. On the other hand, when the job status of all the print jobs of the job management information 600 is confirmed as a result of the determination in step S1008, the CPU 201 inputs each print job set in the restart print job list (step S1009). As a result, the process of FIG. 5 is executed in each of the submitted print jobs, and the print job interrupted due to the restart of the DFE 102 is restarted. Next, the CPU 201 sets the recovery flag to off (step S1010), and ends this process.

11A and 11B are sequence diagrams showing a procedure of print resumption processing executed by the printing system 100 of FIG.

The processes of FIGS. 11A and 11B are performed by the CPU 201 of the DFE 102 executing the program stored in the ROM 202 and the CPU 301 of the MFP 103 executing the program stored in the ROM 303. As an example of the processing of FIGS. 11A and 11B, the DFE 102 is restarted at the timing when the job status of the print job A is "normal output completed" and the job status of the print job B is "printing". This case will be described.

In FIG. 11A, first, the CPU 201 performs the process of step S1001 of FIG. Specifically, the CPU 201 notifies the communication management module 402 of an instruction to execute the connection process from the RIP processing module 401 (step S1101). Next, the CPU 201 transmits a connection request notification requesting execution of the connection process to the MFP 103 by the communication management module 402 (step S1102). When the MFP 103 receives the connection request notification from the DFE 102, the CPU 301 determines whether or not the MFP 103 is in a print job acceptable state (step S1103). In step S1103, when the execution of the print job cancellation process is completed, the CPU 301 determines that the MFP 103 is in the print job acceptable state. On the other hand, when the execution of the print job cancellation process is not completed, the CPU 301 determines that the MFP 103 is in an unacceptable state for the print job. For example, the CPU 301 determines whether or not the execution of the print job cancellation process has been completed based on whether or not the print job queue is empty. If the print job queue is empty at the timing when the connection request notification is received, the CPU 301 determines that the execution of the cancel process has been completed. On the other hand, when the print job remains in the print job queue, the CPU 301 determines that the execution of the cancel process has not been completed.

As a result of the determination in step S1103, when the MFP 103 is in an unacceptable state for the print job, the CPU 301 performs the processes after step S1115 in FIG. 11B, which will be described later. On the other hand, as a result of the determination in step S1103, when the MFP 103 is in a print job acceptable state, the CPU 301 transmits a connection permission notification including setting information and the like used for the connection process to the DFE 102 (step S1104). In the DFE 102, when the connection permission notification is received from the MFP 103, the CPU 201 notifies the communication management module 402 to the RIP processing module 401 of the setting information and the like used for the connection processing (step S1105). As a result, the data communication setting between DFE102 and MFP103 is performed.

Next, the CPU 201 determines whether or not the set recovery flag is on (for example, step S1002 in FIG. 10). When the recovery flag is on, the job management information 600 is acquired from the HDD 204 (for example, step S1003 in FIG. 10). Next, the CPU 201 executes the process of step S1004 of FIG. Specifically, the CPU 201 notifies the communication management module 402 of an instruction to confirm the job status of the print job A from the RIP processing module 401 (step S1106). Next, the CPU 201 transmits a job status transmission request notification requesting transmission of the job status of the print job A to the MFP 103 by the communication management module 402 (step S1107). When the MFP 103 receives the job status transmission request notification of the print job A from the DFE 102, the CPU 301 transmits the job status notification including the job status of the print job A to the DFE 102 (step S1108). In the DFE 102, when the job status notification is received from the MFP 103, the CPU 201 notifies the job status of the print job A from the communication management module 402 to the RIP processing module 401 (step S1109). As a result, the RIP processing module 401 acquires the job status of the print job A. Since the job status of the print job A is "printing", the transfer of the image data included in the print job A is completed. Therefore, the CPU 201 displays the execution status of the print job A on the display unit 205 of the DFE 102 without setting the print job A in the restart job management list (for example, step S1007 in FIG. 10). Next, the CPU 201 determines whether or not the job states of all the print jobs of the job management information 600 have been confirmed (for example, step S1008 in FIG. 10). Among the print jobs set in the job management information 600, for example, when the job status of the print job B is not confirmed, the CPU 201 executes the process of step S1004 of FIG. 10 for the print job B. Specifically, the CPU 201 notifies the communication management module 402 of an instruction to confirm the job status of the print job B from the RIP processing module 401 (step S1110). Next, the CPU 201 transmits the job status transmission request notification of the print job B to the MFP 103 by the communication management module 402 (step S1111). When the MFP 103 receives the job status transmission request notification of the print job B from the DFE 102, the CPU 301 transmits the job status notification including the job status of the print job B to the DFE 102 (step S1112). In the DFE 102, when the job status notification is received from the MFP 103, the CPU 201 notifies the job status of the print job B from the communication management module 402 to the RIP processing module 401 (step S1113). As a result, the RIP processing module 401 acquires the job status of the print job B. Since the job status of the print job B is "cancelled", the transfer of the image data of the print job B is not completed. Therefore, the CPU 201 sets the print job B in the restart job management list (for example, step S1006 in FIG. 10). Next, when the CPU 201 confirms the job status of all the print jobs of the job management information 600 (for example, YES in step S1008 of FIG. 10), the CPU 201 executes the processes of steps S1009 and S1010 of FIG. As a result, the CPU 201 transfers the image data of the print job B to the MFP 103 by the RIP processing module 401. That is, in the present embodiment, only the print job whose execution has been stopped due to the restart of the DFE 102 is restarted. In the MFP 103, when the transfer of the image data is completed, the CPU 301 starts printing the print job B (step S1114), and ends this process.

As a result of the determination in step S1103, when the MFP 103 is in an unacceptable state for the print job, in FIG. 11B, the CPU 301 displays an error screen on the display unit 305 in the MFP 103 (step S1115). By checking the error screen, the user can manually cancel the job that has not been canceled, or manually turn off / on the power of the MFP 103 in order to eliminate the error.

Next, the CPU 301 performs the process of step S1104 and notifies the DFE 102 of the occurrence of an error (S1116). In DFE102, when the occurrence of an error is notified from the MFP 103, the CPU 201 does not perform the processing after step S1105, and displays an error screen indicating that an error has occurred in the MFP 103 on the display unit 205 (step S1117). This makes it possible to prevent the DFE 102 from unnecessarily resubmitting the print job to the MFP 103 even though the MFP 103 is in an unacceptable state for the print job. After that, the CPU 201 ends this process.

According to the above-described embodiment, when an abnormality in the state of the DFE 102 is detected, the RIP processing module 401 and the communication management module 402 are restarted, and the print job is restarted based on the acquired execution status of the MFP 103. Will be done. As a result, even if the image data cannot be transferred due to the abnormal state of the DFE102 and the print job including the transfer of the image data is interrupted, the user gives an instruction to restart the DFE102 or restart the print job. The execution of the print job is restarted in the MFP 103 without performing the above. That is, the interrupted print job can be restarted without bothering the user.

Further, in the above-described embodiment, only the print job whose execution has been stopped due to the abnormal state of DFE102 is executed. As a result, it is possible to prevent the print job that has been executed from being executed again by mistake, and as a result, the execution time of the entire process can be shortened.

Further, in the above-described embodiment, if the MFP 103 does not receive the image data within the preset period, the MFP 103 transitions to the print job unacceptable state, and the print job can be accepted according to the restart of the DFE 102. The request request notification to be transferred to is transmitted to the MFP 103. As a result, even if the MFP 103 cannot receive the image data during the set period due to the abnormal state of the DFE 102 and transitions to the unacceptable state of the print job, it is linked to the restart of the DFE 102. The MFP 103 can be moved to the acceptable state of the print job. As a result, the print job can be executed without delay.

In the above-described embodiment, since the job status is transmitted from the MFP 103 to the DFE 102, it is possible to make the DFE 102 reliably identify the print job whose execution has been stopped due to the abnormality of the status of the DFE 102.

Although the present invention has been described above using the embodiments, the present invention is not limited to the above-described embodiments.

For example, the MFP 103 may determine whether or not the DFE 102 is in a non-communication state, and the MFP 103 may be shifted to a print job acceptable state based on the determination result.

FIG. 12 is a flowchart showing a procedure of the migration process executed by the MFP 103 of FIG.

The process of FIG. 12 is performed by the CPU 301 of the MFP 103 executing the program stored in the ROM 303, and is periodically executed at preset intervals while the MFP 103 is running.

In FIG. 12, first, the CPU 301 transmits a survival confirmation notice confirming whether or not the DFE 102 is in a non-communication state to the DFE 102 (step S1201). When the DFE102 receives the survival confirmation notification, normally, the response notification of the survival confirmation notification is transmitted to the MFP103, but when the DEF102 is in a non-communication state such as during restart, the DEF102 transmits the response notification to the MFP103. I can't. Next, the CPU 301 starts the survival confirmation timer process for measuring the elapsed time since the survival confirmation notification is transmitted (step S1202). Next, the CPU 301 determines whether or not the response notification from the DFE 102 has been received (step S1203).

As a result of the determination in step S1203, when the response notification is not received, the CPU 301 determines whether or not a preset period has elapsed since the start of the survival confirmation timer processing, that is, whether or not a timeout has occurred (step S1204).

As a result of the determination in step S1204, when the time-out does not occur, the CPU 301 returns to the process of step S1203. On the other hand, when the time-out occurs as a result of the determination in step S1204, the CPU 301 cancels the printing job being executed (step S1205). Next, when the MFP 103 is in the unacceptable state of the print job, the CPU 301 shifts the MFP 103 to the acceptable state of the print job (step S1206), and ends this process.

When the response notification is received as a result of the determination in step S1203, the CPU 301 ends the survival confirmation timer processing (step S1207), and determines whether or not all the submitted print jobs have been executed (step). S1208).

As a result of the determination in step S1208, when the execution of any of the submitted print jobs is not completed, the CPU 301 returns to the process of step S1201. On the other hand, as a result of the determination in step S1208, when the execution of all the submitted print jobs is completed, the CPU 301 ends this process.

In the process of FIG. 12 described above, the MFP 103 is shifted to the acceptable state of the print job based on the response notification of the survival confirmation notification transmitted from the MFP 103. As a result, even if the recovery request notification is not transmitted from the DFE 102 to the MFP 103, the MFP 103 can be moved to the acceptable state of the print job, and the print job can be printed without delay.

The present invention supplies a program that realizes one or more functions of the above-described embodiment to a system or device via a network or storage medium, and one or more processors in the computer of the system or device read the program. It can also be realized by the process to be executed. The present invention can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

102 DFE
103 MFP
201 CPU
401 RIP processing module 402 Communication management module 404 Monitoring processing module 406 Job control module

Claims (9)

A receiving means that receives print data from an information processing device, a processing means that executes a decompression process on the print data received by the receiving means, and an image data generated by executing the decompression process by the processing means. A control device having a transmission means for transmitting data to a printing device.
The processing means is restarted according to the detection of a predetermined error of the processing means before the transmission of the image data by the transmitting means is completed, and at least the predetermined error is executed according to the restart of the processing means. control device according to claim Rukoto which have a control means for controlling to start transmission to the printing device of the image data that did not complete the transmission by. Control device according to claim 1, wherein the further Yusuke Rukoto detecting means for detecting the predetermined error of the processing means. The control device according to claim 2 , wherein the detection means gives a predetermined notification to the processing means, and detects the error according to the absence of a response to the predetermined notification for a predetermined time . The control device according to any one of claims 1 to 3, further comprising a measuring means for measuring the predetermined time . The print data is PDL (Page Description Language) data, the expansion process RIP (Raster Image Processor) controller according to any one of claims 1 to 4, characterized in der Rukoto. The control device according to any one of claims 1 to 5, wherein the predetermined error is a hang-up . The receiving means is a first interface and
The control device according to any one of claims 1 to 6, wherein the transmission means is a second interface different from the first interface . A receiving means that receives print data from an information processing device, a processing means that executes a decompression process on the print data received by the receiving means, and an image data generated by executing the decompression process by the processing means. Is a control method of a control device having a transmission means for transmitting the data to the printing device.
The processing means is restarted according to the detection of a predetermined error of the processing means before the transmission of the image data by the transmitting means is completed, and at least the predetermined error is executed according to the restart of the processing means. control method of the control device according to claim Rukoto to have a control step of controlling so as to initiate the transmission to the printing device of the image data that did not complete the transmission by. A program for causing a computer to function as a control device according to any one of claims 1 to 7 .

Images