JP2017130177A - Information processor, processing execution device, control method of information processor, control method of processing execution device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processor capable of restoring a series of suspended processing without imposing any load to a user.SOLUTION: A DFE 102 is configured so that, when an abnormality is detected on the condition of the DFE 102, to activate an RIP processing module 401 and a communication management module 402, and the image data is transmitted to an MFP103 based on the acquired execution state of the MFP 103.SELECTED DRAWING: Figure 10

Description

  The present invention relates to an information processing device that executes processing based on execution data, a processing execution device, a control method for the information processing device, a control method for the processing execution device, and a program.

  There is known a printing system that controls execution of a printing process in which an MFP as a processing execution apparatus performs printing based on print data transmitted from a DFE (Digital Front End) as an information processing apparatus. In the print processing, the DFE performs RIP processing based on the print execution instruction received from the client PC to generate print data including image data, print setting information, and the like, and the MFP based on the print data transmitted from the DFE. Print. In the printing system, if an error occurs during execution of a printing process, for example, a communication error between the DFE and the MFP, 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 resumed 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).

JP 2011-040043 A

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

  An object of the present invention is to provide an information processing device, a processing execution device, a control method for the information processing device, a control method for the processing execution device, which can resume the interrupted processing without causing the user to take more time than necessary. And providing a program.

  In order to achieve the above object, an information processing apparatus according to the present invention is an information processing apparatus that transmits execution data to a process execution apparatus, a transmission unit that transmits the execution data to the process execution apparatus; A detection means for detecting an abnormal state of the apparatus; a restart execution means for executing a restart of the information processing apparatus; and an acquisition means for acquiring an execution status of execution data of the process execution apparatus. When an abnormality in the state of the apparatus is detected, the restart execution unit restarts the information processing apparatus, and after the restart is executed, the transmission unit is based on the execution status acquired by the acquisition unit. The execution data is transmitted to the process execution device.

  In order to achieve the above object, a processing execution apparatus of the present invention is a processing execution apparatus that executes processing based on execution data acquired from the information processing apparatus according to any one of claims 1 to 5. And a transmission control means for controlling the transmission of the execution data from the information processing apparatus by transmitting the execution status of the execution data to the information processing apparatus.

  According to the present invention, it is possible to resume the interrupted process without taking time and effort to the user.

1 is a block diagram schematically showing a configuration of a printing system including a DFE as an information processing apparatus according to an embodiment of the present invention. FIG. 2 is a block diagram schematically showing a configuration of a DFE in FIG. 1. FIG. 2 is a block diagram schematically showing the configuration of the MFP in FIG. 1. FIGS. 4A and 4B are block diagrams schematically showing the configuration of software modules of the printing system of FIG. 1, FIG. 4A shows the configuration of DFE software modules, and FIG. 4B shows the configuration of MFP software modules. FIG. 2 is a sequence diagram illustrating a procedure of print job execution processing executed in the printing system of FIG. 1. It is a figure which shows an example of the job management information used by DFE of FIG. It is a flowchart which shows the procedure of the restart process performed by the monitoring process module of FIG. FIG. 8 is a sequence diagram for explaining a case where the DFE is in an incommunicable state in the printing system of FIG. 1. FIG. 8A shows a case where a DFE hang-up occurs during transfer of image data, and FIG. ) Shows a case where a DFE deadlock occurs when transferring image data, and FIG. 8C shows a case where a DFE hang-up occurs when transferring image data. It is a flowchart which shows the procedure of the restart process performed by the communication management module of FIG. 3 is a flowchart illustrating a procedure of job input processing executed by the DFE of FIG. 1. FIG. 2 is a sequence diagram illustrating a procedure of a print resumption process that is executed in the printing system of FIG. 1. FIG. 2 is a sequence diagram illustrating a procedure of a print resumption process that is executed in the printing system of FIG. 1. 3 is a flowchart showing a procedure of a 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 a DFE (Digital Front End) as an information processing apparatus will be described. However, the application destination of the present invention is not limited to the DFE, and for example, data communication with a processing execution apparatus is possible. It may be a device such as a server. In the present embodiment, a case where the present invention is applied to an MFP as a processing execution apparatus will be described. However, an application destination of the present invention is not limited to an MFP. For example, a device that acquires execution data from an information processing device including an SFP (Single Function Printer) or an LBP (Laser Beam Printer) and performs processing based on the acquired execution data may be used. 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 apparatus 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 the 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 a print processing execution instruction. 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. The DFE 102 transmits the image data and print setting information used for the printing process to the MFP 103 as print data. The MFP 103 performs printing based on the received print data.

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

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

  The CPU 201 controls the entire DFE 102 in an integrated manner. The ROM 202 stores each program executed by the CPU 201. The RAM 203 is used as a work area for the CPU 201 and a temporary storage area for each data of the CPU 201. The HDD 204 is a non-volatile storage medium that can retain data even when power is not supplied, and stores each program and each data. In the present embodiment, the HDD 204 stores job management information 600 shown in FIG. 6 (described later) for managing a job for executing a printing process (hereinafter referred to as “print job”). The display unit 205 displays each image. The operation unit 206 includes a keyboard and a mouse (not shown), and setting information in the DFE 102 can be set by a user operation on the operation unit 206. Network I / Fs 207 and 208 perform data communication with each device connected to the network 104 or the network 105. In the present embodiment, the network I / F 207 receives PDL data from the client PC 101 connected to the network 104. 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.

  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 a system bus 310. The printer unit 309 is connected to the print control unit 308.

  The CPU 301 controls the entire MFP 103 as a whole. The ROM 302 stores each program executed by the CPU 301. A RAM 303 is used as a work area for the CPU 301 and a temporary storage area for each data of the CPU 301. The HDD 304 stores each program and each data. A display unit 305 displays a setting screen for performing each setting of the MFP 103. The operation unit 306 receives input information input by a user 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, the 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 performs printing based on an instruction from the print control unit 308.

  FIG. 4 is a block diagram schematically showing the configuration of the software modules 400 and 405 of the printing system 100 in FIG. 1, FIG. 4A shows the configuration of the software module 400 of the DFE 102, and FIG. 2 shows a configuration of a software module 405 of the MFP 103.

  4A, the software module 400 includes a RIP processing module 401 (print data generation unit), 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 a 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. Also, the RIP processing module 401 generates image data by performing RIP processing on the stored PDL data, and transfers the generated image data to the MFP 103 as print data. The communication management module 402 manages the notification regarding the printing process between the DFE 102 and the MFP 103 and manages the sequence of the printing 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 checks whether or not the RIP processing module 401 is in a communication disabled state such as a hangup or deadlock. If the RIP processing module 401 is in a communication disabled state, 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. In order to resume the interrupted print job, it is necessary to restart the DFE 102.

  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 a program stored in the ROM 303.

  The job control module 406 stores print setting information as print data acquired from the DFE 102 in the RAM 303, and analyzes the print setting information. Thereby, preparation for storing the image data transmitted from the DFE 102 is performed. 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. 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. A print processing module 407 performs printing based on print setting information and 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 illustrating a procedure of print job execution processing executed by the printing system 100 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 a print job start instruction (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, 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 a print job start notification from the DFE 102, the CPU 301 transmits a start confirmation notification indicating that the print job start notification has been confirmed to the DFE 102 (step S503), and starts the print job.

  When the DFE 102 receives a start confirmation notification from the MFP 103, the CPU 201 notifies the RIP processing module 401 that ID information that can identify the print job and that the MFP 103 has started the print job (step S504). Next, the CPU 201 sets the print job in job management information 600 shown in FIG. 6 (to be described later) for managing the print job (step S505). The job management information 600 includes a job ID 601 and a job name 602. In the job ID 601, ID information that can identify the print job notified in step S504 is set, and in the job name 602, the name of print data included in the print setting information is set. When the execution of the print job is completed, the information on the print job is deleted from the job management information 600. The job management information 600 is stored in the HDD 204, which is a non-volatile storage medium, and is retained even after 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 the communication management module 402 transmits the print setting information to the MFP 103 (step S507).

  In MFP 103, when print setting information is received from DFE 102, CPU 301 starts preparation for storing image data based on the received print setting information, and when the storage preparation is completed, processing in step S510 described below 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). When the DFE 102 receives a reception confirmation notification 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). Accordingly, the RIP processing module 401 performs RIP processing to generate image data, and starts preparation for transferring the image data to the MFP 103. When the preparation for the transfer is completed, the CPU 201 performs a process of step S511 described later by the RIP processing module 401.

  On the other hand, when the preparation for storing is completed in the MFP 103, the CPU 301 transmits a transmission request notification requesting 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 from the RIP processing module 401 to the communication management module 402 indicating that the preparation for transfer is complete (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 to the MFP 103 a transfer request notification indicating that the image data is to be transferred ( S step 512). In MFP 103, when a transfer request notification is received from DFE 102, CPU 301 transmits a transfer permission notification indicating that transfer of image data is permitted to DFE 102 (step S513).

  When the DFE 102 receives a transfer permission notification from the MFP 103, the CPU 201 notifies the communication management module 402 to the RIP processing module 401 of a transfer start instruction for starting transfer of image data (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 has been 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 indicating that the transfer completion notification has been confirmed to the DFE 102 (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 this processing ends.

  For example, when the RIP processing module 401 is in a communication disabled 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 resume an interrupted print job, the user himself / herself restarts the DFE 102, and after the DFE 102 restarts, the user needs to instruct the print job to resume. That is, in the conventional printing system, when the RIP processing module 401 is in a communication disabled state, the user is forced to take more time than necessary to resume the interrupted print job.

  In response 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, and specifically check whether the RIP processing module 401 is in a communication disabled state. . When the RIP processing module 401 is in a communication disabled 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 restart processing executed by the monitoring processing module 404 of FIG.

  The processing of FIG. 7 is performed by the CPU 201 of the DFE 102 executing a program stored in the ROM 202, and is periodically executed at a preset interval while the DFE 102 is activated.

  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 communication disabled state from the monitoring processing module 404 to the RIP processing module 401 (step S701). When 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 an incommunicable state such as hang-up, the RIP processing module 401 cannot transmit the response notification to the monitoring processing module 404. Next, the CPU 201 causes the monitoring processing module 404 to start a survival confirmation timer process for measuring an elapsed time after transmitting the survival confirmation notification (step S702). Next, the CPU 201 determines whether or not a 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 a preset period has elapsed since the start of the survival confirmation timer process, that is, whether a time-out has occurred. (Step S704).

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

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

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

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

  In FIG. 9, first, for example, when the CPU 201 receives a transmission request notification from the MFP 103 shown in step S <b> 510 of FIG. 5 (YES in step S <b> 901), the process since the communication management module 402 received the transmission request notification. Communication abnormality timer processing for measuring time is started (step S902). Next, for example, the CPU 201 determines whether or not a 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 since the start of the communication abnormality timer process, that is, whether a time-out has occurred (step S904). . In the present embodiment, if the transfer of image data is not completed before a predetermined period elapses after the MFP 103 transmits the transmission request notification, the MFP 103 enters an error state. In this case, the MFP 103 transitions to a state where it cannot accept a new print job (hereinafter referred to as “print job cannot be accepted”) until a reset process such as restarting the MFP 103 is performed, and the MFP 103 is newly set. Print jobs cannot be executed.

  If the time-out does not occur as a result of the determination in step S904, the CPU 201 returns to the process in step S903. On the other hand, if the result of the determination in step S904 is that a timeout has occurred, the CPU 201 determines that the RIP processing module 401 is in a communication disabled state. Thereafter, the CPU 201 assumes that the MFP 103 has transitioned to a print job unacceptable state, and transmits a recovery request notification to the MFP 103 to shift to a print job acceptable state (executable state) (step S905). ). When the MFP 103 that has transitioned to the print job unacceptable state receives the recovery request notification transmitted from the DFE 102 in step S905, execution of the print job cancel process is started. Thereafter, when the execution of the print job cancel process is completed, the MFP 103 shifts to a print job acceptable state.

  The contents of the recovery request notification and the print job cancel processing method are not particularly limited. The recovery request notification may be, for example, notification from the DFE 102 to the MFP 103 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 print job cancel processing based on the notification of closing the communication port. In other words, the recovery request notification may serve both as a role of notifying that the communication port is closed and a role as the above-described recovery request notification. When the MFP 103 receives a notification indicating that the port is closed, the MFP 103 starts a process of shifting to a print job acceptable state. Alternatively, the recovery request notification may be a notification for instructing the MFP 103 to delete the print job. The communication management module 402 may transmit to the MFP 103 both a first notification that notifies the MFP 103 that the communication port is to be closed and a second notification that instructs the MFP 103 to delete the print job.

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

  As a result of the determination in step S903, when receiving a transfer preparation completion notification, the CPU 201 transmits a transfer request notification to the MFP 103 (for example, step S512 in FIG. 5). Thereafter, when receiving a 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 RIP processing module 401 of a transfer start instruction from the communication management module 402 (step S908) (for example, step S514 in FIG. 5). Next, the CPU 201 causes the communication management module 402 to start data transfer abnormality timer processing for measuring the elapsed time since the transfer start instruction was notified (step S909). Next, the CPU 201 determines whether or not the transfer of the image data has been notified from the RIP processing module 401, for example, as in step S516 in FIG. 5 (step S910).

  As a result of the determination in step S910, when it is not notified that the transfer of the image data has been completed, the CPU 201 determines whether or not a preset period has elapsed since the start of the data transfer abnormality timer process, that is, whether or not a time-out has occurred. (Step S911).

  If the time-out does not occur as a result of the determination in step S911, the CPU 201 returns to the process in step S910. On the other hand, when the result of the determination in step S911 is that a timeout has occurred, the CPU 201 determines that the RIP processing module 401 is in a communication disabled state. Thereafter, the CPU 201 transmits a recovery request notification to the MFP 103 (step S912). As a result, when the MFP 103 has transitioned to a print job unacceptable state, the MFP 103 transitions to a print job acceptable state. Next, the CPU 201 notifies the RIP processing module 401 of a restart instruction (step S913). Here, if the recovery flag has already been set to ON and the RIP processing module 401 and the communication management module 402 have been restarted by the processing of FIG. 7 before performing the processing of step S913, a DFE restart error will occur. It is highly possible that it has been resolved. Also in this case, the CPU 201 does not need to notify the RIP processing module 401 of a restart instruction in order to suppress unnecessary restart. Thereafter, the CPU 201 sets the recovery flag to ON by the RIP processing module 401 and notifies the communication management module 402 of a restart instruction from the RIP processing module 401. Thereafter, the CPU 201 restarts the RIP processing module 401 and the communication management module 402 and ends this processing.

  As a result of the determination in step S910, when it is notified that the transfer of the image data has been completed, the CPU 201 ends the data transfer abnormality timer process (step S914). For example, as shown in step S517 in FIG. Is transmitted to the MFP 103. Thereafter, for example, when a transfer completion confirmation notification is received from the MFP 103 as in step S518 in 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 the process after executing the process of step S915. That is, in the present embodiment, an abnormality in the state of the DFE 102 is detected by the processing in FIG. 7 by the monitoring processing module 404 and the processing in FIG. 9 by the communication management module 402.

  FIG. 10 is a flowchart showing a procedure of job input processing executed by the DFE 102 of FIG.

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

  The DFE 102 uses the job management information 600 to determine whether or not the execution of the print job has been completed. The job management information 600 indicates a print process indicating which process is being executed in each print job. The job execution status is not included. For this reason, the DFE 102 cannot issue an appropriate restart instruction for a print job after restarting in the DFE 102 only with the job management information 600. For example, for a print job in which image data transfer from the DFE 102 to the MFP 103 has been completed, there is a possibility that after the restart in the DFE 102, an erroneous instruction is made to execute the image data transfer again.

  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 connection processing with the MFP 103 in order to perform data communication setting with the MFP 103 reset by restart (step S <b> 1001). The connection process includes communication settings for transmitting image data. 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 not on but set to off, 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”, and “printing suspended”. “Normal output complete” indicates that the execution of the print job has been completed, and “Cancelled” indicates transfer of image data included in the print job due to the restart of the DFE 102 by the processing of FIG. 7 or the processing of FIG. Indicates that has been canceled. “Printing” indicates that the print job is being printed, and “Waiting for print processing” indicates that the print job is waiting for printing. “Printing suspended” indicates that printing of a print job is suspended, and includes interruption factors such as no paper, jam, and full discharge destination. Next, the CPU 201 determines whether or not the acquired job status is “cancelled” (step S1005).

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

  As a result of the determination in step S1005, when the acquired job status is not “cancelled” but is “normal output complete”, “printing”, “waiting for printing”, and “printing suspended” The print job in the job state has at least completed transfer of image data from the DFE 102 to the MFP 103. That is, since the processing of the DFE 102 in the print job has been completed, the CPU 201 does not set the print job in the restart print job list. Thereafter, 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 print jobs in 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 print job in the job management information 600 is not confirmed, the CPU 201 returns to the process in step S1004. On the other hand, as a result of the determination in step S1008, when the job statuses of all print jobs in the job management information 600 are confirmed, the CPU 201 inputs each print job set in the resume print job list (step S1009). As a result, the process shown in FIG. 5 is executed for each input print job, and the print job suspended due to the restart in the DFE 102 is resumed. Next, the CPU 201 sets the recovery flag to OFF (step S1010) and ends this process.

  FIG. 11A and FIG. 11B are sequence diagrams showing the procedure of the print restart process executed by the print system 100 of FIG.

  11A and 11B 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. 11A and 11B, for example, the DFE 102 is restarted at a 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”. The 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 connection processing from the RIP processing module 401 (step S1101). Next, the CPU 201 transmits a connection request notification requesting execution of connection processing 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 the MFP 103 is ready to accept a print job (step S1103). In step S <b> 1103, when the execution of the print job cancel process is completed, the CPU 301 determines that the MFP 103 is in a print job accepting state. On the other hand, when the execution of the print job cancel process has not been completed, the CPU 301 determines that the MFP 103 is in a state where the print job cannot be accepted. 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, if a 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 a state where it cannot accept a print job, the CPU 301 performs processing after step S1115 in FIG. On the other hand, as a result of the determination in step S1103, when the MFP 103 is ready to accept a print job, the CPU 301 transmits a connection permission notification including setting information used for connection processing to the DFE 102 (step S1104). When the DFE 102 receives the connection permission notification from the MFP 103, the CPU 201 notifies the communication management module 402 to the RIP processing module 401 of setting information used for the connection processing (step S1105). Thereby, data communication setting between the DFE 102 and the MFP 103 is performed.

  Next, the CPU 201 determines whether or not the set recovery flag is on (for example, step S1002 in FIG. 10). If 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 in 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 a 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 resume job management list (for example, step S1007 in FIG. 10). Next, the CPU 201 determines whether or not the job statuses of all print jobs in the job management information 600 have been confirmed (for example, step S1008 in FIG. 10). Of 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 in FIG. 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 a 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 a 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 resume job management list (for example, step S1006 in FIG. 10). Next, when the CPU 201 confirms the job states of all print jobs in the job management information 600 (for example, YES in step S1008 in FIG. 10), the CPU 201 executes the processes in steps S1009 and S1010 in FIG. As a result, the CPU 201 uses the RIP processing module 401 to transfer the image data of the print job B to the MFP 103. In other words, in the present embodiment, only print jobs whose execution has been canceled due to restart in the DFE 102 are resumed. 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 the process is terminated.

  As a result of the determination in step S1103, when the MFP 103 is not ready to accept a print job, in FIG. 11B, in the MFP 103, the CPU 301 displays an error screen on the display unit 305 (step S1115). By checking the error screen, the user can manually cancel a job that has not been cancelled, or manually turn off / on the MFP 103 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 the DFE 102, when the occurrence of an error is notified from the MFP 103, the CPU 201 does not perform the processing from step S1105 and displays an error screen indicating that an error has occurred in the MFP 103 on the display unit 205 (step S1117). As a result, it is possible to prevent the DFE 102 from unnecessarily re-entering the print job in the MFP 103 even though the MFP 103 is in a state where the print job cannot be accepted. Thereafter, 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 resumed based on the acquired execution status of the MFP 103. Is done. As a result, even if the transfer of image data cannot be executed due to an abnormality in the state of the DFE 102 and the print job including the transfer of the image data is interrupted, the user instructs the restart operation of the DFE 102 or the restart of the print job. The execution of the print job is resumed in the MFP 103 without performing the above. In other words, the interrupted print job can be resumed without taking time for the user.

  Further, in the present embodiment described above, only a print job that has been canceled due to an abnormal state of the DFE 102 is executed. Accordingly, it is possible to prevent a print job that has been executed from being erroneously executed again, and as a result, it is possible to shorten the execution time of the entire process.

  Further, in the present embodiment described above, when the MFP 103 does not receive image data in a preset period, the MFP 103 shifts to a print job unacceptable state, and accepts a print job according to the restart of the DFE 102. A request request notification for shifting to is sent to the MFP 103. As a result, even if the MFP 103 cannot receive the image data during the set period due to an abnormality in the state of the DFE 102 and transits to a state where the print job cannot be accepted, the MFP 103 is interlocked with the restart of the DFE 102. The MFP 103 can be shifted to a print job accepting state. As a result, the print job can be executed without delay.

  In the present embodiment described above, since the job status is transmitted from the MFP 103 to the DFE 102, it is possible to reliably cause the DFE 102 to specify a print job that has been canceled due to an abnormality in the status of the DFE 102.

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

  For example, the MFP 103 may determine whether or not the DFE 102 is in a communication disabled 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 the procedure of the migration process executed by the MFP 103 in FIG.

  The processing in FIG. 12 is performed by the CPU 301 of the MFP 103 executing a program stored in the ROM 303, and is periodically executed at a preset interval while the MFP 103 is activated.

  In FIG. 12, first, the CPU 301 transmits a survival confirmation notification for confirming whether or not the DFE 102 is in a communication disabled state to the DFE 102 (step S1201). When the DFE 102 receives the survival confirmation notification, the DFE 102 normally transmits a response notification of the survival confirmation notification to the MFP 103. However, if the DEF 102 is in a communication-disabled state such as during a restart, the DEF 102 transmits the response notification to the MFP 103. I can't. Next, the CPU 301 starts a survival confirmation timer process for measuring an elapsed time after transmitting the survival confirmation notification (step S1202). Next, the CPU 301 determines whether or not a response notification from the DFE 102 has been received (step S1203).

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

  If the time-out does not occur as a result of the determination in step S1204, the CPU 301 returns to the process in step S1203. On the other hand, if the result of determination in step S1204 is that a timeout has occurred, the CPU 301 cancels the print job being executed (step S1205). Next, when the MFP 103 is in a state where it cannot accept a print job, the CPU 301 shifts the MFP 103 to a state where it can accept a print job (step S1206), and ends this processing.

  When the response notification is received as a result of the determination in step S1203, the CPU 301 ends the survival confirmation timer process (step S1207), and determines whether or not the execution of all the input print jobs has been completed (step S1207). S1208).

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

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

  The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read the program. It can also be realized by processing executed in the above. 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 (11)

An information processing device that transmits execution data to a process execution device,
Transmitting means for transmitting the execution data to the process execution device;
Detecting means for detecting an abnormal state of the information processing apparatus;
Restart execution means for restarting the information processing apparatus;
Obtaining means for obtaining execution status of execution data of the processing execution device,
When an abnormality in the state of the information processing apparatus is detected, the restart execution means restarts the information processing apparatus, and the execution of the transmission means acquired by the acquisition means after the restart is executed. An information processing apparatus that transmits execution data to the process execution apparatus based on a situation.   The information processing apparatus according to claim 1, wherein the transmission unit transmits only execution data that has not been executed by the process execution apparatus to the process execution apparatus. Further comprising notification means for notifying the processing execution device,
If the process execution device does not receive the execution data in a set period, it transitions to an error state,
2. The notification unit according to claim 1, wherein, in response to the restart of the information processing apparatus, the notification unit performs notification for shifting the execution data from the error state to an executable state. 2. The information processing apparatus according to 2.   The information processing apparatus according to claim 1, wherein the execution data includes print data for printing. Print data generation means for generating the print data by performing RIP (Raster Image Processor) processing;
The information processing apparatus according to claim 4, wherein the detection unit detects an abnormal state of the print data generation unit. A processing execution device that executes processing based on execution data acquired from the information processing device according to any one of claims 1 to 5,
A process execution apparatus comprising: a transmission control unit configured to transmit an execution status of the execution data to the information processing apparatus and control transmission of the execution data from the information processing apparatus. Further comprising receiving means for receiving a notification from the information processing apparatus;
If the execution data is not received within a set period, the execution data transitions to an inexecutable state,
The process execution apparatus according to claim 6, wherein the execution data is shifted to a state in which the execution data can be executed based on a notification transmitted in response to restart of the information processing apparatus. A method of controlling an information processing device that transmits execution data to a process execution device,
A transmission step of transmitting the execution data to the process execution device;
A detection step of detecting an abnormality in the state of the information processing apparatus;
A restart execution step of executing a restart of the information processing apparatus;
Obtaining an execution status of execution data of the processing execution device,
When an abnormality in the state of the information processing apparatus is detected, the restart execution step restarts the information processing apparatus, and the transmission step is acquired in the acquisition step after the restart is executed. A control method for an information processing apparatus, wherein execution data is transmitted to the process execution apparatus based on a situation. A method for controlling a processing execution device that executes processing based on execution data acquired from the information processing device according to any one of claims 1 to 5,
A method for controlling a processing execution apparatus, comprising: a transmission control step for transmitting an execution status of the execution data to the information processing apparatus and controlling transmission of the execution data from the information processing apparatus. A program for causing a computer to execute a control method of an information processing apparatus that transmits execution data to a process execution apparatus,
The control method of the information processing apparatus includes:
A transmission step of transmitting the execution data to the process execution device;
A detection step of detecting an abnormality in the state of the information processing apparatus;
A restart execution step of executing a restart of the information processing apparatus;
Obtaining an execution status of execution data of the processing execution device,
When an abnormality in the state of the information processing apparatus is detected, the restart execution step restarts the information processing apparatus, and the transmission step is acquired in the acquisition step after the restart is executed. A program that transmits execution data to the process execution device based on a situation. A program for causing a computer to execute a control method of a processing execution device that executes processing based on execution data acquired from the information processing device according to any one of claims 1 to 5,
The control method of the processing execution device is:
A program comprising: a transmission control step of transmitting an execution status of the execution data to the information processing apparatus and controlling transmission of the execution data from the information processing apparatus.

Images