Print management system, server, and print management method

Abstract

To provide a print management system, a server, and a print management method capable of managing the status until content is printed.SOLUTION: In a print management system in which a distribution server 100, an image conversion server 500, a printing device 200, a store terminal 300, and a newspaper company terminal 400 can communicate with one another via a network, the distribution server has a storage unit that stores manuscript data, and converts the manuscript data into print data for each page, and transmits a print instruction for the converted print data to the printing device (S94), the printing device receives the print instruction and prints the print data based on the received print instruction (S100), and the newspaper company terminal displays a print status display screen on a display unit, and transmits an instruction to retransmit the print instruction to the distribution server (S90) when a "resume" button operation (S91) instructing reprinting of the print data is accepted.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a print management system, a server, and a print management method for managing printing related to content. [Background technology]

[0002] Conventionally, a system for managing the printing of content distributed over a network has been known, as described in Patent Document 1, for example. This system is composed of a content creation server, a content distribution server, a log management server, and a multifunction peripheral. The content creation server creates new content data and registers it in the content distribution server. The content distribution server adds metadata, including the printing conditions of the content, to the content data and pushes the content data to a printer. Upon receiving the content data, the printer prints the content data based on the metadata added to the content data. The printer also counts the number of copies of the content data printed, and when all printing is complete, sends the log data to the log management server. The log management server receives the log data from the printer. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5468829 Summary of the Invention [Problem to be solved by the invention]

[0004] It is desirable for content providers to manage the status up to the point where the content is successfully printed. However, the system described in Patent Document 1 does not particularly take such management into consideration.

[0005] An object of the present disclosure is to provide a technology that can manage the status up to when content is printed. [Means for solving the problem]

[0006] In order to achieve the above object, the present disclosure relates to the following technology: A print management system in which a server, a printer, and an information processing device are configured to be able to communicate with each other over a network, wherein the server has a memory for storing content and executes a conversion process for converting the content into print data for each partial data portion and a first transmission process for transmitting a print instruction for the print data to the printer on the condition that the partial data included in the content has been converted into the print data in the conversion process, the printer executes a reception process for receiving the print instruction transmitted in the first transmission process and a print process for printing the print data based on the print instruction received in the reception process, and the information processing device executes a first display process for displaying a first management screen indicating the status of the print processing on a display and a second transmission process for transmitting an instruction to retransmit the print instruction to the server in response to receiving a first operation instructing reprinting of the print data.

[0007] The print management system of the present disclosure includes a server, a printer, and an information processing device. The server's memory stores content. The server executes a conversion process to convert the content into print data for each partial data. After converting all partial data into print data, the server sends a print instruction for the converted print data to the printer in a first transmission process. The printer receives the print instruction sent in the first transmission process in a reception process, and prints the print data based on the print instruction in a print process. The information processing device displays a first management screen on a display, which indicates the status of the printing process in the printer, through a first display process. When an operator performs a first operation to instruct reprinting of the print data in response to the display of the first management screen, the information processing device transmits a retransmission instruction for the print instruction to the server through a second transmission process.

[0008] As described above, according to the present disclosure, the operator can use the first management screen displayed on the display of the information processing device to manage the status up to the printing of the content. In particular, the operator can perform a first operation on the information processing device as needed to send an instruction to resend the print instruction to the server. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to manage the status up to when content is printed. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram illustrating an example of the overall configuration of a print management system according to an embodiment. [Figure 2] 10 is a sequence flow illustrating an example of a flow of processes executed by a distribution server, an image conversion server, a newspaper company terminal, a dealer terminal, and a printer. [Figure 3] 10 is a sequence flow illustrating an example of a flow of processes executed by a distribution server, an image conversion server, a newspaper company terminal, a dealer terminal, and a printer. [Figure 4] 10 is an explanatory diagram illustrating an example of a conversion status display screen displayed on a display unit of a newspaper company terminal. FIG. [Figure 5] 10A and 10B are explanatory diagrams showing a distribution time setting screen for setting the distribution time for each printing device at the dealer terminal, and a distribution time change screen for changing the distribution time; [Figure 6] FIG. 10 is an explanatory diagram illustrating an example of a printed matter that includes a mixture of original legitimate content that has been successfully image-converted and print pages with predetermined content that have been replaced due to a failure in image conversion. [Figure 7] FIG. 10 is an explanatory diagram illustrating another example of a printed matter that includes a mixture of original legitimate content that has been successfully image converted and print pages with predetermined content that have been replaced due to a failure in image conversion. [Figure 8] 10 is an explanatory diagram illustrating an example of a printing status display screen displayed on a display unit of a newspaper company terminal. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0011] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure relates to a print management system that distributes content from a server to a printer and performs printing.

[0012] <Overall configuration of the printing management system> FIG. 1 shows an example of the overall configuration of a print management system 1 according to an embodiment. This embodiment is an example of a print management system that mainly distributes newspaper articles as the content. As shown in FIG. 1, the print management system 1 includes a distribution server 100, multiple printing devices 200, a retailer terminal 300, a newspaper company terminal 400, and an image conversion server 500. Note that FIG. 1 shows only one printing device 200 out of the multiple printing devices 200. The servers 100 and 500, the printing device 200, the newspaper company terminal 400, and the retailer terminal 300 each include a communication unit and can communicate with each other via a network NT. The distribution server 100 and the image conversion server 500 are examples of servers, and the newspaper company terminal 400 and the retailer terminal 300 are examples of information processing devices. The newspaper company terminal 400 is also an example of an external device.

[0013] The network NT includes at least one of the Internet, a LAN (Local Area Network), and a WAN (Wide Area Network). The communication unit may include multiple types of communication circuits for connecting to the network NT. In this case, devices connected to the network NT may communicate with multiple other devices using different communication circuits. In this embodiment, the multiple types of communication circuits are collectively referred to as the communication unit.

[0014] <Newspaper company terminal> The newspaper company terminal 400 is, for example, a terminal such as a PC owned by a newspaper company, and is connected to the network NT. The newspaper company terminal 400 is, for example, a tablet PC, a notebook PC, a desktop PC, or the like. The newspaper company terminal 400 has a display unit 401, an operation unit 410, and a control unit, a memory unit, a communication unit, etc. (not shown). The memory unit is configured with, for example, RAM, ROM, EEPROM, HDD, etc., and stores various programs. The control unit is configured with a CPU, and executes the various programs stored in the memory unit. The various programs include programs that execute the processes shown in the flowcharts of Figures 2 and 3, which will be described later.

[0015] The display unit 401 is configured by, for example, a display, and displays various information including a printing status display screen 401B shown in Fig. 8 and a conversion status display screen 401A shown in Fig. 4, which will be described later. The operation unit 410 is configured with, for example, a keyboard, a mouse, or a touch panel, and accepts various input operations by the operator. The operator can input various instructions to the newspaper company terminal 400 by appropriately operating the operation unit 410. In particular, in this example, the operator can upload manuscript data of newspaper articles to the distribution server 100 via operations on the operation unit 410 of the newspaper company terminal 400 (details will be described later).

[0016] <Dealer terminal> The dealer terminal 300 is a terminal such as a PC owned by a dealer of a newspaper published by a newspaper company, and is connected to the network NT. The dealer terminal 300 may be any appropriate terminal other than the printing device 200, such as a tablet PC, a notebook PC, a desktop PC, or a smartphone. The dealer terminal 300 has a display unit 301, an operation unit 310, and a control unit, a storage unit, a communication unit, etc. (not shown). The storage unit is configured with, for example, RAM, ROM, EEPROM, HDD, etc., and stores various programs. The control unit is configured with a CPU and executes the various programs stored in the storage unit. The various programs include programs that execute the processes shown in the flowcharts of Figures 2 and 3 (described below).

[0017] The display unit 301 is configured, for example, by a display. The display unit 301 displays various information, including a distribution time setting screen 301A and a distribution time change screen 301B shown in Figs. 5(a) and 5(b), which will be described later. The operation unit 310 is configured, for example, by a keyboard, a mouse, or a touch panel, and accepts various input operations by an operator. The operator can input various instructions to the dealer terminal 300 by appropriately operating the operation unit 310.

[0018] <Distribution server> The distribution server 100 is a server installed and managed by, for example, an operating company that operates the print management system 1 of this embodiment. The distribution server 100 sequentially stores manuscript data of multiple newspaper articles uploaded by the newspaper company terminal 400 as described above, and then outputs the manuscript data to the image conversion server 500 at a predetermined timing.

[0019] In detail, the distribution server 100 has a control unit 110, a storage unit 115, a communication unit 140, etc. The storage unit 115 is an example of a memory. The control unit 110, the storage unit 115, the communication unit 140, etc. are connected via a bus 105 so as to be able to send and receive information. The storage unit 115 is configured with, for example, RAM, ROM, EEPROM, HDD, etc. The storage unit 115 stores various programs 120 and various data 130. The various programs 120 include an information distribution program that executes the control contents of the distribution server 100 shown in the flows of Figs. 2 and 3 described below, and the various data 130 includes manuscript data of the newspaper articles. The storage unit 115 stores the various data 130 in the form of a database. The manuscript data of the newspaper articles is an example of content.

[0020] The control unit 110 is a device that performs data processing, and is, for example, a processor such as a CPU. The control unit 110 executes various programs stored in the storage unit 115. The control unit 110 performs various processes, including data communication with the printing device 200, the store terminal 300, the newspaper company terminal 400, and the image conversion server 500, which are connected to the network NT. The communication unit 140 includes hardware that connects to the network NT, such as a NIC (Network Interface Card) for connecting to Ethernet, and communicates with the printing device 200, the store terminal 300, the newspaper company terminal 400, and the image conversion server 500.

[0021] <Image conversion server> The image conversion server 500 receives the manuscript data transmitted by the distribution server 100 at a predetermined timing, converts the data into data in a predetermined format for printing by the printing device 200 (hereinafter simply referred to as "print data"), and then transmits the data to the printing device 200. The image conversion server 500 has a control unit, a storage unit, a communication unit, etc., which are not shown. The control unit, storage unit, and communication unit of the image conversion server 500 each have the same configuration as those of the distribution server 100.

[0022] The distribution server 100 and the image conversion server 500 may each be configured as a single "server," or may each be configured as multiple servers. Alternatively, at least two of the functions of the servers 100 and 500 may be provided in a single "server."

[0023] <Printer> The printing device 200 includes a control unit 210, a memory unit 215, a display unit 240, an operation unit 250, a communication unit 260, and a printing unit 270. The control unit 210, the memory unit 215, the display unit 240, the operation unit 250, the communication unit 260, and the printing unit 270 are connected via a bus 205 so as to be able to send and receive information.

[0024] The storage unit 215 is configured with, for example, RAM, ROM, EEPROM, HDD, etc. The storage unit 215 stores various programs 220 and various data 230. The various programs 220 include, for example, programs that execute the control content of the printing device 200 according to the flows shown in Figures 2 and 3 described below. The various data 230 includes print data received from the image conversion server 500, i.e., manuscript data of newspaper articles converted into a printable format.

[0025] The control unit 210 is a device that processes data and is, for example, a processor such as a CPU. The control unit 210 executes various programs stored in the memory unit 215. The display unit 240 is, for example, a liquid crystal display and is capable of displaying various information. The operation unit 250 is, for example, a keyboard, buttons, etc., and accepts input operations by an operator. The operator can input various instructions to the printing device 200 by operating the operation unit 250. The communication unit 260 is connected to the network NT and is capable of communication with the distribution server 100, the image conversion server 500, the newspaper company terminal 400, and the retailer terminal 300. The printing unit 270 includes a print engine and forms and prints an image on the printing paper, for example, by an inkjet method, while removing and transporting printing paper from a paper tray using a transport mechanism (not shown).

[0026] The cartridge holder 280 is configured to be able to accommodate one cartridge 285. The cartridge holder 280 may be able to accommodate cartridges 285 of multiple ink colors, such as cyan, magenta, yellow, and black. Furthermore, the printer 200 may be provided with multiple cartridge holders 280. The printing unit 270 is composed of, for example, an inkjet head, a carriage, and a motor and belt that drive the carriage. The printing unit 270 performs printing processing while consuming ink by ejecting ink from a cartridge 285 from the inkjet head onto printing paper. Ink is an example of a consumable item, and printing paper may also be an example of a consumable item. Note that the printing unit 270 is not limited to an inkjet type, and may also be a laser type. In this case, the toner cartridge or drum would be a consumable item.

[0027] <Main parts of the embodiment> The present embodiment is characterized by a series of steps from uploading manuscript data of the newspaper article to printing by the printing device 200, and a method for managing the status up to printing by the newspaper company terminal 400, etc. Details of this procedure are explained below using the sequence flows in Figures 2 and 3. The sequence flow in Figure 2 represents the control executed by the distribution server 100, image conversion server 500, newspaper company terminal 400, retailer terminal 300, and printing device 200 when uploading manuscript data of the newspaper article. The sequence flow in Figure 2 is repeatedly executed while the power to the distribution server 100, image conversion server 500, newspaper company terminal 400, retailer terminal 300, and printing device 200 is on.

[0028] <Processing flow (part 1)> In S4 of FIG. 2, the newspaper company terminal 400 uploads manuscript data of a newspaper article to be printed by the printing device 200 to the distribution server 100 based on the operation of the operator. This manuscript data includes, for example, a distribution list name, a distribution date to the printing device 200, a page number indicating which page of the newspaper article the manuscript is, a file name, and file contents. As will be described later, in this embodiment, as an example, 30 pages of manuscript data are distributed at one time as a single newspaper article. One page of manuscript data constitutes one file. Therefore, a newspaper article distributed at one time is made up of 30 files of manuscript data. The newspaper company terminal 400 uploads the manuscript data in units of a predetermined portion of the 30 pages of manuscript data that make up a newspaper article, in units of one page (one file) in this example. One page of manuscript data contained in one file is an example of partial data. In S6, distribution server 100 stores the uploaded manuscript data in the database of storage unit 115, and returns a response to newspaper company terminal 400 indicating that the manuscript data has been accepted. The database of storage unit 115 stores information about newspaper articles to be distributed to printing device 200 in one distribution in one record. One record includes a distribution list name and the file names of multiple manuscript data items included in the distribution list identified by the distribution list name.

[0029] In S8, distribution server 100 determines whether the manuscript data received in S4 has already been received in the past. Specifically, as will be described later in S10, if the received manuscript data has been received in the past, the file name of the received manuscript data is stored as a record in the database of storage unit 115, and therefore distribution server 100 determines whether the same file name as the file name of the manuscript data received in S4 has already been stored as a record in the database.

[0030] If the same file name is not found in the database, the manuscript data is new and has not been received before. Therefore, the distribution server 100 determines No in S8 and stores the manuscript data received in S4 in the storage unit 115 in S10. Then, the file name of the manuscript data is added to a record that includes the same distribution list name as the distribution list name included in the manuscript data, and the process proceeds to S14, which will be described later. If the distribution list name included in the manuscript data is not found in the database, the distribution server 100 adds a new record and stores the distribution list name and file name of the manuscript data in association with each other in the database. Then, the distribution server 100 sets the conversion status for each file of the manuscript data in the record to "waiting for conversion start," and records the file name, distribution date and time, upload time, page number, etc. in association with the conversion status (see FIG. 4, which will be described later). If the same file name is found in the database, distribution server 100 determines Yes in S8, and then compares the content of the manuscript data previously received and stored in the database with the content of the manuscript data of the same record newly received in S4 to determine whether there is a difference. The process executed by distribution server 100 in S12 is an example of a determination process. If there is no difference, the content of the manuscript data of the record has not been particularly updated, so distribution server 100 determines No in S12 and ends the processing in Fig. 2. If there is a difference, the content of the manuscript data of the record has been updated, so distribution server 100 proceeds to processing S10. After S10, distribution server 100 proceeds to processing S14.

[0031] In S14, distribution server 100 transmits a display instruction to newspaper company terminal 400 to start displaying conversion status display screen 401A shown in Fig. 4, which will be described later. In S16, newspaper company terminal 400 receives the display instruction and starts displaying conversion status display screen 401A shown in Fig. 4 (details will be described later) on display unit 401. The process executed by newspaper company terminal 400 in S16 is an example of second display process.

[0032] In S18, distribution server 100 transmits to image conversion server 500 an instruction to convert the manuscript data received in S4 into the print data for printing by printing device 200, along with the file contents of the manuscript data. Image conversion server 500 creates a file ID for the manuscript data received in S18, and returns the file ID to distribution server 100 in S20. Distribution server 100 stores the file ID received in S20 in memory unit 115 in association with the file name of the manuscript data transmitted in S18.

[0033] In S30, the image conversion server 500 converts the manuscript data received in S18 into the print data described above using a known method. The converted print data is assigned the file ID created in S18 and stored in the image conversion server 500. In this embodiment, as shown in FIG. 8 described below, one newspaper article consists of 30 pages of manuscript data. In S4 described above, the newspaper company terminal 400 is configured to upload all 30 pages of manuscript data in predetermined portions, for example, one page of manuscript data at a time. In response to this, in S30, the image conversion server 500 converts all 30 pages of manuscript data into print data in predetermined portions, for example, one page of manuscript data at a time. S30 is an example of a conversion step, and the processing performed by the image conversion server 500 in S30 is an example of a conversion process.

[0034] When the image conversion server 500 starts conversion into print data in S30, the distribution server 100 inquires of the image conversion server 500 about the conversion status of the manuscript data indicated by the file ID described above in S32, which is performed, for example, periodically. In response to the inquiry received in S32, the image conversion server 500 notifies the distribution server 100 in S34 of the conversion status of the manuscript data of the file ID in question, i.e., whether the conversion is still in progress, whether the conversion has been completed successfully, or whether the conversion has been completed unsuccessfully. While the distribution server 100 is performing the image conversion process to print data in S30, it updates the information in the database based on the conversion status notified from the image conversion server 500. As a result, the conversion status displayed on the conversion status display screen 401A displayed on the newspaper company terminal 400 is updated.

[0035] <Conversion status display screen> 4 shows an example of a conversion status display screen 401A displayed on the display unit 401 of the newspaper company terminal 400. The conversion status display screen 401A is an example of a second management screen. The conversion status display screen 401A displays information based on information in a database stored in the distribution server 100. The example of conversion status display screen 401A shown in FIG. 4 displays 30 pages of manuscript data included in one distribution list, "Newspaper 0402_01-0402_30," arranged in the order of upload from top to bottom. Conversion status display screen 401A also displays the following items for each page: "Distribution Date and Time," "Upload Time," "Page Number," "File Name," "Conversion Status," and "Cause of Error." The "Distribution Date and Time" field stores the earliest of the times set in FIG. 5 (described below) for distributing the distribution list "Newspaper 0402_01-0402_30" to multiple printing devices 200. The "Upload Time" field indicates the time when the manuscript data upload was completed. The "Page Number" field indicates the page order of the manuscript data. The "File Name" field indicates the file name of the manuscript data. The "Conversion Status" field indicates the upload status of the manuscript pages and the status of converting the manuscript data into print pages, and indicates one of the following information: "Complete," "Converting," "Conversion Error," "Waiting for Upload," "Uploading," "Upload Error," etc. "Cause of Error" indicates the cause of an abnormality such as a "conversion error" or "upload error" that occurred during the conversion status. In addition, the upload deadline may also be displayed as an item. The conversion status item on this conversion status display screen 401A shows the upload status of manuscript data from newspaper company terminal 400 to distribution server 100 and the image conversion status of manuscript data by image conversion server 500.

[0036] In this embodiment, the newspaper company terminal 400 uploads pages to the distribution server 100 in the order of page numbers: page 1 → page 2 → page 5 → page 4 → page 3 → page 6 → page 7 → page 10, which is unrelated to the page number order, that is, for example, in the order in which the manuscripts were completed. The distribution server 100 sends conversion instructions to the image conversion server 500 in the upload order. Therefore, the image conversion server 500 starts image conversion in the upload order. 4, the manuscript data with page numbers 1 and 2 have been successfully converted into the print data described above, and conversion status display screen 401A displays "Completed" in the "Conversion Status" field. The manuscript data with page number 5 is currently being converted into the print data described above, and conversion status display screen 401A displays "Converting" in the "Conversion Status" field.

[0037] Conversion to print data for the manuscript data with page number 4 ended in failure, and conversion status display screen 401A displays "Conversion Error" in the "Conversion Status" column. Conversion failures can occur, for example, because the original manuscript data uploaded by newspaper company terminal 400 before conversion was too large in data size, was not in a predetermined file format such as PDF, or the file contained some kind of defect. The illustrated example shows a case where the file format is not the predetermined file format, and conversion status display screen 401A displays "File Format Abnormal" in the "Cause of Error" column.

[0038] As mentioned above, the manuscript data for pages 3, 6, and 7 is currently being converted into print data, and the conversion status display screen 401A displays "Converting" in the "Conversion status" column. For the manuscript data with page number 10, after the newspaper company terminal 400 uploaded the manuscript data, the image conversion server 500 has not yet started converting it into print data, and the conversion status display screen 401A displays "Waiting for conversion to start" in the "Conversion status" column.

[0039] In this embodiment, distribution server 100 recognizes in advance that newspaper company terminal 400 will upload 30 pages of manuscript data. As a result, conversion status display screen 401A displays "Waiting for upload" in the "Conversion status" column for manuscript data for pages other than page 1, page 2, ..., and page 10, i.e., page 9, page 8, ..., indicating that newspaper company terminal 400 has not yet uploaded the data. Conversion status display screen 401A displays "Converting" or the like in the "Conversion status" column for each page of manuscript data that is "Waiting for upload" as the newspaper company terminal 400 has uploaded the manuscript data to distribution server 100 and image conversion server 500 has started conversion in response to a conversion instruction from distribution server 100.

[0040] For example, if even one page of manuscript data is still "waiting to be uploaded" after a predetermined timing, i.e., the aforementioned upload deadline, has passed, distribution server 100 may notify newspaper company terminal 400 of this fact by email or the like. This process performed by distribution server 100 is an example of notification processing. In such a case, in response to a print instruction from distribution server 100, printing device 200 may print a printed matter including a guide message separate from the newspaper article, which is the original legitimate content, as in the printed matter shown in Figures 6 and 7 described below. The process in which distribution server 100 sends a print instruction to printing device 200 in this case is an example of a third transmission process. In this case, the printing device 200 prints the newspaper article, which is the regular content, for the pages that have been converted into print data out of the 30 pages of manuscript data mentioned above, and prints the above-mentioned information message for the pages that have not yet been uploaded. The information message might say, for example, "Of the total x pages scheduled for distribution, XX pages have not yet been uploaded and have not been distributed. For details, please contact XXX-XXX."

[0041] <Processing flow (part 2)> 2, in S36, the distribution server 100 determines whether or not there is any unconverted manuscript data among the uploaded manuscript data for which a conversion instruction to print data has not yet been sent. If there is any unconverted manuscript data, the distribution server 100 determines Yes in S36, returns the process to S18 described above, and repeats the same process as described above. If there is no unconverted manuscript data and the process has ended with the conversion completed normally or has ended with the conversion failing, the distribution server 100 determines No in S36 and proceeds to S38.

[0042] In S38, based on the results of reception in S34, distribution server 100 determines whether all manuscript data included in one newspaper article has been successfully converted into print data, i.e., whether all conversions into print data have been completed normally. If all conversions into print data have been completed normally, distribution server 100 determines Yes in S38, sends a conversion completion notification to newspaper company terminal 400 in S40, and proceeds to S50. If even one conversion to print data has failed, distribution server 100 determines No in S38 and proceeds to S42. In S42, distribution server 100 replaces the manuscript data of the page that failed to be converted with data for a predetermined replacement page (see FIG. 6 for details) containing content apologizing for the conversion failure, and transmits this to image conversion server 500. Image conversion server 500 converts the replacement page data received in S42 into the corresponding print data in the same manner as described above. Image conversion server 500 assigns a file ID to the converted replacement page, and transmits this file ID to distribution server 100 in S44.

[0043] The distribution server 100, which received the file ID in S44, stores the received file ID in a database in association with the manuscript data whose conversion failed, and in S46 transmits a conversion error notification to the newspaper company terminal 400, indicating that conversion of the manuscript data into print data has failed and that the specified replacement pages have been replaced. The newspaper company terminal 400 receives the transmitted conversion error notification in S48 and displays a corresponding conversion error on the conversion status display screen 401A. The display of "Conversion Error" for the aforementioned four pages of manuscript data on the conversion status display screen 401A in FIG. 4 corresponds to the conversion error display in S48. This processing executed by the newspaper company terminal 400 is an example of a notification processing. After S46, the distribution server 100 advances the processing to S50.

[0044] In S50, distribution server 100 records the conversion status of the manuscript data, i.e., whether conversion is in progress, conversion is complete, conversion failed, etc., in the database of storage unit 115. Thereafter, distribution server 100 ends the processing of Fig. 2. By executing the sequence flow of Fig. 2, the manuscript data uploaded from newspaper company terminal 400 is converted into print data by image conversion server 500.

[0045] The sequence flow in Fig. 3 represents the control executed by the distribution server 100, image conversion server 500, newspaper company terminal 400, retail store terminal 300, and printer 200 from the time the uploaded manuscript data is distributed until printing is completed. As with Fig. 2 above, the sequence flow in Fig. 3 is repeatedly executed in parallel with each other while the power of the distribution server 100, image conversion server 500, newspaper company terminal 400, retail store terminal 300, and printer 200 is on. 3, the distribution server 100 transmits a display instruction to the newspaper company terminal 400 to start displaying a printing status display screen 401B shown in FIG. 8, which will be described later. The newspaper company terminal 400 receives the display instruction from the distribution server 100 in S70, and starts displaying the printing status display screen 401B (details of which will be described later) shown in FIG. 8, which will be described later, on the display unit 401. S70, which is executed by the newspaper company terminal 400, is an example of a display step, and the processing executed by the newspaper company terminal 400 in S70 is an example of a first display processing. In this example, the display unit 301 of the dealer terminal 300 is also configured to display a screen similar to the printing status display screen 401B. Hereinafter, the printing status display screen 401B of the newspaper company terminal 400 and the similar screen of the dealer terminal 300 will be collectively referred to as simply "printing status display screen 401B, etc."

[0046] In S60, the distribution server 100 also transmits a display instruction to the dealer terminal 300 to start displaying the screen. The dealer terminal 300 receives the display instruction from the distribution server 100 in S80, and starts displaying the same as a printing status display screen 401B in FIG. 8 (described later) on the display unit 301 (detailed description is omitted). S80 executed by the dealer terminal 300 is also an example of a display step, and the processing executed by the dealer terminal 300 in S80 is also an example of a first display processing.

[0047] In S82, the distribution server 100 determines whether the print error flag F is 1 (see S114 described later). If F=0, the distribution server 100 determines No in S82 and proceeds to S84. In S84, the distribution server 100 determines whether the startup time, which is predetermined, for example, at a predetermined interval, has arrived in order to start the processing from S86 onward, which will be described later. The predetermined interval is, for example, one hour. If the startup time has not arrived, the distribution server 100 determines No in S84, returns to S82, and repeats the same processing. If the startup time has arrived, the distribution server 100 determines Yes in S84, and proceeds to S86.

[0048] In S86, the distribution server 100 identifies the printing device 200 that will start distribution based on the distribution start times for each printing device 200 that have been preset by the dealer terminal 300. A distribution time setting screen 301A for setting the distribution time for each printing device 200 on the dealer terminal 300 is shown in FIG.

[0049] <Distribution time setting screen and distribution time change screen> In the example of the distribution time setting screen 301A shown in FIG. 5(a), six printing devices 200 are set as distribution targets, and the display shows the fields "Printer ID," "Distribution Start Time," and "Change Required" for each printing device 200. The distribution start time is a time that is appropriately set and input by operating the operation unit 310 of the dealer terminal 300. As shown in the figure, in this example, the distribution time setting screen 301A sets the distribution start time for six printing devices 200, ID01 to ID06, to 4:00 or 5:00 on April 2nd. For the distribution start time of each printing device 200, the distribution time setting screen 301A displays a "Change" button in the "Change Required" field. When the operator operates the "Change" button via the operation unit 310, the display unit 301 displays the distribution time change screen 301B shown in FIG. 5(b).

[0050] 5(b) shows an example of changing the distribution time of the printing device 200 with ID01. In the example shown, distribution time change screen 301B shows a state in which April 3rd has been selected from the list box as the changed distribution start date, and 0:00 has been selected from the list box as the changed distribution start time. The operator can confirm the changes by operating the "Save" button via operation unit 310, or cancel the changes by operating the "Cancel" button.

[0051] Instead of setting or changing the distribution start time as described above, the estimated distribution completion time may be set or changed on an appropriate screen of the dealer terminal 300. In this case, the distribution server 100 calculates the required distribution time from the total number of pages scheduled for distribution on the day, and automatically sets the distribution start time so that it does not exceed the estimated distribution completion time set on the screen. For example, if it is estimated that it takes 30 seconds to distribute one page of manuscript data and print it on the printer 200, and there are 30 pages of manuscript data in total, distribution will start 900 seconds before the estimated distribution completion time. Furthermore, the newspaper company terminal 400 may display screens similar to the distribution time setting screen 301A and distribution time change screen 301B, allowing the operator to perform the same operations as those described above. The distribution server 100 stores the times set on the distribution time setting screen 301A and the distribution time change screen 301B in the storage unit 115 in association with the printer ID of the printing device 200.

[0052] <Processing flow (part 3)> 3, in S88, the distribution server 100 reads and acquires the name of the distribution list to be distributed to the printing device 200 identified in S86 from the database in the storage unit 115. After S88, the distribution server 100 proceeds to S94, which will be described later.

[0053] On the other hand, if F=1 in S82, the distribution server 100 judges S82 as Yes and proceeds to S92. In S92, the distribution server 100 judges whether or not a "Resume" button (details to be described later) has been operated on the printing status display screen 401B (details to be described later) of the newspaper company terminal 400 or the printing status display screen of the dealer terminal 300, which instructs retransmission of the manuscript data. If the "Resume" button has not been operated, the distribution server 100 judges S92 as No, returns the process to S82, and repeats the same procedure. If the "Resume" button has been operated on the newspaper company terminal 400 or the dealer terminal 300, the newspaper company terminal 400 or the dealer terminal 300 transmits an operation signal corresponding to the operation to the distribution server 100 in S90 or S91, and the distribution server 100 judges S92 as Yes and proceeds to S94 (details to be described later). Note that operating the "Resume" button is an example of a first operation and also an example of a predetermined operation. Furthermore, S90 executed by the newspaper company terminal 400 and S91 executed by the dealer terminal 300 are examples of a second transmission step, and the processing executed by the newspaper company terminal 400 in S90 and the processing executed by the dealer terminal 300 in S91 are examples of a second transmission processing. In S94, distribution server 100 reads from storage unit 115 the file ID associated with the manuscript data included in the distribution list name acquired in S88, and transmits a print instruction to printing device 200 to instruct printing of one page of the manuscript data to be distributed. The print instruction includes one file ID. S94 is an example of a first transmission step, and the processing executed by distribution server 100 in S94 is an example of first transmission processing and also an example of instruction transmission processing.

[0054] Note that when the "Resume" button is pressed, the distribution server 100 proceeds from S92 to S94, and resumes printing that was once completed, as described below. Therefore, pressing the "Resume" button serves as an instruction to reprint using the print data. The operation signal sent from the newspaper company terminal 400 or the retailer terminal 300 to the distribution server 100 thereby serves as an instruction to resend the print command.

[0055] Furthermore, for pages of the uploaded manuscript data for which the image conversion process by the image conversion server 500 failed in S30, the distribution server 100 replaces them in S42, so that the printing device 200 prints content different from the original content based on the print instruction in S94. As a result, the printed matter finally printed by the printing device 200 will be a printed matter that contains a mixture of, for example, printed pages of the original legitimate content for which image conversion was successful, in this example, the content of a newspaper article, and printed pages of specified content that were replaced because image conversion failed.

[0056] Figure 6 shows an example of such a mixed printout. In this example, the printing device 200 prints legitimate content on pages 1, 2, 3, 5, and so on out of the 30 pages mentioned above, but prints a predetermined apology message on page 4 due to a failed image conversion. In this example, as shown in the figure, the apology message reads, "Due to a system problem, this page could not be delivered. Please contact XXX-XXX." As shown in Figure 7, the page on which the image conversion failed may not be printed, and a new page containing the above apology message and the page number on which the conversion failed may be printed in a predetermined order, such as on the first page, page 0, in the illustrated example.

[0057] 3, in S96, the printing device 200 receives the print instruction sent in S94 by the distribution server 100. The process executed by the printing device 200 in S96 is an example of a receiving process. In response to the file ID included in the print instruction received in S96, the printing device 200 sends a request for converted print data of the page corresponding to the print instruction to the image conversion server 500 in S98. The request for print data includes the file ID.

[0058] The image conversion server 500 transmits to the printing device 200 one page of print data corresponding to the file ID included in the print data request received from the printing device 200 in S98. The printing device 200 performs printing processing in S100 using the print data received from the image conversion server 500 in S99, and forms one page of image on printing paper by the printing unit 270. S100 is an example of a printing step, and the processing performed by the printing device 200 in S100 is an example of printing processing.

[0059] In S104, which is performed at an appropriate interval, for example, the distribution server 100 inquires of the printing device 200 about the print result based on the print instruction in S94. In response to the inquiry received in S104, the printing device 200 notifies the distribution server 100 in S106 of the status of printing on the printing paper, i.e., whether printing is still in progress, whether the process has ended with normal printing completion, whether there has been some abnormality or malfunction that has caused the process to end with an error, or whether there has been some abnormality or malfunction that has caused the device to temporarily stop. The distribution server 100 stores in the memory unit 115 a database that manages the printing status of newspaper articles for each printing device 200 in order to display the printing status display screen 401B shown in Figure 8 described below, and in S106, updates the printing status in accordance with the content notified from the printing device 200.

[0060] <Printing status display screen> 8 shows an example of a printing status display screen 401B displayed on the display unit 401 of the newspaper company terminal 400. The printing status display screen 401B is an example of a first management screen. The example of the print status display screen 401B shown in FIG. 8 shows the status up to the point where printing of all pages of the target print data, that is, a 30-page file, is completed between the above-mentioned S94 and the below-described S124 in FIG.

[0061] The upper section of the print status display screen 401B displays the following items for the data to be distributed in one distribution: "Category," "Scheduled distribution start time," "Start time," "End time," "Distribution status," "Distribution list name," "Number of items scheduled for distribution," "Number of items distributed successfully," "Number of items in operation," "Number of items not in operation," and "Remarks." "Category" indicates the type of content to be distributed. "Scheduled distribution start time" indicates the earliest of the distribution start times set in Figure 5. "Start time" indicates the earliest time when distribution of newspaper articles began to the multiple printing devices 200 shown on the screen. "End time" indicates the time when all distribution to the multiple printing devices 200 shown on the screen was completed. "Distribution status" indicates an abnormality if there is an abnormality in the distribution status of even one of the multiple printing devices 200 shown on the screen, and indicates normality if the distribution status of all is normal. "Distribution list name" indicates the name of the distribution list. In this example, there is only one distribution list, but if the configuration allows multiple distribution lists to be distributed to the printing device 200 at once, the printing status display screen 401B may accordingly include two items, for example, "Distribution List Name 1" and "Distribution List Name 2." "Number of planned distributions" indicates the number of printing devices 200 to which newspaper articles will be distributed. "Number of completed distributions" indicates the number of printing devices 200 to which newspaper article distribution has been completed. "Number in operation" indicates the number of printing devices 200 that have started distributing newspaper articles and are currently printing. "Number of inoperational items" indicates the number of printing devices 200 for which newspaper article distribution or printing has stopped midway. "Notes" indicates supplementary information accompanying each item on the printing status display screen 401B.

[0062] 8, the top row of the printing status display screen 401B shows that the print instruction for "Newspaper 0402_01-0402_30," a distribution list of newspaper articles, was sent as scheduled at 4:00 AM on April 2nd, and six printers or multifunction peripherals are executing print processing in response to the print instruction. The printing status display screen 401B also shows that distribution is scheduled to six printing devices 200, one has completed printing based on the print instruction, two are operating and in a printing state, and three are in a non-operating state, having finished printing before all print pages had been printed.

[0063] The bottom section of the print status display screen 401B displays more detailed information for each of the six printing devices 200, including "Category," "Display Name," "Number of Pages to be Printed," "Number of Pages Completed Printing," "Page Number Being Printed," "Print Status," "Cause of Error," "Whether to Resume," and "Whether to Cancel." "Category" indicates the type of printing device 200. "Display Name" indicates the identification information of the printing device 200. "Number of Pages to be Printed" indicates the number of pages to be printed by the printing device 200 as a result of the distribution of the distribution list "Newspaper 0402_01-0402_30." "Number of Pages Completed Printing" indicates the number of pages that have been printed by the printing device 200 as a result of the distribution of the distribution list "Newspaper 0402_01-0402_30." "Page Number Being Printed" indicates the page number currently being printed by the printing device 200. "Print Status" indicates the status of the printing process by the printing device 200. "Cause of Error" indicates the cause of the error when the printing device 200 is in a stopped or terminated state. "Resume required" is an area that displays a button for resending a print instruction for an incomplete page. "Cancel required" is an area that displays a button for canceling the delivery or printing of pages after the page currently being printed.

[0064] In the illustrated example, the printing device 200 with ID01 is a so-called printer, and has completed printing all 30 pages that were scheduled to be printed. The printing device 200 with ID02 is a so-called printer, and has completed printing 10 of the 30 pages scheduled to be printed. An out-of-paper error occurred while printing the 11th page, temporarily halting the process. In this embodiment, in the event of an out-of-paper error, the user of the printing device 200 can clear the error by replenishing printing paper, and the printing device 200 will automatically resume printing. Therefore, the printing status display screen 401B does not display a "Resume" button in the "Resume?" field. Because printing of all 30 pages has not yet been completed, the printing status display screen 401B displays a "Cancel" button in the "Cancel?" field. The operator of the newspaper company terminal 400 can cancel printing of pages 11 and beyond by pressing the "Cancel" button via the operation unit 410.

[0065] The printing device 200 with ID03 is a so-called multifunction device. It has completed printing 10 of the 30 pages scheduled to be printed. While printing the 11th page, a paper jam error occurred, terminating the process. In this embodiment, unlike the out-of-paper error described above, the paper jam error terminates the printing process without waiting for the error to be resolved. Even if the error is resolved, the printing device 200 does not automatically resume printing. Therefore, to resume printing, a new print instruction from the distribution server 100 and redistribution of the print data from the image conversion server 500 are required. The print status display screen 401B displays a "Resume" button in the "Resume Required" field. The "Resume" button is an example of an object. When the operator of the newspaper company terminal 400 operates the "Resume" button via the operation unit 410, the newspaper company terminal 400 sends a resend instruction to the distribution server 100 for the print instructions. Upon receiving the resend instruction from the newspaper company terminal 400, the distribution server 100 sends print instructions for pages 11 and beyond to the printing device 200 with ID03. The printing device 200 with ID03 that has received the print instruction can receive print data for pages 11 and onward from the image conversion server 500. As described above, the printing status display screen 401B displays a "Cancel" button in the "Cancel" field.

[0066] Printing device 200 with ID04 is a so-called printer, and has completed printing 10 of the 30 pages scheduled to be printed. While printing page 11, the processing time exceeded a predetermined upper limit, resulting in a timeout and termination. Therefore, as described above, resuming printing requires a new print instruction from distribution server 100 and redistribution of the print data from image conversion server 500, and printing status display screen 401B displays a "Resume" button in the "Resume Required" field. When the operator of newspaper company terminal 400 operates the "Resume" button via operation unit 410, distribution server 100 issues a print instruction for pages 11 and onward, and image conversion server 500 retransmits the print data for pages 11 and onward to printing device 200. As described above, printing status display screen 401B displays a "Cancel" button in the "Cancel Required" field.

[0067] The printing device 200 with ID05 is a so-called printer, and the printing device 200 with ID06 is a so-called multifunction device. In both cases, printing of 10 pages of the total 30 pages to be printed has been completed, and the 11th page is currently being printed. Therefore, the printing status display screen 401B does not display the "Resume" button in the "Resume required" field. However, since printing of all 30 pages has not been completed, the printing status display screen 401B displays the "Cancel required" button in the "Cancel required" field.

[0068] As described above, the printing status display screen 401B of Figure 8 includes a display of the printing status of multiple, in this example six, printing devices 200 represented by ID01 to ID06 for the files in the above-mentioned "Newspaper 0402_01-0402_30" list, which is an example of specific content.

[0069] Although detailed description is omitted, the display unit 301 of the dealer terminal 300 also displays a print status display screen equivalent to the print status display screen 401B, and the operator can perform the same operations as those described above. This print status display screen of the display unit 301 is also an example of the first management screen.

[0070] <Processing flow (part 4)> 3, in S108, the distribution server 100 determines whether or not a printing error has occurred in the target printing device 200, in response to the print status notification received in S106 from the printing device 200. As described with reference to Fig. 8, if no printing error, such as running out of paper or a paper jam, has occurred, the distribution server 100 determines No in S108 and proceeds to S122.

[0071] In S122, the distribution server 100 determines whether or not the "Cancel" button on the printing status display screen 401B described above in FIG. 8 has been operated. When the "Cancel" button on the printing status display screen 401B of the newspaper company terminal 400 is operated, the newspaper company terminal 400 transmits a corresponding operation signal to the distribution server 100 in S120. If the operation signal has not been received, the distribution server 100 determines No in S122 and proceeds to S124. Note that operating the "Cancel" button on the printing status display screen 401B of the newspaper company terminal 400 is an example of a second operation. In S124, the distribution server 100 determines, based on the print status notification received in S106, whether the printing device 200 has finished printing all pages of the manuscript pages in the distribution list for which print instructions have been issued one page at a time since S94. If there are still unprinted pages, the distribution server 100 determines No in S124, returns the process to S94, and repeats the same procedure. As a result, the distribution server 100 repeats the processes in the order of S94, S108, S122, and S124, sending print data distribution instructions to the printing device 200 one page at a time to sequentially print the pages. On the other hand, if printing of all pages has been completed in S124, the distribution server 100 determines Yes in S124 and ends the sequence flow of FIG.

[0072] On the other hand, if a printing error such as a paper jam error or timeout occurs in the target printing device 200 in S108 and printing is terminated, the distribution server 100 determines Yes in S108 and proceeds to S110. In S110, the distribution server 100 sends an error notification to the retailer terminal 300 and proceeds to S114. In S114, the distribution server 100 sets the print error flag F, which indicates that a printing error has occurred, to 1, and ends the processing according to the sequence flow in Figure 3. Note that if the distribution server 100 determines Yes in S122 when an operation signal corresponding to the operation of the "Cancel" button is received in the above-mentioned S122, the distribution server 100 proceeds to S112.

[0073] In S112, the distribution server 100 transmits a stop instruction to the printing device 200 to stop printing of the print data one page at a time, which has been performed sequentially in the flow of S94, S108, S122, and S124. After processing S112, the distribution server 100 ends the processing according to the sequence flow of FIG.

[0074] 3 is repeated after setting flag F=1, distribution server 100 determines Yes in S82 of FIG. 3. Therefore, unless S92 is determined Yes by operating the "Resume" button, distribution server 100 does not issue a print instruction in S94. Therefore, the operation signal sent by newspaper company terminal 400 in S120 by operating the "Cancel" button on newspaper company terminal 400, which leads to the process flow of S122 to S112, is an abort instruction to abort the process of S94, which is the first transmission process. Furthermore, when distribution server 100 receives this operation signal and aborts printing in S112, it aborts the transmission of print instructions that have not yet been sent in S94, which is the first transmission process.

[0075] <Effects of the embodiment> As described above, this embodiment includes the distribution server 100, the image conversion server 500, the printing device 200, the newspaper company terminal 400, and the retailer terminal 300. The storage unit 115 of the distribution server 100 stores manuscript data. The image conversion server 500 converts the manuscript data into print data by executing S30. The distribution server 100 transmits a print instruction for the converted print data to the printing device 200 in S94. The printing device 200 receives the print instruction transmitted in S94 in S96, and prints the print data based on the print instruction in S100. In S70 and S80, the newspaper company terminal 400 and the dealer terminal 300 display a print status display screen 401B or the like on the display unit 401, 301, which shows the status of the print processing in the printing device 200. In response to the display of the print status display screen 401B or the like, when the operator operates the "Resume" button to instruct reprinting of the print data, the newspaper company terminal 400 or the dealer terminal 300 sends an instruction to resend the print instruction to the distribution server 100 in S90 or S91. As described above, according to this embodiment, the operator can manage the status up to the time the manuscript data is printed by using the print status display screen 401B and the like displayed on the display units 401, 301 of the newspaper company terminal 400 and the dealer terminal 300. In particular, the operator can send an instruction to resend the print instruction to the distribution server 100 by operating the "resume" button on the newspaper company terminal 400 and the dealer terminal 300 as necessary.

[0076] In particular, in this embodiment, the print status display screen 401B etc. includes a "Resume" button as an object. The operator can check the print status on the print status display screen 401B etc. and press the "Resume" button as necessary to cause the distribution server 100 to resend the print instruction.

[0077] In particular, in this embodiment, the print status display screen 401B displays an object only when an abnormality occurs in S100. That is, according to this embodiment, it is possible to appropriately display an object for receiving necessary operations depending on whether the status of S100 is good or bad.

[0078] Furthermore, particularly in this embodiment, the operator can check the status of S100 through the print status display screen 401B, etc., and press the "Cancel" button as necessary to cause the distribution server 100 to stop sending the print instruction.

[0079] Furthermore, in this embodiment in particular, the operator can collectively manage the printing status of a plurality of printing apparatuses 200 for specific document data using the printing status display screen 401B or the like.

[0080] In particular, in this embodiment, the newspaper company terminal 400 displays a conversion status display screen 401A on the display unit 401, and if a conversion error occurs, reports it in S48. The operator can recognize through the conversion status display screen 401A that some abnormality has occurred in the image conversion process of S30.

[0081] Furthermore, in this embodiment, as described above, if there is a page in the manuscript data that has not been uploaded, a corresponding notification can be given. In this case, by receiving the notification, the operator can recognize that there is manuscript data that has not been uploaded for some reason.

[0082] Furthermore, in this embodiment in particular, as described above, when there is a page of manuscript data that has not been uploaded, a print instruction for print data indicating the existence of data for that page that has not been uploaded can be sent to the printing device 200. In this case, based on a print instruction from the distribution server 100, the printing device 200 prints out a printed matter including a guidance message, and the operator can recognize that there is manuscript data that has not been uploaded for some reason.

[0083] In particular, in this embodiment, the distribution server 100 determines in S12 whether there is a difference between the data of the newly uploaded manuscript data and the manuscript data already stored in the database of the storage unit 115 of the distribution server 100. According to this embodiment, when the content of manuscript data that has already been uploaded is updated, the distribution server 100 determines this in S12 and distributes the updated page to the printing device 200 for printing.

[0084] <Other variations> In the above, the distribution server 100 and the image conversion server 500 have been described as single devices, but the functions of the distribution server 100 or the image conversion server 500 may be fulfilled by multiple devices operating in conjunction with each other.

[0085] Although the above description has been given using newspaper articles as an example of content, the present invention is not limited to this and other service content may be used, such as advertisements, comics, novels, or thumbnails of parts of these.

[0086] Furthermore, the sequence flows shown in Figures 2 and 3 do not limit the present disclosure to the procedures shown in the above flows, and steps may be added or deleted or the order may be changed within the scope that does not deviate from the intent and technical idea of ​​the disclosure.

[0087] In addition to the above, the methods according to the above embodiments and modifications may be used in appropriate combination.

[0088] Although not specifically illustrated, the present disclosure can be implemented with various modifications within the scope of the spirit thereof. [Explanation of symbols]

[0089] 1. Print Management System 100 Distribution server (example of server) 110 control section 115 Memory unit (an example of memory) 140 Communications Department 200 Printing device (example of printer) 300 Dealer terminal (an example of an information processing device) 301 Display section 400 Newspaper company terminal (an example of an information processing device, an example of an external device) 401 Display section 401A Conversion status display screen (example of the second management screen) 401B Printing status display screen (example of the first management screen) 500 Image conversion server (example of a server)

Claims

1. A print management system in which a server, a printer, and an information processing device are configured to be able to communicate with each other via a network, The server a memory for storing content; and, a conversion process for converting the content into print data for each partial data; a first transmission process for transmitting a print instruction of the print data converted in the conversion process to the printer; Run The printer a receiving process for receiving the print instruction transmitted in the first transmitting process; a printing process for printing the print data based on the print instruction received in the receiving process; Run The information processing device includes: a first display process for displaying a first management screen showing a status of the printing process on a display; a second transmission process of transmitting a retransmission instruction for the print instruction to the server in response to receiving a first operation for instructing reprinting of the print data; A print management system that runs

2. The first management screen The print management system according to claim 1 , further comprising an object displayed for accepting the first operation.

3. The object is 3. The print management system according to claim 2, wherein if an abnormality occurs in the printing process, it is displayed on the first management screen.

4. The information processing device includes: transmitting an instruction to cancel the first transmission process to the server in response to receiving a second operation instructing to cancel the printing process; The server The print management system according to claim 1 , wherein, when the cancel instruction is received, transmission of the print instruction that has not been transmitted in the first transmission process is canceled.

5. The first management screen The print management system according to claim 1 , further comprising a display of print states of a plurality of said printers for a particular said content.

6. The information processing device further comprises: a second display process for displaying a second management screen showing a status of the conversion process on the display; a notification process for notifying that an abnormality has occurred in the conversion process; The print management system of claim 1 , wherein the print management system executes the following steps:

7. the memory stores the partial data of the content uploaded from an external device; The server performs a notification process to notify the information processing device if there is any partial data of the content that has not yet been uploaded, based on the upload deadline of the content and information related to the content to be uploaded. The print management system of claim 1 , wherein the print management system executes the following steps:

8. a third transmission process in which the server transmits, to the printer, a print instruction for print data indicating the existence of the partial data that has not been uploaded, when the partial data that has not been uploaded exists; The print management system according to claim 7, wherein the print management system executes the following:

9. The server executes a determination process to determine whether there is a difference between the partial data of the content uploaded from the external device and the partial data of the content stored in the memory; The print management system according to claim 7 , wherein when it is determined in the determination process that there is a difference, the conversion process of the uploaded partial data is executed.

10. A server having a communication unit capable of communicating with a printer and an information processing device, a memory for storing content, and a control unit, The control unit a conversion process for converting the content into print data for each partial data; an instruction transmission process for transmitting a print instruction for the print data converted in the conversion process to the printer; an instruction receiving process for receiving an instruction to resend the print instruction in response to a predetermined operation for instructing reprinting of the print data on a management screen displayed on a display of the information processing device and showing the status of the print processing of the printer; The server that runs

11. A print management method executed by a print management system in which a server, a printer, and an information processing device are configured to be able to communicate with each other via a network, comprising: a conversion step of converting the content into print data for each partial data; a first transmission step of transmitting a print instruction of the print data converted in the conversion step to the printer; a printing step of receiving the print instruction transmitted in the first transmission step and printing the print data by the printer based on the print instruction; a display step of displaying a management screen showing a processing status of the printing step on a display of the information processing device; a second sending step of sending a resend instruction to the server in response to receiving a predetermined operation to instruct reprinting of the print data; A printing management method comprising:

Images