Print processing system and printing system, error notification method, and program

Abstract

To solve the problem in which: in retention printing, a user does not notice an error occurring during rendering of print data until execution of printing, which causes re-execution.SOLUTION: A print processing system renders print data received from a terminal, and stores print data generated by the rendering. When an error occurs during the rendering, the print processing system notifies the terminal of the error.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to a printing system such as a reservation printing system, and more particularly to a print processing system, a printing system, an error notification method, and a program. [Background technology]

[0002] Conventionally, reservation printing has been one of the printing methods for multifunction printing devices (MFPs). In reservation printing, when print data is sent from a client terminal such as a personal computer (PC) to a print server, the print data is saved on the print server. After that, the print data saved on the print server can be selected from the operation panel of the MFP and printed (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2018-118419 Summary of the Invention [Problem to be solved by the invention]

[0004] With reservation printing, when a user performs a print execution operation on the MFP, the print management server performs a rendering process to convert the print data into a data format that the MFP can print, and then prints the data. Rendering here refers to the process of adjusting the resolution of the document and images, adjusting the document's page layout and position, and setting the output format of the printed material, and converting the data into a data format that the MFP 120 can print, such as PDF, JPEG, or TIFF. However, if the print data is corrupted or encrypted, rendering fails and an error occurs. In this case, an error notification is displayed on the MFP panel, allowing the user to check the error on the MFP. However, because the error is displayed after the print execution operation on the MFP, the user is forced to return to their PC, correct the print data, and repeat the transmission process.

[0005] In contrast, in the reservation printing method described in Patent Document 1, the image forming device analyzes the print job data received from the PC, and if an error occurs, adds an error message corresponding to the error to the bibliographic information of the print job. Patent Document 1 also discloses a method for displaying the error message when the user displays the print job list on the operation unit of the image forming device. Thus, Patent Document 1 displays the print job list on the image forming device and displays the page number on which the error will occur before the user instructs the start of printing, allowing the user to instruct the device to print up to the page before the error occurred. However, even with the technology described in Patent Document 1, the error message is displayed on the operation unit of the image forming device, so for pages after the page on which the error occurred, the user must return to the PC, correct the print data, and resubmit the print job. As described above, with conventional reservation printing, errors require rework, which places a heavy burden on the user and reduces productivity.

[0006] The present invention has been made in consideration of the above-mentioned conventional example, and has an object to reduce the inconvenience to the user by speeding up the notification of an error when performing reservation printing. [Means for solving the problem]

[0007] In order to achieve the above object, the present invention has the following configuration: That is, according to one aspect of the present invention, a rendering unit that renders print data received from a terminal; a storage means for storing the print data generated by rendering; and a notification means for notifying the terminal of an error when an error occurs during rendering. A print processing system is provided. [Effects of the Invention]

[0008] According to the present invention, it is possible to speed up the notification of an error when performing reservation printing, thereby reducing the workload on the user. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates a configuration of a printing system. [Figure 2] FIG. 2 is a block diagram showing a schematic configuration of an MFP 120. [Figure 3] 1 is a block diagram showing a schematic configuration of a client terminal 110, a print management server 140, and a data conversion server 150. FIG. [Figure 4] 10 is a sequence diagram showing the flow of a process for saving print data in the print management server 140. FIG. [Figure 5] FIG. 10 is a diagram showing a print setting screen displayed on the client terminal 110. [Figure 6] FIG. 10 is a diagram showing a print number display screen displayed on the client terminal 110. [Figure 7] FIG. 10 is a diagram showing an error notification screen displayed on the client terminal 110. [Figure 8] FIG. 10 is a diagram showing a screen displayed on the client terminal 110 during generation of print data. [Figure 9] 10 is a sequence diagram showing the flow of processing in which the MFP 120 prints and executes print data reserved in the print management server 140. FIG. [Figure 10] FIG. 10 is a diagram showing a print number input screen displayed by the MFP 120. [Figure 11] FIG. 10 is a sequence diagram showing the flow of processing for saving print data in the print management server 140 according to the second embodiment. [Figure 12] FIG. 10 is a diagram showing an error notification screen displayed on the client terminal 110. [Figure 13] FIG. 10 is a sequence diagram of a second embodiment showing the flow of a process in which the MFP 120 prints and executes print data reserved in the print management server 140. [Figure 14] FIG. 11 is a sequence diagram showing the flow of processing for saving print data in the print management server 140 according to the third embodiment. [Figure 15] 10 is a flowchart showing a rendering process performed by the data conversion server 150. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention claimed. Although multiple features are described in the embodiments, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0011] <<Embodiment 1>> <Overall structure> Fig. 1 is a diagram showing the overall configuration of a printing system. The printing system in Fig. 1 includes a client terminal 110 and a multifunction printer (MFP) 120, and also includes a print management server 140 and a data conversion server 150 connected to the client terminal 110 and the MFP 120 via a network 130. Here, the print management server 140 and the data conversion server 150 may be collectively referred to as a print processing system.

[0012] Network 130 may be, for example, a local area network (LAN), a wide area network (WAN), a telephone line, a dedicated digital line, an asynchronous transfer mode (ATM), a frame relay line, a cable television line, a wireless line for data broadcasting, or a so-called communications network such as the Internet realized by a combination of these.

[0013] The client terminal 110 and the MFP 120 are connected to the Internet via an access point. The client terminal 110 may be an information processing device, i.e., a device including a computer. The client terminal 110 is equipped with a web browser and applications and can transmit print data and print setting information to the print management server 140 via the network 130. The client terminal 110 also has a message function 111. The message function 111 refers to a function that can receive messages such as email, SMS, and chat apps, but is not limited to email, SMS, and chat apps. The client terminal 110 may be any terminal that can connect to the Internet, such as a smartphone, tablet, or general-purpose personal computer. The MFP 120 is a multifunction device that has multiple functions such as a scanner and printer, and is an example of an image processing device.

[0014] The print management server 140 provides functions for managing print data, such as storing print data, creating print jobs, and sending print jobs, in response to communication with the client terminal 110 and the MFP 120 .

[0015] The data conversion server 150 performs rendering processing to convert the print data received from the print management server 140 into a data format that can be printed by the MFP 120. Specifically, the data conversion server 150 adjusts the resolution of documents and images, adjusts the page layout and placement of documents, sets the output format of printed materials, and converts the data into a data format that can be printed by the MFP 120, such as PDF, JPEG, or TIFF.

[0016] The print management server 140 and the data conversion server 150 may be realized by one server computer, or may be realized by three or more server computers.

[0017] <Hardware configuration> 2 is a block diagram showing the schematic configuration of the MFP 120 as an image processing device. In the MFP 120, the printing function is realized by a printer unit 201, the scanner function is realized by a scanner unit 202, and the storage function is realized by a memory card mounting unit 203 and a memory card 204. The printer unit 201 prints image data received from an external source or image data stored in the memory card 204 onto printing paper using a recording method such as inkjet or electrophotography. It also manages ink information including the amount of remaining ink and paper information including the number of sheets of paper in the load.

[0018] The scanner unit 202 optically reads an original placed on a platen (not shown) and converts it into electronic data, and then transmits the image data converted into a specified file format to an external device via a network or stores it in a storage area (not shown) such as a HDD. The copy service is realized by transferring image data generated by reading an original placed on the platen with the scanner unit 202 to the printer unit 201, which then prints the image data on printing paper.

[0019] Various file data are stored in a memory card 204 inserted into a memory card insertion section 203. This file data can be read and edited from an external device via a network. It is also possible to store file data in the memory card 204 from an external device.

[0020] The MFP 120 further includes a CPU 205, a program memory 206, a work memory 207, a display unit 208, an operation unit 209, a network communication unit 210, a network connection unit 211, and a flash memory 212. The CPU 205 is a central processing unit for controlling each unit within the MFP 120. The program memory 206 is configured with a ROM or the like and stores various program codes and an application 214 for communicating with a server device. The application 214 also accesses the printer unit 201 to obtain information on consumables such as ink and paper. The work memory 207 is configured with a RAM or the like and temporarily stores or buffers image data when executing each service. The display unit 208 is configured with, for example, an LCD and displays various information. The operation unit 209 includes switches and the like that allow the user to perform various input operations. The display unit 208 and operation unit 209 may be implemented as an integrated touch panel or the like. The network communication unit 210 connects the MFP 120 to a network and performs various communications. A network such as the Internet can be connected via a network connection unit 211. The network communication unit 210 is compatible with wired LAN and wireless LAN, and in the case of wired LAN compatibility, the network connection unit 211 is a connector for connecting a wired LAN cable, and in the case of wireless LAN compatibility, the network connection unit 211 serves as an antenna. The flash memory 212 is a non-volatile memory for storing image data and the like received by the network communication unit 210. The above-mentioned units are connected to each other via a bus 213.

[0021] FIG. 3 is a block diagram showing a schematic configuration of the client terminal 110, the print management server 140, and the data conversion server 150. As shown in FIG.

[0022] The CPU 301 is a central processing unit that controls the following components. The disk device 302 stores various files, including application programs 312, databases 313, and operating systems that are read by the CPU 301. The external storage medium reader 303 is a device for reading information, such as files, stored on an external storage medium such as an SD card. The memory 304 is composed of RAM or the like, and performs temporary data storage and buffering as needed by the CPU 301. The display unit 305 is composed of, for example, an LCD, and displays various information. The operation unit 306 includes a keyboard, mouse, and the like for users to perform various input operations. The network communication unit 307 is connected to a network such as the Internet via a network connection unit 308 and performs various communications. The network communication unit 307 supports both wired and wireless LANs. In the case of a wired LAN, the network connection unit 308 is a connector for connecting a wired LAN cable. In the case of a wireless LAN, the network connection unit 308 is an antenna. Note that the network connection unit 308 may support both wired and wireless LANs. The USB communication unit 310 is connected to various peripheral devices via a USB connection unit 311 and performs various communications. The above-mentioned units are connected to each other via a bus 309. The client terminal 110 in Fig. 3 is shown with a display unit 305 and an operation unit 306 shown separately. However, the present invention is not limited to this, and a touch panel display or the like in which the display unit and operation unit are integrated may also be used.

[0023] <Overall processing flow> Print data rendering In this embodiment, the process from when the client terminal 110 sends print data to the print management server 140 in response to a user operation until the client terminal 110 displays a notification received from the print management server 140 on the display unit 305 of the terminal will be described. FIG. 4 is a sequence diagram showing this process. Note that in FIG. 4, the operations performed by each device are realized by the CPU of each device executing a program loaded into memory. Furthermore, the operation of the client terminal 110 may be, for example, the operation of a web browser executed on the client terminal 110.

[0024] First, in S401, the client terminal 110 transmits to the print management server 140 print data and print settings that the user has set by operating the client terminal 110. FIG. 5 shows an example of a print setting screen displayed on the display unit 305 of the client terminal 110. Details of this processing will be described later. Next, in S402, the print management server 140 transmits the print data and print settings received from the client terminal 110 to the data conversion server 150. In S403, the data conversion server 150 renders the print data received from the print management server 140. In this rendering, the print data is converted into a data format that can be printed by the MFP 120 based on the print settings received from the print management server 140. Specifically, based on the received print settings, the print data is converted into a data format that can be printed by the MFP 120, such as PDF, JPEG, or TIFF, by adjusting the resolution of the document and images, adjusting the page layout and placement of the document, and setting the output format of the printed material. During rendering by the data conversion server 150, a rendering error may occur if the print data is corrupted, encrypted, or in a format not supported by the rendering engine being used.

[0025] If no error occurs during rendering by the data conversion server 150 in S403, the data conversion server 150 transmits the rendered print data to the print management server 140 in S404. The rendered print data refers to print data generated by the rendering process. Next, in S405, the print management server 140 issues identification information corresponding to the received print data, such as a print number. The print number here is a unique number associated with the print job to identify it. In S406, the print management server 140 associates the rendered print data received from the data conversion server 150 with the print number issued in S405 and stores the associated print job in the database 313. Thereafter, in S407, the print management server 140 transmits the issued print number to the client terminal 110. In S408, the client terminal 110 displays the print number received from the print management server 140 on the display unit 305 of the terminal. FIG. 6 shows a print number display screen on the client terminal. Details of this process will be described later.

[0026] Furthermore, if an error occurs during rendering in the data conversion server 150 in S403, the data conversion server 150 sends an error notification to the print management server 140 in S409. The content of the error notification does not simply notify the occurrence of an error, but may vary depending on the type of error. In S410, the print management server 140 sends the error notification received from the data conversion server 150 to the client terminal 110. In S411, the client terminal 110 displays the error notification received from the print management server 140 on the display unit 305 of the terminal. An example of a print error screen displayed on the client terminal 110 is shown in FIG. 7. Details of this processing will be described later.

[0027] FIG. 5 shows a print setting screen 500 on the client terminal 110. The upload area 501 is an area for uploading files, and files can be uploaded using buttons or drag-and-drop. The print settings 502 are a field for selecting print setting information. The print settings 502 include the number of copies to be printed, paper size, layout, double-sided printing settings, print color settings, and print range. Note that the print settings 502 are not limited to the number of copies to be printed, paper size, layout, double-sided printing settings, print color settings, and print range. The print settings 502 also implement a function for accepting input using an input box or selection box. The user uploads a file in the upload area 501, edits the print settings in the print settings 502, and presses the print button 503 to send the print data and print settings in S401. Thereafter, while the data conversion server 150 is performing rendering, the client terminal 110 displays the print data generation screen shown in FIG. 8. Note that the period during which rendering is being performed may be the period until the client terminal 110 receives from the print management server 140 the notification of the print number in S407 or the error notification in S411.

[0028] 6 shows the print number display screen displayed on the client terminal 110 for the print number sent by the print management server 140 at step S407. A print number display screen 600 shows the GUI framework of the print number display screen, and a display field 601 is the display field for the print number. When the print number is sent from the print management server 140 in step S407, FIG. 6 is displayed on the display unit 305 of the client terminal 110.

[0029] 7 shows the display screen of the error notification sent by the print management server 140 at the time of sending the error notification S410. The error notification display screen 700 shows the GUI framework of the error notification display screen, and a display field 701 is a display field for the error notification content. The error notification content may vary depending on the type of error, or may be left blank if simply notifying that an error has occurred.

[0030] Fig. 8 shows a print data generation screen 800 that is displayed on the client terminal 110 while the data conversion server 150 is performing rendering in S403. If no error occurs in the rendering by the data conversion server 150, the screen moves to the print number display screen 600 in Fig. 6, and if an error occurs in the rendering, the screen moves to the error notification display screen 700 in Fig. 7.

[0031] ●Printing procedure Next, Figure 9 shows a sequence diagram illustrating the process from when MFP 120 sends the print number entered by the user by operating display unit 208 of MFP 120 to print management server 140 to when MFP 120 prints the print job reserved in print management server 140.

[0032] First, in S901, the MFP 120 transmits to the print management server 140 a print number that the user inputs by operating the operation unit 209 of the MFP 120. The print number input by the user here is the print number displayed on the client terminal 110 in S408. FIG. 10 shows a print number input screen on the display unit 208 of the MFP 120. Details of the process will be described later. The print number may be input not only on the panel of the MFP 120 but also on a screen linked to a smartphone linked to the MFP 120. Next, in S902, the print management server 140 searches for a print job linked to the print number received from the MFP 120. In S903, the print management server 140 transmits a print instruction for the print job obtained by the search to the MFP 120. In S904, the MFP 120 receives the print instruction from the print management server 140 and executes printing. The print instruction received by the MFP 120 includes the print job obtained by the search.

[0033] 10 shows the basic configuration of a screen on the display unit 208 of the MFP 120 where the user inputs a print number. An input screen 1000 shows the framework of the GUI on the MFP 120. The input screen 1000 is displayed when the user performs a predetermined operation. When the user inputs a print number in a number input field 1001 and presses a start print button 1002, the print number is sent to the print management server 140.

[0034] With the above-described configuration and procedure, in this embodiment, an error can be notified to the client terminal, allowing the user to know that an error has occurred before going to an image forming apparatus such as an MFP, thereby reducing the need for rework.

[0035] In the present embodiment, an example has been described in which print data received from the client terminal 110 is stored in the print management server 140 and associated with a print number, thereby executing the stored print job. Alternatively, the print management server 140 may store the received print data associated with a user, and the MFP 120 may execute the stored print job associated with the authenticated user through user authentication. In this case, rendering of the print data is performed before user authentication in the MFP 120, so that errors that occur during rendering can be checked by the client terminal 110 when the print data is submitted. The time of submission of the print data may be when the print data is sent from the client terminal 110 and rendered. The same applies to the following embodiments.

[0036] <<Embodiment 2>> In the first embodiment, after the client terminal 110 transmits the print data and print settings entered by the user to the print management server 140 on the print setting screen in Fig. 5, the data conversion server 150 performs rendering processing. The user then waits on the print data generation screen in Fig. 8 until the rendering processing is complete. However, if the size of the print data is large, rendering can take time, which can keep the user waiting.

[0037] In this embodiment, after the client terminal 110 transmits the print data and print settings to the print management server 140, the print management server 140 issues a print number and transmits it to the client terminal 110 without waiting for the rendering to be completed. If an error occurs during rendering in the data conversion server 150, an error notification is sent to the client terminal 110 by a message notification method such as email or chat, thereby reducing the user's waiting time.

[0038] <Overall processing flow> Print data rendering In this embodiment, the process from when the client terminal 110 sends print data to the print management server 140 in response to a user operation until the client terminal 110 displays a notification received from the print management server 140 on the terminal's display unit 305 will be described. Figure 11 is a sequence diagram showing this process. The configuration of each device and the entity that executes the process are the same as in the first embodiment.

[0039] First, in S1101, the client terminal 110 transmits print data and print settings set by the user operating the client terminal 110 to the print management server 140. Next, in S1102, the print management server 140 issues a print number. In S1103, the print management server 140 transmits the issued print number to the client terminal 110. Thereafter, in S1104, the client terminal 110 displays the print number received from the print management server 140 on the display unit 305 of the terminal. FIG. 6 shows a print number display screen on the client terminal 110.

[0040] Meanwhile, in S1105, the print management server 140 transmits the print data and print settings received from the client terminal 110 to the data conversion server 150. At this time, identification information may be attached to the print data transmitted to the data conversion server 150 so that the rendered print data can be linked to the issued print number. The print number may be used as the identification information. In S1106, the data conversion server 150 renders the print data received from the print management server 140. If no error occurs in the rendering by the data conversion server 150 in S1106, in S1107, the data conversion server 150 transmits the rendered print data to the print management server 140. At this time, the rendered print data may be attached with the identification information received from the print management server 140 together with the print data. This makes it possible to link the rendered print data to the issued print number. Then, in S1108, the print management server 140 associates the rendered print data received from the data conversion server 150 with the print number issued in S1102, and stores the associated data in the database 313 as a print job.

[0041] Furthermore, if an error occurs in the rendering by the data conversion server 150 in S1106, in S1109 the data conversion server 150 sends an error notification to the print management server 140. At this time, the error notification may be accompanied by identification information received from the print management server 140 along with the print data. This allows the error notification to be linked to the issued print number. Then, in S1110, the print management server 140 links the error notification received from the data conversion server 150 to the print number issued in S1102 and stores them in the database 313.

[0042] In S1111, the print management server 140 transmits the error notification received from the data conversion server 150 to the client terminal 110. At this time, the error notification may be transmitted to the message function 111 in the client terminal 110 by a messaging method such as email or chat. The client terminal to which the error notification is transmitted does not have to be the client terminal 110 that transmitted the print data. In this case, the destination address or the like may be set in advance in the print management server 140 for each user, for example. Alternatively, the destination address may be transmitted from the client terminal 110 to the print management server 140 together with the print data. Note that the destination of the print number in S1103 may also be the same as the destination of the error notification.

[0043] Next, in S1112, the message function 111 in the client terminal 110 displays the error notification received from the print management server 140 on the display unit 305 of the terminal. Fig. 12 shows an error notification screen displayed by the client terminal 110. This error notification screen may be displayed by the message function 111 of the client terminal 110 if an error notification has been sent to the message function 111.

[0044] 12 shows the basic configuration of a screen on which the client terminal 110 displays the error notification content received from the print management server 140 in S1112. Screen 1200 shows the GUI framework of the client terminal 110, and includes a message 1201 that notifies the content of the error that occurred during rendering in the data conversion server 150. Screen 1200 may be displayed by the message function 111 of the client terminal 110 when an error notification has been sent to the message function 111.

[0045] ●Printing procedure Next, a process will be described in which the user operates the operation unit 209 of the MFP 120 to input a print number and transmit it to the print management server 140, and the MFP 120 prints the print job reserved in the print management server 140, or the MFP 120 displays an error notification. A sequence diagram of this process is shown in FIG.

[0046] First, in S1301, the MFP 120 transmits to the print management server 140 a print number that the user inputs by operating the operation unit 209 of the MFP 120. The print number input by the user here is the print number that was displayed on the client terminal 110 in S1102. FIG. 10 shows a print number input screen on the display unit 208 of the MFP 120. Next, in S1302, the print management server 140 searches for the print number received from the MFP 120. If the searched print number is associated with rendered print data, in S1303 the print management server 140 transmits a print instruction for the print job to the MFP 120. The print instruction may include the print job. In S1304, the MFP 120 receives the print instruction from the print management server 140 and executes printing.

[0047] On the other hand, if the print management server 140 searches for the print number in S1302 and finds that the searched print number is associated with an error notification, then in S1305 the print management server 140 sends the error notification associated with the print number to the MFP 120. Then, in S1306, the MFP 120 displays the error notification received from the print management server 140 on the display unit 208. The error notification screen here has an error notification content display field 701, just like the error notification screen displayed on the client terminal 110 in Fig. 7. Note that the error notification content may vary depending on the type of error, or may be left blank if simply notifying that an error has occurred.

[0048] As explained above, issuing a print number before rendering can shorten the user's waiting time for rendering. Furthermore, if an error occurs during rendering, an error notification is sent to the client terminal at the time of the error occurrence, for example, by a message notification method such as email or chat. This allows the client terminal to notify the user of the error in a timely manner, reducing the need to retry the printing process. Furthermore, even if the user operates the MFP to instruct printing before the error notification, if an error occurs, the MFP will notify the user of the error, so the user can be reliably notified of the error.

[0049] <<Embodiment 3>> In the second embodiment, the print management server 140 issues a print number before the data conversion server 150 executes rendering on the print setting screen of Fig. 5, and if an error occurs, an error notification is sent to the client terminal 110. It has also been mentioned that the error notification may be sent to the message function 111 of the client terminal by a messaging method such as email or chat. This reduces the waiting time for rendering.

[0050] As explained above, there are various causes of rendering errors. For example, an error may occur when the print data is corrupted, or the print file may not be opened because the print data is encrypted. The timing at which these errors occur varies depending on the type of error.

[0051] Therefore, in this embodiment, the burden of waiting on the user can be reduced by changing the medium and timing of notifying the user of an error depending on the type of error or the timing of the error. For example, when attempting to open print data (e.g., a file), an error may occur because the file type is not supported or the file is corrupted. Since such errors occur quickly after a print instruction is issued, the user does not have to wait for a long time even if the error is sent to the terminal that issued the print instruction. Therefore, such errors that occur within a short period after the print instruction are notified to the terminal that issued the print instruction. On the other hand, since the timing of an error that occurs during rendering of print data cannot be predicted, if an error notification is sent to the terminal that issued the print instruction, the user must wait until rendering is complete. Therefore, by notifying such errors to, for example, the user's mobile device, the user does not have to wait at the terminal that issued the print instruction. This embodiment discloses such a system and process.

[0052] <Overall processing flow> In this embodiment, the process from when the client terminal 110 transmits print data to the print management server 140 in response to a user operation until when the client terminal 110 displays a notification received from the print management server 140 on the display unit 305 of the terminal will be described. Fig. 14 is a sequence diagram showing this process.

[0053] First, in S1401, the client terminal 110 transmits print data and print settings set by the user operating the client terminal 110 to the print management server 140. Next, in S1402, the print management server 140 transmits the print data and print settings received from the client terminal 110 to the data conversion server 150. In S1403, the data conversion server 150 opens the print data to perform rendering of the print data received from the print management server 140. The print data is, for example, a data file, and in this case, this data file (also referred to as a print data file) is opened. Here, FIG. 15 shows the processing performed by the data conversion server 150 from receiving the print data to transmitting the rendering results to the print management server 140. Details of this processing will be described later.

[0054] If the data conversion server 150 fails to open the print data file in S1403, then in S1404 the data conversion server 150 sends a data opening error notice to the print management server 140. In S1405, the print management server 140 sends the data opening error notice received from the data conversion server 150 to the client terminal 110. In S1406, the client terminal 110 displays the data opening error notice received from the print management server 140 on the display unit 305 of the terminal. Fig. 7 shows an error notice screen on the client terminal 110.

[0055] On the other hand, if the data conversion server 150 succeeds in opening the print data file in S1403, the data conversion server 150 sends a rendering start notification to the print management server 140 in S1407. Next, in S1408, the print management server 140 issues a print number. Thereafter, in S1409, the print management server 140 sends the issued print number to the client terminal 110. In S1410, the client terminal 110 displays the print number received from the print management server 140 on the display unit 305 of the terminal. FIG. 6 shows the print number display screen on the client terminal. Following S1407, in S1411, the data conversion server 150 performs rendering of the print data.

[0056] If an error occurs in rendering by the data conversion server 150 in S1411, the data conversion server 150 sends a rendering error notification to the print management server 140 in S1412. Then, in S1413, the print management server 140 associates the error notification received from the data conversion server 150 with the print number issued in S1408 and stores them in the database 313. In S1414, the print management server 140 sends the rendering error notification received from the data conversion server 150 to the client terminal 110, for example, its message function 111. In S1415, the client terminal 110, for example, its message function 111, displays the rendering error notification received from the print management server 140 on the display unit 305 of the terminal. FIG. 12 shows a rendering error screen displayed by the client terminal 110, for example, its message function 111.

[0057] On the other hand, if no error occurs in the rendering by the data conversion server 150 in S1411, then in S1416 the data conversion server 150 transmits the rendered print data to the print management server 140. Then, in S1417, the print management server 140 associates the rendered print data received from the data conversion server 150 with the print number generated in S1408 and stores them in the database 313 as a print job.

[0058] ●Rendering process by data conversion server FIG. 15 is a flowchart of rendering performed by the data conversion server 150, and shows the processing from when the data conversion server 150 receives print data and print settings from the print management server 140 to when it sends the rendering processing results to the print management server 140.

[0059] First, in S1501, print data and print settings are received from the print management server 140. Next, in S1502, the print data is opened. In S1503, it is determined whether the print data could be opened. If the print data could not be opened, in S1504, a data opening error notice is sent to the print management server 140.

[0060] If the print data can be opened in S1503, a print rendering start notification is sent to the print management server 140 in S1505. Thereafter, the print data is rendered in S1506. In S1507, it is determined whether an error occurred in rendering the print data. If an error occurred in rendering, a rendering error notification is sent to the print management server 140 in S1508. If no error occurred in rendering the print data in S1507, the rendered print data is sent to the print management server 140 in S1509.

[0061] As described above, the client terminal can notify the user of an error in a timely manner depending on the type of error, thereby reducing the burden of waiting on the user. Furthermore, as in the first and second embodiments, it is possible to reduce the need to retry printing. Furthermore, even if the user operates the MFP to instruct printing before receiving an error notification, if an error has occurred, the MFP will notify the user of the error, so the user can be reliably notified of the error.

[0062] Summary of embodiments The above embodiments can be summarized as follows: (Item 1) a rendering means for rendering print data received from the terminal; a storage means for storing the print data generated by rendering; and a notification means for notifying the terminal of an error when an error occurs during rendering. A print processing system comprising: (Item 2) Item 1, a printing processing system, The notification means notifies the error using a message function. A print processing system comprising: (Item 3) Item 1 or 2, the print processing system, The terminal that sent the print data and the terminal that notifies the error are different terminals. A print processing system comprising: (Item 4) Item 3. The print processing system according to item 3, When no error occurs during rendering of the print data by the rendering means, the notification means transmits identification information of the print data generated by rendering to the terminal to which the notification means notifies the error. A print processing system comprising: (Item 5) 5. A printing processing system according to any one of items 1 to 4, The notification means notifies the error to a destination according to the timing at which the error occurred. A print processing system comprising: (Item 6) Item 5. The print processing system according to item 5, The notification means notifies the terminal that is the sender of the print data of an error that occurs when opening the print data for rendering, and notifies a designated terminal of an error that occurs during rendering of the print data. A print processing system comprising: (Item 7) 7. A print processing system according to any one of items 1 to 6, The printing device further includes a transmitting unit that transmits the identification information of the print data generated by the rendering unit and stored in the storing unit to the terminal that is the sender of the print data. A print processing system comprising: (Item 8) Item 7. A print processing system according to item 7, The transmitting means transmits the identification information when the rendering means has successfully rendered the print data. A print processing system comprising: (Item 9) Item 7. A print processing system according to item 7, The transmitting means transmits the identification information in response to receiving the print data from the terminal. A print processing system comprising: (Item 10) 10. A program for causing a computer to function as the print processing system according to any one of items 1 to 9. (Item 11) A print processing system according to any one of items 1 to 9; a terminal that transmits print data to the print processing system; an image forming device that acquires and prints the print data generated by the rendering means and stored in the print processing system. A printing system characterized by: (Item 12) An error notification method for a print processing system having a rendering unit, a saving unit, and a notification unit, comprising: the rendering means renders print data received from a terminal; the storage means stores the print data generated by rendering, When an error occurs during rendering, the notification means notifies the terminal of the error. An error notification method comprising:

[0063] The present invention is not limited to the above-described embodiments, and various changes and modifications can be made without departing from the spirit and scope of the invention. Therefore, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]

[0064] 110 Planning and terminal, 120 MFP, 130 Network, 140 Print management server, 150 Data conversion server

Claims

1. a rendering means for rendering print data received from the terminal; a storage means for storing the print data generated by rendering; and a notification means for notifying the terminal of an error when an error occurs during rendering. A print processing system comprising:

2. 2. The print processing system according to claim 1, The notification means notifies the error using a message function. A print processing system comprising:

3. 3. The print processing system according to claim 2, The terminal that sent the print data and the terminal that notifies the error are different terminals. A print processing system comprising:

4. 4. The print processing system according to claim 3, When no error occurs during rendering of the print data by the rendering means, the notification means transmits identification information of the print data generated by rendering to the terminal to which the notification means notifies the error. A print processing system comprising:

5. 2. The print processing system according to claim 1, The notification means notifies the error to a destination according to the timing at which the error occurred. A print processing system comprising:

6. 6. The print processing system according to claim 5, The notification means notifies the terminal that is the sender of the print data of an error that occurs when opening the print data for rendering, and notifies a designated terminal of an error that occurs during rendering of the print data. A print processing system comprising:

7. 2. The print processing system according to claim 1, The printing device further includes a transmitting unit that transmits the identification information of the print data generated by the rendering unit and stored in the storing unit to the terminal that is the sender of the print data. A print processing system comprising:

8. 8. The print processing system according to claim 7, The transmitting means transmits the identification information when the rendering means has successfully rendered the print data. A print processing system comprising:

9. 8. The print processing system according to claim 7, The transmitting means transmits the identification information in response to receiving the print data from the terminal. A print processing system comprising:

10. A program for causing a computer to function as the print processing system according to any one of claims 1 to 9.

11. A print processing system according to any one of claims 1 to 9; a terminal that transmits print data to the print processing system; an image forming device that acquires and prints the print data generated by the rendering means and stored in the print processing system. A printing system characterized by:

12. An error notification method for a print processing system having a rendering unit, a saving unit, and a notification unit, comprising: the rendering means renders print data received from a terminal; the storage means stores the print data generated by rendering, When an error occurs during rendering, the notification means notifies the terminal of the error. An error notification method comprising:

Images