JP2005100348A - Printing processor, image processor, method for controlling printing processor, control program for printing processor, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a printing processor managing the printing processing conditions of an image processor, a method for controlling the printing processor, a control program for the printing processor, and the image processor which provides information indicating a printing processing conditions to the printing processor. <P>SOLUTION: The printing processor for allowing a prescribed image processor to print out document data specified by a request outputted from a client device connected through a network in accordance with the request comprises: a printing condition acquisition means for acquiring printing state information indicating the printing processing conditions of document data in the prescribed image processor requesting the printing of the document data from the image processor; and a printing state information storing means for storing the printing condition information acquired by the printing condition acquisition means. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a print processing device for causing an image processing device to print document data, a control method for the print processing device, a control program for the print processing device, and a recording medium. The present invention also relates to an image processing apparatus that executes printing based on a request from the print processing apparatus.

  When printing document data, the user may instruct the application corresponding to the document data to print. When the application executes print processing based on the print instruction, print data that can be interpreted by the printer based on the document data is generated by the printer driver and spooled in the spooler. The spooled print data is transmitted to a printer and printed on paper by the printer.

  Here, the processing by the spooler is executed asynchronously with the print instruction by the user. That is, for the application directly used by the user, after the print data generated by the printer driver is spooled in the spooler, the control of the process is restored before the printing process by the printer is completed.

  By executing the processing by the spooler asynchronously, the user can perform an operation using the application without waiting for the completion of the printing processing by the printer after issuing the print instruction.

  However, such a mechanism has a problem that it is difficult for the user to confirm the result of the printing process in the printer. In other words, the user can recognize the return of the application until the print data is normally spooled by the spooler. Further, a tool for confirming the status of a print job is provided by the OS. The tool is for referring to the status of the job in the spooler, and the status of processing in the printer, for example, a paper jam, The fact that the processing is interrupted due to running out of toner or the like cannot be confirmed unless the user actually goes to the printer.

  The present invention has been made in view of the above points, and is capable of managing the status of print processing in an image processing apparatus, a control method for the print processing apparatus, and a control program for the print processing apparatus. An object of the present invention is to provide an image processing apparatus capable of providing information indicating the state of print processing to the print processing apparatus.

  Accordingly, in order to solve the above-described problem, the present invention provides a predetermined image processing device that converts document data specified in a request in response to a request from a client device connected via a network. A print processing apparatus that prints the document data, and obtains print status information indicating the status of the print processing of the document data in the image processing apparatus from the predetermined image processing apparatus that has requested printing of the document data And a printing status information holding unit that holds the printing status information acquired by the printing status acquisition unit.

  In such a print processing apparatus, it is possible to acquire and manage the state of print processing in an image processing apparatus such as a printer that is a printing destination of document data.

  In order to solve the above problem, according to the present invention, as described in claim 13, an image for executing print processing of document data transmitted from the print processing apparatus according to any one of claims 1 to 12. An image processing apparatus, wherein the image processing apparatus transmits print status information indicating a status of the print processing to the print processing apparatus in response to a request from the print processing apparatus.

  In such an image processing apparatus, it is possible to provide information indicating the state of print processing to a print request source.

  In order to solve the above problems, the present invention provides a control method for the print processing apparatus, a program for causing a computer to execute the control method for the print processing apparatus, or a recording medium on which the control program for the print processing apparatus is recorded. Also good.

  According to the present invention, a print processing apparatus capable of managing the status of print processing in an image processing apparatus, a control method for the print processing apparatus, a control program for the print processing apparatus, and print processing for the print processing apparatus It is possible to provide an image processing apparatus that can provide information indicating the state of the image.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a printing system according to an embodiment of the present invention. As shown in FIG. 1, the printing system 1 according to the present embodiment includes a print server 10, a document management server 20, a Web server 30, a terminal 40, and the like. (Wired or wireless).

  The print server 10 is a computer that provides a function for causing the printer 50 to print document data or the like as a Web service, and includes a print service 11 in which such a function is installed.

  The document management server 20 is a computer that provides a document data management function as a Web service, and includes a document management service 24 in which the document management function is implemented. The document management service 24 includes a SOAP listener 21, a document management unit 22, a document management DB 23, and the like. The SOAP listener 21 is a module in which a function for enabling the function of the document management means 22 to be called by the RPC of SOAP. The document management means 22 is a module that provides an interface for operating document information stored in the document management DB 23. For example, the document management unit 22 registers a document acquisition method for acquiring document data from the document management DB 23, a document list acquisition method for acquiring document data list information, and registration of document data in the document management DB 23. It has a document registration method. The document management DB 23 is a database that stores document data.

  The Web server 30 is a so-called Web server that provides a Web page for using functions of the data management server 10 and the document management server 20, and includes an httpd 31, a Web application 32, a SOAP proxy 33, and the like. The httpd 31 is a daemon program that controls HTTP communication with the terminal 40. When the httpd 31 receives an HTTP request from the terminal 40, the httpd 31 calls the Web application 32 corresponding to the URL specified in the HTTP request, and transmits the Web page output as a processing result by the Web application 32 to the terminal 40.

  The web application 32 is a so-called web application whose main function is to generate a web page. The Web application 32 makes a predetermined processing request to the print server 10 and the document management server 20 as necessary, and generates a Web page that displays the result. For example, the Web application 32 generates a Web page (hereinafter referred to as “document list page”) that displays a list of document data managed in the document management DB 23 of the document management server 20.

  The SOAP proxy 33 is a module that provides the Web application 32 with an interface for calling various methods implemented in the print server 10 and the document management server 20 by means of SOAP RPC. The SOAP proxy 33 enables the Web application 32 to call the method of the functions of the print server 10 and the document management server 20 transparently without being aware of network communication.

  In the figure, the Web application 32 is shown as one block, but there are a plurality of instances. For example, the source code is implemented for each module for generating a document list page and other modules for generating other Web pages.

  The terminal 40 has a communication function such as a PC (Personal Computer), a PDA (Personal Digital (Data) Assistants), or a mobile phone that provides an interface (Web page) for the user to use the printing system 1 by the Web browser 41. It is a terminal.

  In the drawing, the terminal 40 and the printer 50 are shown as one block, but it is not intended to be physically limited to one terminal or printer. As with a general information system, a large number of terminals and printers can be connected.

  Next, a hardware configuration example of the print server 10 will be described. FIG. 2 is a diagram illustrating a hardware configuration example of the print server according to the embodiment of the present invention. The print server 10 shown in FIG. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, an arithmetic processing device 104, and an interface device 105 that are connected to each other via a bus B. The

  A program for realizing print data generation processing in the print server 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100.

  The auxiliary storage device 102 stores the installed program and also stores necessary files and data. The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The arithmetic processing device 104 executes functions related to the print server 10 in accordance with a program stored in the memory device 103. The interface device 105 includes, for example, a modem, a router, etc., and is used for connecting to a network. The document management server 20 and the Web server 30 can have the same hardware configuration as that of the print server 10 shown in FIG.

  Next, details of the print service 11 in the print server 10 will be described. FIG. 3 is a diagram illustrating a functional configuration example of a print service in the print server according to the first embodiment. As shown in FIG. 3, the print service 11 includes a SOAP listener 111, a print request reception unit 112, a print instruction unit 113, a document application 114, a printer driver 115, a spooler 116, a port program 117, a printer control unit 118, and event monitoring. A unit 119, an asynchronous management unit 120, a document management connection unit 121, a print job queue 131, a job status file 132, and the like.

  The SOAP listener 111 is a module that provides a function for allowing a later-described method of the print request receiving unit 112 to be called from the Web server 30 or the like by SOAP RPC.

  The print request receiving unit 112 is a module in which a method for providing the function of the print service 11 is mounted. For example, the print request receiving unit 112 is mounted with a print method for receiving a print request for document data, a print status acquisition method for receiving an inquiry as to whether or not print processing based on the print request has been completed, and the like. ing. By enabling the functions of the print service 11 to be called by SOAP RPC, the client-side implementation can be facilitated in the system construction in the Internet environment.

  The print instruction unit 113 is a module that issues a document data print instruction to the document application 114 in response to a print request from the print method in the print request reception unit 112 (hereinafter referred to as a print instruction by the print instruction unit 113). Jobs are called “print jobs”.) However, the print instruction unit 113 does not immediately execute a print job when a print request is received from the print method. The print instruction unit 113 executes a print job asynchronously with the print request by using an asynchronous management unit 120 and a print job queue 131 described later.

  The asynchronous management unit 120 is a program for periodically prompting the print instruction unit 113 to execute a print job, and is activated as an independent process.

  The print job queue 131 temporarily stores information (hereinafter referred to as “job information”) that defines the contents of a print job included in a print request received from the print method by the print instruction unit 113. It is a file for.

  The document application 114 is an application used for generating and editing document data, and corresponds to various applications such as word processing software and spreadsheet software. The printer driver 15 is a so-called printer driver provided with a printer when the printer is purchased, and is a module for converting document data into print data in a format that can be processed by the printer 50 as a printing destination.

  The spooler 116 is a so-called spooler provided by an OS (Operating System) such as Windows (registered trademark). The spooler 116 temporarily stores print data generated by the printer driver 115 and sequentially stores the stored print data. Output to program 117.

  The port program 117 corresponds to the positioning of a module generally called a port monitor. In the present embodiment, a port program 117 is used instead of the port monitor provided in advance by the OS. It has been. That is, a general port monitor has a function of outputting print data output from a spooler to a printer, but the port program 117 is not for the printer but for the printer control means 118. Implemented to output print data.

  In Windows (registered trademark), a function for setting a module that is uniquely implemented to be called by a spooler is provided instead of a port monitor provided in advance. The port program 117 may be called from the spooler 116 using such a function.

  The printer control unit 118 is a program that transmits the print data output from the port program 117 to the printer 50 and constantly monitors the status of print processing in the printer 50. The printer control unit 118 generates an event indicating that, for example, when the state of the printing process in the printer 50 changes. The event monitoring unit 119 is a program that executes processing (details will be described later) according to the type of the event based on the event generated by the printer control unit 118.

  The document management connection unit 15 is a module that provides an interface for calling the function of the document management unit 22 in the document management server 20 by SOAP RPC.

  The job status file 132 is a file for holding information (status information) relating to the status of the print job, and is generated for each print job when the print job occurs.

  Hereinafter, the processing procedure of the printing system 1 in the first embodiment will be described. FIGS. 4 to 6 are sequence diagrams for explaining document data printing processing in the printing system according to the first embodiment.

  In step S11, the user of the terminal 40 selects document data to be printed (hereinafter referred to as “target data”) on the document list page displayed on the Web browser 41, and further defines the printing process on the setting page. When the parameter information (hereinafter referred to as “print parameter information”) is set, the Web browser 41 transmits a print request for the target data to the Web server 30.

  FIG. 7 is a diagram illustrating a display example of a document list page. The document list page 410 can be displayed on the web browser 41 by inputting the URL of the document list page 410 into the web browser 41. That is, when the Web browser 41 transmits a transmission request for the document list page 410 to the Web server 30 based on the URL input by the user, the Web application 32 of the Web server 30 passes through the document management unit 22 of the document management server 20. Thus, the document list information of the predetermined folder in the document management DB 23 is acquired. The Web application 32 generates a Web page (document list page 410) on which the acquired document data list information is posted. The document list page 410 generated by the web application 32 is transmitted to the terminal 40 by the httpd 31 and displayed on the web browser 41.

  In the document list page 410, each document data is displayed as a thumbnail in an area 411. Here, if a rectangular area in which one document data is displayed is called a “cell”, each cell has a check button for selecting the document data, and a document data name (document name). Has a document name display area and an icon display area. For example, a cell in which document data with the document name “Document 3” is displayed includes a check button 413, a document name display area 414, and an icon display area 415.

  The user checks the check button corresponding to the document data to be printed (in FIG. 7, check document 1), and selects the menu item “print” (not shown) displayed by clicking the document output menu 412 Then, a setting page is displayed on the web browser 41.

  FIG. 8 is a diagram illustrating a display example of the setting page. A setting page 420 in FIG. 8 includes a target document display area 421 and a print condition setting area 422. In the target document display area 421, a list of document names of target data selected as print targets on the document list page 410 is displayed. In the print condition setting area 422, it is possible to set a printer to be printed, a document size, a print direction, a print start position, and the like.

  When the user sets print parameter information on the setting page 420 and clicks an OK button 423, the Web browser 41 transmits the print request in step S11 described above to the Web server 30 with the print parameter information.

  Progressing to step S12 following step S11, the web application 32 of the web server 30 transmits a SOAP message for calling the print method of the print request reception unit 112 of the print server 10 by SOAP RPC to the print server 10. As a result, the print server 10 is requested to print the target data.

  FIG. 9 is a diagram illustrating an example of a SOAP message when a print method is called. In the SOAP message 710 of FIG. 9, “PrintDocument” which is the tag name of the tag 711 is the method name of the print method. The description 712 is argument information. For example, a description 713 surrounded by <jobName> tags is an argument in which the job name of a print job generated based on the call of the print method is specified. In the present embodiment, the document name of the target data is used as the job name. A description 714 surrounded by <clientName> tags is an argument in which the name of the terminal 40 that is the caller of the print method is specified. A description 715 surrounded by a <docTicket> tag is an argument in which an electronic ticket (hereinafter referred to as “document ticket”) for acquiring target data from the document management server 20 is specified. The document ticket is issued in advance by the Web application 32 from the document management server 20, and information for specifying target data is recorded. Note that the character string shown in the description 715 is a further encrypted version of the ticket encoded. A description 716 surrounded by a <repositoryURL> tag is an argument in which the URL of the server (document management server 20) where the target data is stored is designated.

  In step S13 following step S12, the print request reception unit 112 of the print server 10 for which the print method has been called requests the print instruction unit 113 to print the target data. Progressing to step S14 following step S13, the print instructing unit 113 assigns a job ID which is information for uniquely identifying a print job to be executed in response to the print request. Here, “001” is assigned as the job ID, and the print job with the job ID “001” is referred to as “print job 001”. Progressing to step S15 following step S14, the print instructing unit 113 registers information associating the numbered job ID with the print parameter information specified as the argument of the print method in the print job queue 131 as job information. (S15).

  FIG. 10 is a diagram illustrating a configuration example of job information in the print job queue. As shown in FIG. 10, the job information 1310 includes a job ID, a target data ID, a user name, a printer name, a target data acquisition destination URL, and the like.

  The job ID is the job ID assigned in step S14. The target data ID is a document ID that uniquely identifies the target data. The user name is a name for uniquely identifying the user of the terminal 40 that is the print request source in the printing system 1. The printer name is a name that identifies the printer 50 that is the printing destination. The target data acquisition destination URL indicates the URL (position information) of the server (document management server 20) where the target data is stored.

  In addition, the job information 1310 includes print parameter information to be set on the setting page 420, but is omitted for convenience in FIG.

  Progressing to step S16 following step S15, the print instruction unit 113 generates a job status file 132 for managing the status information of the print job 001, and sets the initial value of the status information of the print job 001 in the generated job status file 132. register.

  FIG. 11 is a diagram illustrating a configuration example of status information of a print job. In FIG. 11, the left column indicates the item names of the items constituting the status information, and the right column indicates the value of each item registered in step S16. As shown in FIG. 11, the status information includes a job ID, a job status, a job reception time, a job name, a client name, a reason for interruption, and the like.

  The job ID is the job ID described above. The job status is a character string for identifying the status of the print job. Here, “pending” indicating that the print job is waiting in the print job queue 131 is registered. The job reception time is the time when the print instruction unit 113 receives a print job. The job name and client name are the job name and client name specified as arguments of the print method. The reason for interruption is information indicating the cause of the interruption when the job status indicates that the printing process has been interrupted.

  In step S17 following step S16, the print instructing unit 113 outputs the job ID assigned in step S14 to the print request receiving unit 112 without executing the printing process here. Progressing to step S18 following step S17, the print request reception unit 112 transmits a SOAP message including the job ID to the web application 32 as return information of the print method.

  FIG. 12 shows a SOAP message including print method return information. In the SOAP message 720 of FIG. 12, the part indicated by reference numeral 721 is the job ID. That is, the job ID “001” is shown surrounded by <jobID> tags in the description 721. The job ID received by the web application 32 is stored for each user in the web server 30 by the web application 32, and is used when the web application 32 checks the status of the print job.

  Progressing to step S19 following step S18, the web application 32 displays a web page (hereinafter referred to as “response page”) indicating that the print request is accepted as a response to the print request via the httpd 31. Send to. The response page is displayed by the Web browser 41, and the user can confirm that the print request has been received normally.

  On the other hand, in the print server 10, the asynchronous management unit 120 periodically urges the print instruction unit 113 to execute a print job (S20). Based on the call from the asynchronous management unit 120, the print instruction unit 113 refers to the print job queue 131. When the job information is registered in the print job queue 131, the print instruction unit 113 acquires the job information and the print job. The job status value in the job status file 132 is updated to “processing” indicating that the printing process is in progress (S21). Here, it is assumed that the job information of the print job 001 has been acquired.

  FIG. 13 is a diagram illustrating an example of status information in the job status file in which the job status is updated to processing. As shown in FIG. 13, the value of the job status of the print job 001 is updated from “pending” to “processing”.

  Progressing to step S22 following step S21, the print instruction unit 113 receives the job information from the document management unit 22 of the document management server 20 specified by the “target data acquisition destination URL” in the acquired job information (FIG. 10). In order to acquire the target data specified by the “target data ID”, the session management method of the document management unit 22 is called by SOAP RPC to request the document management unit 22 to open a session.

  Progressing to step S23 following step S22, the document management unit 22 establishes a session with the print instruction unit 113, and sets a session ID uniquely identifying the session as a return value of the session establishment method to the print instruction unit 113. To send. (S24).

  Progressing to step S25 following step S24, the print instruction unit 113 requests the document management unit 22 to transmit the target data by calling the document acquisition method of the document management unit 22. Note that a document ticket is specified as information for specifying target data in the argument of the document acquisition method. The document management unit 22 retrieves the target data from the document management DB 23 and transmits the target data to the print instruction unit 113 (S27).

  Progressing to step S28 (FIG. 5) following step S27, the print instruction unit 113 requests the document application 114 corresponding to the type of the target data acquired from the document management server 20 to print the target data. When the document application 114 requests the printer driver 115 to print the target data (S29), the printer driver 115 generates print data of the target data and stores the generated print data in a predetermined folder (S30). When the print data is stored, control of the process returns to the print instruction unit 113 via the document application 114 (S31, S32).

  Progressing to step S33 following step S32, the print instructing unit 113 acquires the temporarily stored print data, and outputs the print data to the spooler 116, thereby issuing a print request to the spooler 116. Do. Progressing to step S34 following step S33, the spooler 116 makes a response to the print request to the print instruction unit 113. Since the spooler 116 executes print processing asynchronously with respect to the print request as is well known, the response in step S34 is performed before the spooler 116 executes print processing (S36) described later. When control of the process returns from the print instruction unit 113 to the asynchronous management unit 14 (S35), the process called by the asynchronous management unit 14 in step S20 ends.

  On the other hand, the spooler 116 issues a print data print request to the port program 117 asynchronously with the request from the print instruction means 113 (S36). Progressing to step S37 following step S36, the port program 117 indicates that the printer 50 is processing the job status value in the status information (FIG. 13) registered in the job status file 132 for the print job 001. Update to “executing”. Strictly speaking, the processing in the printer 50 is not started at this timing. However, as will be described later, since a print request is made to the printer 50 immediately after this, in this embodiment, the job is processed at this timing. The status value is updated to “executing”.

  FIG. 14 is a diagram illustrating an example of status information in the job status file in which the job status is updated to executing. As illustrated in FIG. 14, the job status value of the print job 001 is updated from “processing” to “executing”.

  Progressing to step S38 (FIG. 6) following step S37, the port program 117 issues a print request to the printer control means 118. Proceeding to step S39 following step S38, the printer control means 118 transmits print data to the printer 50 and requests printing of the print data. The printer 50 receives a print request, and assigns an ID (equipment job ID) for uniquely identifying a job (hereinafter referred to as “device job”) executed in the printer 50 in response to the print request. The device job ID is transmitted to the printer control means 118 (S40). The device job ID is further output from the printer control means 118 to the port program 117 (S41). In response to the print request, the printer 50 executes a print process of the device job, that is, print data at a predetermined timing (S42).

  After notifying the port job 117 of the device job ID (S41), the printer control means 118 makes an inquiry about the status of the printing process to the printer 50 (S43). This inquiry is repeated until the printing process in the printer 50 is completed. In this embodiment, “complete” of the printing process is not only a state in which the printing process has been normally completed, but also a process in which no operation is performed by the user, such as a suspended state or a suspended state. It also means a state that does not resume.

  When the status of the printing process is returned from the printer 50 (S44), the printer control means 118 generates an event indicating the status of the printing process in the printer 50. The event is detected by the event monitoring unit 119 (S45). Note that the event monitoring unit 119 is notified of the job ID and device job ID of the print job along with the event.

  Here, as a specific method for mounting an event, for example, as a first method, the printer control unit 118 generates a signal used as a kind of interprocess communication in a UNIX (registered trademark) OS or the like. It may be. In this case, the event monitoring unit 119 may be mounted so that the signal can be fetched.

  As a second method, the printer control unit 118 may output the print processing status to a predetermined file. In this case, the event monitoring unit 119 may be mounted so as to monitor the update of the predetermined file by polling or the like.

  Further, as a third method, the printer control unit 118 may call a predetermined method of the event monitoring unit 119.

  Progressing to step S46 following step S45, the event monitoring unit 119 updates the job status value in the job status file 132 according to the content of the event generated by the printer control unit 118. For example, when the event indicates that the printing process has been normally completed, the event monitoring unit 119 updates the value of the job status to “completed”. Further, when the event indicates that the printing process is stopped due to the occurrence of an error, the event monitoring unit 119 updates the value of the job status to “aborted”. When the event indicates that the printing process is interrupted due to the occurrence of an error, the event monitoring unit 119 updates the job status value to “stopped-error” to indicate the cause of the interruption. Information is registered as the reason for interruption of status information in the job status file 132. Here, the information indicating the cause of the interruption includes out of paper, paper jam, offline state (the printer 50 is turned off), or out of toner.

  FIG. 15 is a diagram illustrating an example of status information in the job status file in which the job status is updated to completed. As shown in FIG. 15, the job status value of the print job 001 is updated from “executing” to “completed”.

  Next, processing when an inquiry is made to the print server 10 as to whether or not the printing processing in the printer 50 has been completed will be described. FIG. 16 is a sequence diagram for explaining the processing when there is an inquiry as to whether or not the printing processing in the printer has been completed.

  In step S47, based on the input to the web browser 41 by the user of the terminal 40, the web browser 41 displays the status of the printing process related to the print request (FIG. 4: S11) previously made by the user of the terminal 40. A transmission request (HTTP request) of (print status display page) is transmitted to the Web server 30. Examples of the input by the user include inputting a URL for the print status display page, clicking a link to the print status display page in another Web page, and the like.

  In step S48 following step S47, the web application 32 transmits a SOAP message for calling the print status acquisition method of the print request reception unit 112 of the print server 10 by SOAP RPC to the print server 10. The print server 10 is inquired about the print processing status.

  FIG. 17 is a diagram illustrating an example of a SOAP message when calling the print status acquisition method. In the SOAP message 730 of FIG. 17, the tag name “isCompleted” of the tag 731 is the method name of the print status acquisition method. A description 732 surrounded by <jobID> tags is argument information in which a job ID of a print job (hereinafter referred to as “current job”) for which a print result inquiry is made is specified.

  Proceeding to step S49 following step S48, the print request receiving means 112 of the print server 10 for which the print status acquisition method has been called acquires the job status value of the current job from the job status file 132 of the current job. Therefore, here, as the value of the job status, “pending”, “processing”, “executing”, “completed”, “aborated”, or “stopped-error” is acquired.

  Proceeding to step S50 following step S49, the print request receiving means 112 determines whether or not the print processing for the current job is completed. Here, as described above, “completed” includes not only when the printing process is normally completed (completed) but also when it is stopped (aborated) or when it is interrupted (stopped-error). Accordingly, when the job status of the current job is completed, aborted, or stopped-error, the print request receiving unit 112 determines that the processing for the current job is complete.

  Progressing to step S51 following step S50, the print request receiving unit 112 transmits a SOAP message including information indicating the print processing status of the current job to the web application 32 as return information of the print status acquisition method.

  FIG. 18 is a diagram illustrating a SOAP message including return information of the print status acquisition method. In the SOAP message 740 of FIG. 18, description 741 is information indicating whether or not processing for the current job is completed. That is, when the value enclosed in the <returnValue> tag is “true”, it indicates that the current job is completed, and when it is “false”, it indicates that the current job is not completed.

  A description 742 indicates the job status of the current job. That is, a character string indicating the value of the job status is shown surrounded by <status> tags.

  Note that when the job status value is “stopped-error”, the return information further includes information indicating the cause of the interruption of the current job.

  FIG. 19 is a diagram illustrating a SOAP message including return information of the print status acquisition method when the job status is “stopped-error”. The SOAP message 750 in FIG. 19 has almost the same configuration as the SOAP message 740 in FIG. That is, the description 751 indicates whether or not the processing for the current job is completed, and the description 752 indicates the job status of the current job. However, the SOAP message 750 includes a description 753 surrounded by <reason> tags. Description 753 is information indicating the cause of job interruption, and “out of paper” is indicated as the information here.

  Progressing to step S52 following step S51, the web application 32 generates a print status display page based on the return information from the print request receiving means 112. When the return information indicates that the current job has been completed normally or has been canceled, the Web application 32 can, for example, “print processing has ended normally” or “print processing has been canceled. The print status display page is generated so that the message “Done” is displayed. When the return information indicates that the current job is interrupted, the Web application 32 performs a printing process such as “Printing process is interrupted due to running out of paper”. A print status display page is generated so that a message indicating the cause of the interruption is displayed.

  Progressing to step S53 following step S52, when the web application 32 transmits a print status display page to the terminal 40 via the httpd 31, the web browser 41 displays the print status display page. The user can check the print status of the printer 50 by referring to the print status display page.

  As described above, according to the print server 10 in the first embodiment, even after making a print request to the printer 50, the printer control means 118 inquires about the status of the print processing in the printer 50, and the result Is stored in the job status file 132, the print processing state in the printer 50 can be managed.

  In addition, since the print status acquisition method in the print request reception unit 112 is published on the network via the SOAP listener 111, it is possible to receive a print processing status query from a client such as the Web application 32. It is possible to respond with information indicating whether the printing process has been completed, the state of the printing process, and information indicating the cause when the printing process is interrupted. As a result, on the client side, functions such as notification of such information to the user can be realized.

  Next, as a second embodiment, an example in which the function in the printer 50 is implemented as a Web service will be described. FIG. 20 is a diagram illustrating a functional configuration example of a print service and a printer in the print server according to the second embodiment. 20, parts that are the same as the parts shown in FIG. 3 are given the same reference numerals, and explanation thereof is omitted.

  As shown in FIG. 20, the print service 11 in the second embodiment includes the spooler 116, the port program 117, the printer control means 118, and the event monitoring means included in the first embodiment (FIG. 3). 119 is not included, but a SOAP proxy 122 is added. The SOAP proxy 122 is a module in which an interface for calling a method in the print interface unit 52 in the printer 50 (to be described later) by SOAP RPC is installed.

  On the other hand, the printer 50 in the second embodiment includes a SOAP listener 51, a print interface means 52, and the like. The SOAP listener 51 is a module in which a function for enabling a method in the print interface means 52 to be called by a SOAP RPC.

  The print interface means 52 includes a method for receiving a print request (hereinafter referred to as “print execution method”), a method for providing a print processing state (hereinafter referred to as “print status acquisition method”), and the like. It is a module that has been.

  Hereinafter, the processing procedure of the printing system 1 in the second embodiment will be described. FIG. 21 is a sequence diagram for explaining document data printing processing in the printing system according to the second embodiment.

  Until the print instruction unit 113 of the print server 10 acquires the document data (target data) designated as the print target from the document management server 20 based on the print request of the document data from the Web browser 41 of the terminal 40. Since it is the same as the process in the first embodiment (FIG. 4: S11 to S27), the description thereof is omitted in the second embodiment. Therefore, in FIG. 21, it demonstrates as a continuation of step S27 of FIG.

  In step S <b> 101, the print instruction unit 113 requests the document application 114 corresponding to the type of the target data acquired from the document management server 20 to print the target data. When the document application 114 requests the printer driver 115 to print the target data (S102), the printer driver 115 generates print data of the target data and stores the generated print data in a predetermined folder (S103).

  When control of the process returns from the printer driver 115 to the asynchronous management unit 14 via the document application 114 and the print instruction unit 113 (S104, S105, S106), the process called by the asynchronous management unit 14 in step S20 (FIG. 4) is performed. finish.

  In step S107 following step S106, the print instruction unit 113 updates the job status value in the job status file 132 of the print job to be processed (hereinafter referred to as “current job”) to “executing”. To do.

  In step S108 following step S107, when the print instruction unit 113 calls the print execution method of the SOAP proxy 116 by specifying the stored print data as an argument, the SOAP proxy 116 prints the print interface unit of the printer 50. A SOAP message (SOAP request) including call information of the print execution method 52 is transmitted to the printer 50 (S109). The SOAP message from the SOAP proxy 116 is received by the SOAP listener 51 of the printer 50, and the print execution method of the print interface unit 52 is called by the SOAP listener 51.

  Proceeding to step S110 following step S109, the print interface unit 52 assigns a device job ID for the device job executed in the printer 50 in response to a print request by the print execution method, and a SOAP message including the device job ID. (SOAP response) is transmitted to the print server 10 via the SOAP listener 51. Thereafter, a printing process is executed at a predetermined timing in the printer 50 (S111).

  The SOAP proxy 116 that has received the SOAP response from the printer 50 outputs the device job ID included in the SOAP response to the print instruction unit 113 (S112). Progressing to step S113 following step S112, the print instruction unit 113 generates a monitoring thread 1121 as a thread for monitoring the state of the printing process in the printer 50.

  Progressing to step S114 following step S113, when the monitoring thread 1121 calls the print status acquisition method of the SOAP proxy 116, the SOAP proxy 116 includes a SOAP message including call information of the print status acquisition method of the print interface means 52 of the printer 50. (SOAP request) is transmitted to the printer 50 (S115). Here, the transmitted SOAP message is the same as the SOAP message 730 described in FIG. The SOAP message from the SOAP proxy 116 is received by the SOAP listener 51 of the printer 50, and the print status acquisition method of the print interface unit 52 is called by the SOAP listener 51.

  Proceeding to step S116 following step S115, the print interface means 52 acquires information (normal end, cancellation, interruption, etc.) indicating the state of the printing process (device job) in the printer 50, and sends a SOAP message including the information. It is transmitted to the print server 10 via the SOAP listener 51. Note that the SOAP message transmitted here is the same as the SOAP message 740 or 750 described with reference to FIGS.

  Progressing to step S117 following step S116, when the SOAP proxy 116 outputs to the monitoring thread 1121 information indicating the print processing status in the printer 50 included in the SOAP message from the printer 50, the monitoring thread 1121 Information is notified to the print instruction unit 113 (S118). Progressing to step S119 following step S118, the print instructing unit 113 sets the value of the job status in the job status file 132 to “completed”, according to the information notified from the monitoring thread 1121, as in step S46 of FIG. Update to “aborated” or “stopped-error” or the like.

  Thereafter, the processing described in FIG. 16 (inquiry about completion of the printing process) is executed, and when the print status acquisition method in the print request reception unit 112 of the print server 10 is called by SOAP RPC, the print request reception unit 112 The job status value of the current job is acquired from the job status file 132 of the current job, and a SOAP message including the value is transmitted to the Web server 30. Thereby, a client such as the Web application 32 can know the state of the printing process.

  As described above, in the second embodiment, by implementing the SOAP interface in the printer 50, it is possible to realize the same function as in the first embodiment while simplifying the mounting in the print server 10. ing. That is, a print request to the printer 50, an inquiry about the status of the printing process, and the like can be made by calling a method, and the burden on the developer can be reduced.

  In the above-described embodiment, an example in which document data to be printed is acquired from the document management server 20 has been described. However, document data stored in the file system of the terminal 40 may be printed.

  FIG. 22 is a sequence diagram for explaining processing when document data stored in a terminal is to be printed. In the following, a form in which document data stored in the terminal 40 is a print target is referred to as “PUSH type”.

  In step S211, when the user issues a print instruction on the PUSH type setting page substantially the same as the setting page 420 (FIG. 8) displayed on the Web browser 41, the Web browser 41 sets the print parameter information and the print target. A print request accompanied by document data (target data) is transmitted to the Web server 30. Here, the push type setting page may be any page in which a user interface for selecting document data stored in the file system of the terminal 40 is further added to the setting page 420.

  The Web application 32 of the Web server 30 prints the target data by transmitting a SOAP message for calling the PUSH type print method of the print request reception unit 112 of the print server 10 by the SOAP RPC to the print server 10. Is requested to the print server 10 (S212).

  FIG. 23 is a diagram illustrating an example of a SOAP message when calling a push type print method. In the SOAP message 760 of FIG. 23, the tag name “PrintPushDocument” of the tag 761 is the method name of the PUSH type print method. The description 762 is argument information. The SOAP message 710 in FIG. 9 includes an argument (description 763) in which the job name is specified, an argument (description 764) in which the name of the terminal 40 that is the caller of the PUSH type print method is specified, and the like. Similarly, in the case of the PUSH type, there is no argument for designating a ticket because it is not necessary to acquire document data from the document management server 10. Instead, the encoded target data is added to the portion indicated by reference numeral 765.

  In step S213 following step S212, the print request reception unit 112 stores the target data included in the received SOAP message 760 in a predetermined folder, and requests the print instruction unit 113 to print the target data. (S214).

  In step S215 and subsequent steps, the same processing as that in step S14 and subsequent steps in FIG. 4 is executed. However, in the case of the PUSH type in FIG. 22, it is not necessary to execute the target data acquisition process (S22 to S27) from the document management server 10 described in FIG. 4, and the target data stored in step S213 is the print process. It is treated as a target.

  FIG. 24 shows the SOAP message transmitted to the Web application 32 in step S219 as return information of the push type print method. As shown in FIG. 24, the SOAP message 770 as the return information of the push type print method is almost the same as the SOAP message 720 shown in FIG. 12, and the job ID “001” is shown in the description 771. .

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

It is a figure which shows the structural example of the printing system in embodiment of this invention. It is a figure which shows the hardware structural example of the print server in embodiment of this invention. It is a figure which shows the function structural example of the print service in the print server of 1st embodiment. It is a sequence diagram for demonstrating the printing process of the document data in the printing system of 1st embodiment. It is a sequence diagram for demonstrating the printing process of the document data in the printing system of 1st embodiment. It is a sequence diagram for demonstrating the printing process of the document data in the printing system of 1st embodiment. It is a figure which shows the example of a display of a document list page. It is a figure which shows the example of a display of a setting page. It is a figure which shows the example of a SOAP message when calling a printing method. 6 is a diagram illustrating a configuration example of job information in a print job queue. FIG. FIG. 6 is a diagram illustrating a configuration example of status information of a print job. It is a figure which shows the SOAP message containing the return information of a printing method. It is a figure which shows the example of the status information in the job status file in which the job status was updated to processing. It is a figure which shows the example of the status information in the job status file in which the job status was updated to executing. It is a figure which shows the example of the status information in the job status file with which the job status was updated to completed. FIG. 6 is a sequence diagram for explaining processing when there is an inquiry as to whether or not printing processing has been completed in a printer. It is a figure which shows the example of a SOAP message when calling a printing status acquisition method. It is a figure which shows the SOAP message containing the return information of a printing status acquisition method. It is a figure which shows the SOAP message containing the return information of the printing status acquisition method when the job status is stopped-error. It is a figure which shows the function structural example of the printing service and printer in the print server of 2nd embodiment. It is a sequence diagram for demonstrating the printing process of the document data in the printing system of 2nd embodiment. FIG. 6 is a sequence diagram for explaining processing when document data stored in a terminal is to be printed. It is a figure which shows the example of a SOAP message when calling the printing method for PUSH type | molds. It is a figure which shows the SOAP message containing the return information of the printing method for PUSH type | molds.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Print system 10 Print server 11 Print service 20 Document management server 21 SOAP listener 22 Document management means 23 Document management DB
24 Document management service 30 Web server 31 httpd
32 Web application 33 SOAP proxy 40 Terminal 41 Web browser 50 Printer 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 Arithmetic processing device 105 Interface device 111 SOAP listener 112 Print request reception means 113 Print instruction means 114 Document application 115 Printer Driver 116 Spooler 117 Port program 118 Printer control means 119 Event monitoring means 120 Asynchronous management means 121 Document management connection means 122 SOAP proxy 132 Job status file B bus

Claims (22)

A print processing apparatus that causes a predetermined image processing apparatus to print document data specified in a request in response to a request from a client apparatus connected via a network,
Print status acquisition means for acquiring print status information indicating the status of the print processing of the document data in the image processing device from the predetermined image processing device that has requested the printing of the document data;
A printing processing apparatus comprising: a printing status information holding unit that holds the printing status information acquired by the printing status acquisition unit. In response to a request from the client apparatus, information indicating whether or not a printing process in the predetermined image processing apparatus is completed based on the printing state information held in the printing state information holding unit is the client apparatus The print processing apparatus according to claim 1, further comprising print information providing means for transmitting to the print information. The print information providing means indicates that the print processing is completed when the print status information indicates that the print processing has been completed normally, has been interrupted, or has been canceled. The print processing apparatus according to claim 2, wherein information is transmitted to the client apparatus. 4. The print processing apparatus according to claim 2, wherein the print information providing unit transmits the print status information to the client apparatus together with information indicating whether or not the print process is completed. When the print status information indicates that the print process is interrupted, the print information providing means further transmits information indicating the cause of the interrupt of the print process to the client device. The print processing apparatus according to claim 4. The information indicating the cause of the interruption of the printing process includes that the paper is out, that a paper jam has occurred, that the predetermined image processing apparatus is turned off, or that the toner is out. The print processing apparatus according to claim 5, wherein the print processing apparatus is information indicating a print quality. A first SOAP processing means for receiving a SOAP message transmitted from the client device;
The print processing apparatus according to claim 1, wherein the document data is printed on the predetermined image processing apparatus based on a first SOAP message received by the first SOAP processing unit. . The print information providing means sends a SOAP message including information indicating whether or not the print processing is completed based on the second SOAP message received by the first SOAP processing means to the first SOAP processing. The print processing apparatus according to claim 7, wherein the print processing apparatus transmits the message to the client apparatus. The first SOAP processing unit transmits a SOAP message including the print status information together with information indicating whether or not the printing process is completed to the client device. Print processing device. When the print status information indicates that the print process is interrupted, the first SOAP processing means sends a SOAP message further including information indicating the cause of the interrupt of the print process to the client device. The print processing apparatus according to claim 9, wherein the print processing apparatus transmits the information to the print processing apparatus. The printing status acquisition unit generates an event indicating the printing status information acquired from the image processing apparatus,
The print processing apparatus according to claim 1, wherein the print processing apparatus includes a print state information registration unit that registers the print state information in the print state information holding unit based on the event. apparatus. A SOAP message requesting transmission of the print status information to the predetermined image processing apparatus is transmitted, and a SOAP message including the print status information transmitted from the image processing apparatus as a response to the SOAP message is received. Further comprising a SOAP processing means,
The print processing apparatus according to claim 1, wherein the print status acquisition unit acquires the print status information from the image processing apparatus using the second SOAP processing unit. An image processing apparatus for executing print processing of document data transmitted from the print processing apparatus according to claim 1,
In response to a request from the print processing device, the image processing device transmits print status information indicating the status of the print processing to the print processing device. An image processing apparatus that executes print processing of predetermined document data based on a first SOAP message transmitted from the print processing apparatus according to claim 12,
An image processing apparatus that transmits a SOAP message including print status information indicating a status of the print processing to the print processing apparatus based on a second SOAP message transmitted from the print processing apparatus. A method of controlling a print processing apparatus that causes a predetermined image processing apparatus to print document data specified in a request in response to a request from a client apparatus connected via a network,
A print status acquisition procedure for acquiring print status information indicating the status of print processing of the document data in the image processing device from the predetermined image processing device that has requested printing of the document data;
A printing processing apparatus control method comprising: a printing status information storing procedure for storing the printing status information acquired in the printing status acquiring procedure in a predetermined storage area of the printing processing apparatus. In response to a request from the client device, information indicating whether or not the print processing in the predetermined image processing device is completed based on the print status information stored in the predetermined storage area is sent to the client device. 16. The method of controlling a print processing apparatus according to claim 15, further comprising a print information providing procedure to be transmitted to the print processing apparatus. The print information providing procedure indicates that the print process is completed when the print status information indicates that the print process has been normally completed, has been interrupted, or has been canceled. The method according to claim 16, wherein the information is transmitted to the client device. 18. The print processing apparatus according to claim 16, wherein the print information provision procedure transmits the print status information to the client apparatus together with information indicating whether or not the print process is completed. Control method. In the print information providing procedure, when the print status information indicates that the print process is interrupted, the print information providing procedure further transmits information indicating the cause of the interrupt of the print process to the client device. The method of controlling a print processing apparatus according to claim 18. The information indicating the cause of the interruption of the printing process includes that the paper is out, that a paper jam has occurred, that the predetermined image processing apparatus is turned off, or that the toner is out. 20. The method of controlling a print processing apparatus according to claim 19, wherein the control information is information indicating the print quality. In response to a request from a client device connected via a network, a print processing device that causes a predetermined image processing device to print document data specified in the request,
A print status acquisition procedure for acquiring print status information indicating the status of print processing of the document data in the image processing device from the predetermined image processing device that has requested printing of the document data;
A control program for a print processing apparatus for executing a print status information storage procedure for storing the print status information acquired in the print status acquisition procedure in a predetermined storage area of the print processing apparatus. In response to a request from a client device connected via a network, a print processing device that causes a predetermined image processing device to print document data specified in the request,
A print status acquisition procedure for acquiring print status information indicating the status of print processing of the document data in the image processing device from the predetermined image processing device that has requested printing of the document data;
A computer readable recording of a control program for a print processing apparatus for executing a print status information storage procedure for storing the print status information acquired in the print status acquisition procedure in a predetermined storage area of the print processing apparatus recoding media.

Images