JP2004280600A - Print management device, printing device management device, print management method, print management program, and print management system - Google Patents

Abstract

An object of the present invention is to provide a print management device, a printing device management device, a print management method, a print management program, and a print management system capable of simplifying a print instruction operation of document data or the like.
A print management apparatus that causes a printing device to print document data in response to a print request transmitted from a terminal, wherein the print condition specified in the print request is managed by the print condition management means. And a printing condition registration unit registered in the printing condition management unit based on a simple print request transmitted from the terminal and requesting printing under printing conditions registered in the printing condition management unit. The above problem is solved by providing a simple printing unit that prints the document data with reference to a printing condition.
[Selection diagram] FIG.

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a print management device, a print device management device, a print management method, a print management program, and a print management system for causing a printing device to print document data in response to a print request transmitted from a terminal.
[0002]
[Prior art]
When printing document data or the like created by an application or the like, it is common to first set printing conditions and then instruct printing. For example, when printing the document data currently being edited from word processing software installed on the terminal, selecting the print menu of the word processing software displays a dialog for setting the printing conditions. Can be set.
[0003]
Further, with the development of network technology in recent years, it is possible to instruct printing of document data stored in a document management server existing on a network through a Web page displayed on a Web browser. In such a case, the user sets print conditions on a print condition setting Web page displayed on the Web browser and gives a print instruction (for example, Patent Document 1).
[0004]
An application (word processing software or the like) for generating print data from document data by causing a server to perform print processing from a Web browser via a network may be installed only on the server side. Resource efficiency and maintenance efficiency can be improved.
[0005]
Here, various conditions such as paper size, paper direction, aggregate printing, number of copies, sort, staple, and image quality, such as paper size, must be set in accordance with recent multifunctional printing equipment. The user can print the document data in various modes according to his / her own use.
[0006]
[Patent Document 1]
JP-A-2000-10753
[0007]
[Problems to be solved by the invention]
However, in general, applications provided by a Web page displayed on a Web browser often have functional limitations due to the versatility of the Web browser. The same applies to the case where document data is printed. The printing conditions used in the past are not retained, and even when the user wants to use the same printing conditions again, the user needs to set them again.
[0008]
In particular, with the recent multi-functionality of printing apparatuses, it is possible to make detailed settings for printing conditions, and it is very inconvenient for the user to perform the same setting again even though the setting has been performed once in the past.
[0009]
The present invention has been made in view of the above points, and provides a print management device, a printing device management device, a print management method, a print management program, and a print management device capable of simplifying a print instruction operation of document data and the like. The purpose is to provide a print management system.
[0010]
[Means for Solving the Problems]
Therefore, in order to solve the above-mentioned problem, the present invention provides a print management apparatus which causes a printing device to print document data in response to a print request transmitted from a terminal. Printing condition registration means for registering the printing condition specified in the printing condition management means for managing the printing condition, and printing under the printing condition registered in the printing condition management means transmitted from the terminal. A simple printing unit that prints the document data with reference to a printing condition registered in the printing condition management unit based on the requested simple printing request.
[0011]
In such a management apparatus, it is possible to save the printing conditions used once by the user. Therefore, even when the user wants to execute printing under the same printing conditions next time, the user does not need to set the printing conditions again, and can easily perform the print instruction operation.
[0012]
In order to solve the above problems, the present invention provides a print management method in the print management device, a program for causing a computer to perform the print management method, a print management system configured by the print management device, and A printing device management device that causes a printing device to execute document data printing in response to a print instruction may be used.
[0013]
BEST MODE FOR CARRYING OUT THE INVENTION
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 print management system according to an embodiment of the present invention. In the print management system 1 of FIG. 1, a print management server 10, a terminal 20, a printer server 30, and a document management server 40 are connected via a network 50.
[0014]
The terminal 20 is a terminal on which a Web browser is installed, and corresponds to, for example, a PC (Personal Computer), a PDA (Personal Digital Assistants), and a mobile phone. In FIG. 1, although only one terminal 20 is described, the purpose is not limited to one terminal, and a plurality of terminals 20 can be connected to the network 50.
[0015]
The printer server 30 manages the printers 31, 32, 33, and 34 connected via a network such as a LAN, and publishes print processing for each printer on the network 50 as a Web service. A computer that functions as a printing device management device. The function of the printer server 30 can be called by RPC of SOAP. For example, the printer server 30 discloses a “print instruction method” on the network 50 for receiving a print instruction for the printer 31 or the like.
[0016]
The document management server 40 is a computer that discloses a document management service related to document data stored in a document DB (Data Base) 41 on the network 50 as a Web service. The function of the document management server 40 can be called by RPC of SOAP. For example, the document management server 40 discloses a “document list acquisition method” for acquiring list information of document data stored in an arbitrary folder of the document DB 41 on the network 50. In the following, a server such as the printer server 30 and the document management server 40 that can call its function by SOAP RPC is referred to as a “SOAP server”.
[0017]
The print management server 10 is a computer that controls a process for causing the printer 31 or the like to print document data managed in the document DB 41 in response to a request from the terminal 20 via the printer server 30.
[0018]
FIG. 2 is a diagram illustrating a hardware configuration example of the print management server according to the embodiment of the present invention. The print management server 10 includes a CPU 11, a ROM 12, a RAM 13, an auxiliary storage device 14, a network interface (I / F) 15, a drive device 16, and the like.
[0019]
The CPU 11 is a control unit that controls the entire print management server 10. The CPU 11 executes various control programs and application programs stored in the ROM 12 and the auxiliary storage device 14 to control the apparatus, control communication, acquire and edit data, and the like. Is performed.
[0020]
The ROM 12 is storage means for mainly storing a control program of the apparatus. The RAM 13 is a storage unit used for a work memory of the CPU 11 and temporary storage of data. The auxiliary storage device 14 is storage means for storing various application programs and data, and may store files and the like described later as necessary.
[0021]
The network I / F 15 is an interface for connecting the print management server 10 to the network 50. The drive device 16 is a device for reading a recording medium 17 such as a CD-ROM on which a program for executing a process which is a feature of the present invention is recorded.
[0022]
Although an operation unit and a display unit are not shown in FIG. 2, an operation unit such as a keyboard and a mouse, and a display unit such as a liquid crystal display or a cathode ray tube (CRT) are provided to receive input from a user and display operation results. May be performed.
[0023]
Next, a functional configuration of the print management server 10 will be described. FIG. 3 is a diagram illustrating a functional configuration example of the print management server according to the embodiment of the present invention. 3, the print management server 10 includes a Web server program 101, a document list page module 102, a print condition setting page module 103, a print condition storage module 104, a print execution module 105, a printer information file 111, a print condition management file 112, and the like. Consists of
[0024]
The Web server program 101 is equivalent to a program generally called HTTPd (HTTP daemon), and is for causing the print management server 10 to function as a Web server. Therefore, the Web server program 101 receives a request (HTTP request) from the terminal 20 and calls various Web applications such as the document list page module 102 corresponding to the request from the terminal 20. Further, the Web server program 101 transmits to the terminal 20 a Web page output from the called Web application.
[0025]
The document list page module 102 is a Web application for providing the terminal 20 with a Web page (hereinafter, referred to as a “document list page”) displaying a list of document data managed by the document management server 40. When called from the Web server program 101 based on a request from the terminal 20, the document list page module 102 acquires document data list information from the document management server 40, and based on the acquired document data list information, Generate a page.
[0026]
The print condition setting page module 103 is a Web application for providing the terminal 20 with a Web page for setting print conditions when printing document data. When called from the web server program 101 based on a request from the terminal 20, the print condition setting page module 103 generates a web page for setting print conditions. Here, the printing condition refers to information for specifying the mode of the printing process of the document data, and includes the number of copies, paper size, printing direction, whether to sort, whether to use the staple function, and whether to use the punch function. It has information such as whether or not to use, whether to perform double-sided printing, and whether to perform aggregate printing.
[0027]
The print condition storage module 104 is a Web application for executing processing for storing print conditions in the print condition management file 112 when the terminal 20 requests storage of the print conditions used for printing.
[0028]
The print execution module 105 is a Web application for executing printing of document data based on transmission print conditions from the terminal 20 or with reference to print conditions registered in the print condition management file 112. If it is not possible to print from the terminal 20 to the printer designated as the print destination, the print execution module 105 provides the terminal 20 with a list of printers that can perform printing. That is, the print execution module 105 determines a printer that can correspond to the requested printing condition based on the printer information file 111, and displays a list of printers that are determined to be capable of meeting the requested printing condition. Generate
[0029]
The printer information file 111 is a file that functions as a printing function identification information management unit. That is, the printer information file 111 manages information for identifying the printing function of each of the plurality of printers managed by the printer management server 30. Here, the printing function refers to a function for processing printing of document data in a mode specified by printing conditions, and includes a paper size designation function, a paper direction designation function, a sort function, a staple function, a punch function, and a two-sided printing function. , And the aggregate printing function.
[0030]
The printing condition management file 112 is a file in which printing conditions specified at the time of printing are stored for each user.
[0031]
Hereinafter, the processing procedure of the print management system 1 of FIG. 1 will be described mainly on the print management server 10 of FIG. FIG. 4 is a sequence diagram for explaining processing of the print management system at the time of a normal print request.
[0032]
In step S11, when the user of the terminal 20 instructs the printer 31 to print the document data stored in the document DB 41 on the Web browser 21 under predetermined printing conditions, the terminal 20 sets the printing conditions and the print target. A print request (HTTP (HyperText Transfer Protocol) request) for the document data is transmitted to the print management server 10 together with a file name of the document data (hereinafter, referred to as “print information”).
[0033]
Selection of document data to be printed, selection of a printer as a printing destination, setting of printing conditions, and the like can be performed using the Web pages shown in FIGS. 5, 6, and 7.
[0034]
FIG. 5 is a diagram illustrating a display example of a document list page. The document list page 210 can be displayed on the web browser 21 by inputting the URL of the document list page 210 into the web browser 21. That is, when the Web browser 21 transmits a transmission request for the document list page 210 to the print management server 10 based on the input of the URL, the document list page module 102 of the print management server 10 Get information. The document list page module 102 generates a Web page (document list page 210) on which the acquired document data list information is described. The document list page 210 generated by the document list page module 102 is transmitted to the terminal 20 by the Web server program 101 and displayed on the Web browser 21.
[0035]
In the document list page 210, each document data is displayed as a thumbnail in an area 211. Here, if a rectangular area in which one piece of document data is displayed is called a “cell”, each cell has a check button for selecting document data, and a name (document name) of the document data. , And an icon display area. For example, for a cell in which document data having a document name of “document 3” is displayed, there is a check button 213, a document name display area 214, and an icon display area 215.
[0036]
When the user checks a check button corresponding to the document data to be printed (in FIG. 5, check documents 1, 2, and 3) and clicks a print button 212, the Web browser 21 prints the print conditions. A transmission request for a Web page (hereinafter, referred to as “printing basic condition setting page”) for setting the basic information (hereinafter, referred to as “printing basic condition”) is transmitted to the print management server 10. As a response to the transmission request of the basic printing condition setting page from the web browser 21, the basic printing condition setting page generated by the printing condition setting page module 103 is transmitted from the print management server 10 to the terminal 20 and displayed on the web browser 21. .
[0037]
FIG. 6 is a diagram illustrating a display example of a printing basic condition setting page. The printing basic condition setting page 220 is roughly divided into a printing target document list display area 221 and a basic setting area 222. In the print target document list display area 221, a list of the document names of the document data selected as the print targets on the document list page 210 is displayed.
[0038]
The basic setting area 222 is an area for setting basic printing conditions, and can set a printer name of a printing destination, the number of copies, a printing range, a document size, a printing direction, an image image, and the like. . As for the setting of the image image, it is possible to select a print start position and whether or not to reduce the image so as to fit on the printing paper. In FIG. 6, the printing destination printer is "Printer 31", the number of copies is one, the printing range is all sections, the document size is A4, the printing direction is vertical, the printing start position is centering, and the printing is performed so that it fits on the paper. An example in which reduction is set is shown.
[0039]
An OK button 223 on the printing basic condition setting page 220 is a button that is clicked when printing is performed. That is, when the user clicks the OK button 223, the process of step S11 is executed.
[0040]
The detailed setting tab 224 is clicked when displaying a Web page (hereinafter, referred to as “printing detailed condition setting page”) for setting detailed information of the printing condition (hereinafter, referred to as “printing detailed condition”). Tab. That is, when the user clicks the detailed setting tab 224, the Web browser 21 transmits a request for transmitting a detailed print condition setting page to the print management server 10. As a response to the transmission request of the printing detailed condition setting page from the web browser 21, the printing detailed condition setting page generated by the printing condition setting page module 103 is transmitted from the print management server 10 to the terminal 20, and displayed on the web browser 21. .
[0041]
FIG. 7 is a diagram illustrating a display example of a print detailed condition setting page. The detailed print condition setting page 230 is roughly composed of a print target document list display area 231 and a detailed setting area 232. In the print target document list display area 231, a list of the document names of the document data selected as the print target on the document list page 210 is displayed.
[0042]
The detailed setting area 232 is an area for setting detailed printing conditions, and can set functions such as sorting, stapling, punching, double-sided printing, and consolidated printing. FIG. 7 shows an example in which sorting is performed, staples are not set, punches are set at two places on the left side, double-sided printing is set, and two pages are combined into one page.
[0043]
The basic setting tab 234 is a tab that is clicked when the printing basic condition setting page 220 is displayed. The OK button 233 is a button that is clicked when printing is performed. That is, when the user clicks the OK button 233, the process of step S11 is executed.
[0044]
In the description below, it is assumed that the printing conditions set on the printing basic condition setting page 220 in FIG. 6 and the printing detailed condition setting page 230 in FIG. 7 have been transmitted in step S11.
[0045]
Proceeding to step S12 following step S11, the print execution module 105 of the print management server 10 requests the printer server 30 to print the document data by calling the print execution method of the printer server 30 with the print information as an argument. I do.
[0046]
Proceeding to step S13 following step S12, when the printer server 30 requests the document management server 40 to send document data to be printed by calling the document acquisition method of the document management server 40 by SOAP, the document The management server 40 retrieves the requested document data from the document DB 41 and sends it to the printer server 30 (S14).
[0047]
Proceeding to step S15 following step S14, the printer server 30 transmits a print request for the document data acquired from the document management server 40 to the printer 31 together with print conditions.
[0048]
If the printer 32 is operating normally, the printer 32 notifies the printer server 30 of a response indicating that the print request has been normally received (S16), and further informs that the print processing has been executed normally. Is transmitted from the printer server 30 to the print management server 10 (S17). At the same time, the printer 31 prints the document data according to the printing conditions requested from the terminal 20.
[0049]
Proceeding to step S18 following step S17, the print execution module 105 asks the user whether or not the print conditions set this time should be stored in the print management server 10 (hereinafter referred to as a “print condition storage page”). "). That is, it is possible to store the printing conditions in the print management server 10. As a result, the user can use the printing conditions registered at the time of next printing and save the trouble of setting the printing conditions again on the printing basic condition setting page 220 and the printing detailed condition setting page 230. It becomes possible.
[0050]
Proceeding to step S19 following step S18, when the Web server program 101 transmits the print condition storage page to the terminal 20, the print condition storage page is displayed on the Web browser 21 of the terminal 20.
[0051]
FIG. 8 is a diagram illustrating a display example of a print condition storage page. The print condition storage page 250 includes a message 251, a print condition display area 252, a check button 253, a print condition name input area 254, an OK button 255, and the like. The message 250 notifies that the print request has been normally processed, and asks whether to register the current print condition.
[0052]
The print condition display area 252 is an area where the current print condition is displayed. The check button 253 is a check button that is checked when saving the current printing conditions. The print condition name input area 254 is an area that can be input when the check button 253 is checked, and is a name for uniquely identifying the current print condition displayed in the print condition display area 252 (print condition name). This is the area for inputting
[0053]
When the user checks the check button 253, inputs a print condition name in the print condition name input area 254, and clicks the OK button 255, the process proceeds to step S20, and the terminal 20 transmits the current print condition to the print management server 10. Send a save request. In step S21 following step S20, the print condition storage module 104 in the print management server 10 is called from the Web server program 10, and stores the current print conditions in the print condition management file 112.
[0054]
FIG. 9 is a diagram illustrating an example of the print condition management file. In the description 1121 enclosed by the <EasyPrint> tags of the printing condition management file 112 in FIG. 9, the values of the respective attributes constituting one printing condition are registered. For example, an element enclosed by <PRINTER> tags indicates a printer name of a printing destination. The element enclosed by the <APLPAGESIZE> tag indicates the paper size. Elements enclosed by <COPIES> tags indicate the number of copies to be printed. The element enclosed by the <APLPAGELAYOUT> tag indicates the paper direction, where "0" indicates the horizontal direction, and "1" indicates the vertical direction. An element surrounded by a <POS> tag indicates a print start position, where "0" indicates centering, and "1" indicates an upper left reference. Hereinafter, settings for sort processing, stapling processing, punch processing, double-sided printing, and consolidated printing are registered.
[0055]
When a plurality of printing conditions are registered, the elements enclosed by <EasyPrint> are registered in the printing condition management file 112 correspondingly.
[0056]
The print condition management file 112 uses the user name of the terminal 20 as its file name. That is, the printing conditions are managed for each user. Therefore, in step S21, the printing condition storage module 104 registers the current printing condition in the printing condition file 112 corresponding to the user of the terminal 20.
[0057]
Further, the print condition management file 112 can store a plurality of print conditions for the same printer. In that case, the setting content including the same parameters as the description 1121 is registered in the form shown in the description 1122.
[0058]
Proceeding to step S22 following step S21, the print condition storage module 104 transmits to the terminal 20 a Web page indicating that the print conditions have been registered normally (hereinafter, referred to as a “print condition storage notification page”). The print condition saving notification page is displayed on the Web browser 21, and the user can confirm that the current print condition has been normally saved.
[0059]
Next, the processing of the print management system 1 when the user newly executes the printing of the document data using the printing conditions stored this time will be described. In the following description, printing using the printing conditions already stored in the printing condition management file 112 is referred to as “simple printing”.
[0060]
When the user displays the document list page 210 again on the Web browser 21 after saving the printing conditions, the document list page 210 is newly displayed with a button for executing simple printing.
[0061]
FIG. 10 is a diagram illustrating a display example of a document list page to which a button for simple printing is added. The button 216 on the document list page 210 in FIG. 10 is a button for simple printing, and the printing condition name “simple printing 1” is displayed as a label. This is because, when the document list page module 102 generates the document list page 210, the print conditions are stored with reference to the print condition file 112 corresponding to the user of the terminal 20 that has requested the document list page 210. Is realized by performing a process of adding the button 216 to the document list page 210.
[0062]
Since the printing conditions are managed separately for each user, the document list page module 102 can arrange a button for simple printing only for the user who has requested the document list page 210 on the document list page 210. It is possible to provide personalized services for each user.
[0063]
When the user selects the document data to be printed on the document list page 210 and clicks the button 216, the process for executing the simple printing starts. FIG. 11 is a sequence diagram for explaining processing of the print management system when performing simple printing.
[0064]
In step S31, the terminal 20 transmits a simple print request (simple print request) to the print management server 20 based on the user clicking the button 216. Proceeding to step S32 following step S31, the print execution module 105 of the print management server 10 acquires the print condition corresponding to the button 216 from the print condition management file 112 corresponding to the user of the terminal 20, and stores the acquired print condition. A Web page to be displayed (hereinafter referred to as a “print condition confirmation page”) is generated.
[0065]
Proceeding to step S33 following step S32, when the Web server program 101 transmits the print condition confirmation page to the terminal 20, the print condition confirmation page is displayed on the Web browser 21 of the terminal 20.
[0066]
FIG. 12 is a diagram illustrating a display example of a print condition confirmation page. The print condition confirmation page 260 is a page for allowing the user to confirm whether there is any error in the recognition of the print condition, and the print condition corresponding to the requested simple print (“simple print 1”) is displayed. . However, in the print target document list display area 261, the document name of the document data selected this time on the document list page 210 is displayed.
[0067]
When the user confirms that there are no errors in the print conditions and clicks the OK button 261, the terminal 20 transmits a print request for document data under the print conditions displayed on the print condition confirmation page 260 to the print management server 10. (S34).
[0068]
After step S34, the process proceeds to step S35, after which the same processing as in normal printing is performed. That is, when the print execution module 105 of the print management server 10 calls the print execution method of the printer server 30 (S35), the printer server 30 acquires document data from the document management server 40 (S36, S37). Subsequently, the printer server 30 issues a print request to the printer 31 (S38), and upon receiving a notification from the printer 31 that the print request has been processed normally (S39), prints a response indicating that the print request has been processed normally. This is transmitted to the server 10 (S40). The print execution module 105 generates a Web page notifying that the print request has been normally processed (hereinafter, referred to as a “normal processing notification page”), and the Web server program 101 transmits the normal processing notification page to the terminal 20. (S41). The normal processing notification page is displayed on the Web browser 21, and the user can confirm that the print request has been normally processed.
[0069]
Next, as in the case of FIG. 11, when the user of the terminal 20 attempts to simply print the document data stored in the document DB 41 of the document management server 40 on the printer 31, some trouble has occurred in the printer 31. For this reason, an example in which another printer performs proxy printing will be described. FIG. 13 and FIG. 14 are sequence diagrams for explaining processing of the print management system when printing cannot be performed on the printer at the printing destination.
[0070]
Steps S51 to S58 are exactly the same as steps S31 to S38 in FIG. That is, based on the simple print request (S51) from the terminal 20, a print request is made to the printer 31 (S58).
[0071]
Proceeding to step S59 following step S58, the printer 31 notifies the printer server 30 of error information indicating that printing is not possible because some failure has occurred as described above.
[0072]
When the printer 31 is not activated, or when there is an abnormality in the communication between the printer server 30 and the printer 31, the printer 31 does not transmit the error information. The server 30 detects in step S59 that printing to the printer 31 is not possible, and transmits error information to the effect that printing to the printer 31 has failed to the print management server 10 (S60).
[0073]
Proceeding to step S61 following step S60, the print execution module 105 requests the printer server 30 to transmit list information of printers under the printer server 30 (hereinafter, referred to as "printer list information"). Then, the printer list information is received (S62).
[0074]
Proceeding to step S63 following step S62, the print execution module 105 newly compares the printer list information managed by the print management server 10 with the printer list information received from the printer server 30 to newly print the printer. It is determined whether there is a printer under the control of the server 30.
[0075]
That is, the print management server 10 independently manages list information of printers under the control of the printer server 30. The printer server 30 also manages list information of printers under its control. The printer list information in the printer server 30 is updated by the administrator when a new printer is added under the printer server 30 or when a printer under the control of the printer server is removed. However, the printer list information in the print management server 10 is not updated at the timing when the printers under the print server 30 change, so that the printer list information of the print management server 10 and the printer list information of the printer server 30 are not updated. Differences may occur. Thus, the print execution module 105 executes a process for detecting such a difference in step S63. Here, it is assumed that the printer 32 has been newly added to the printer server 30. Accordingly, in step S63, the print execution module 105 detects that the printer 32 is newly registered under the printer server 30 because the printer 32 is not registered only in the printer list information of the print management server 10.
[0076]
Proceeding to step S64 of FIG. 14 subsequent to step S63, the print execution module 105 calls the printer information acquisition method of the printer server 30 by SOAP, thereby obtaining a list of print functions of the printer 32 (hereinafter, “printer information”). Is transmitted to the printer server 30. The printer server 30 inquires the printer 32 of printer information (S65, S66), and transmits the printer information received from the printer 32 to the print management server 10 (S67).
[0077]
Proceeding to step S68 following step S67, the print execution module 105 merges the printer information of the printer 32 into the printer information file 111.
[0078]
FIG. 15 is a diagram illustrating an example of the printer information file. As shown in FIG. 15, in the printer information file 111, information for identifying a printing function of the printer is registered in an XML format for each printer. That is, a description 1111 enclosed by a printer name tag (<Printer 31>) of the printer 31 indicates printer information of the printer 31. Hereinafter, a description 1112, a description 1113, and a description 1114 indicate a printer 32, a printer 1 33, printer information for the printer 34.
[0079]
Each description is composed of a set of elements for identifying each printing function. If the value of each element is “「 ”, it indicates that the printer has the printing function. Indicates that the printing function is not provided.
[0080]
An element enclosed by <APLPAGESIZE> tags (hereinafter, referred to as an “APLPAGESIZE element”) means a paper size designation function. The APPLAGELAYOUT element, the COLLATE element, the STAPLE element, the PUNCH element, the DUPLEX element, and the NUP element mean a paper direction designation function, a sort function, a staple function, a punch function, a double-sided printing function, and an integrated printing function, respectively.
[0081]
From FIG. 15, it can be seen that, for example, the printer 31 and the printer 32 have all the functions described above. Further, it can be seen that the printer 33 does not have the staple function and the duplex printing function.
[0082]
Some of the printing functions require a parameter to be specified in order to use the printing function. For example, when using the paper size specification function, the user specifies the paper size to be printed. Therefore, if there is a difference in the paper size that can be handled by each printer, it is necessary to manage the printer information so that the paper size that can be handled by each printer can be identified.
[0083]
FIG. 16 is a diagram illustrating an example of a printer information file when parameter information of a printing function is managed. FIG. 16 shows an example in which the APLPAGESIZE element in FIG. 15 is extracted and parameter information is registered there.
[0084]
In FIG. 16, parameter information is composed of descriptions 1131 to 1136, and each description is composed of an element (element element) surrounded by one <element> tag. The <element> tag is
<Element name = “element name” type = “element type”>
It is described in the format.
[0085]
Here, the “element name” is a name for identifying the meaning of the element. “Element type” indicates the data type of the element value. Element names include types such as propVal, rangeType, propValMin, propValMax, propValStep, and propValEnum.
[0086]
The default value of the parameter is registered in the element whose element name is propVal. Since the element name of the description 1131 is propVal, the description 1131 indicates the minimum value of the parameter.
[0087]
In the element whose element name is rangeType, the category of the parameter value range is registered. Since the element name of the description 1132 is rangeType, the description 1132 indicates the range of the parameter value range.
[0088]
The element with the element name propValMin registers the minimum value of the parameter. Since the element name of the description 1133 is propValMin, the description 1133 indicates the minimum value of the parameter.
[0089]
The maximum value of the parameter is registered in the element whose element name is propValMax. Since the element name of the description 1133 is propValMax, the description 1133 indicates the maximum value of the parameter.
[0090]
In the element whose element name is propValStep, a step value indicating an interval when the parameter takes a value of an equal interval is registered. Since the element name of the description 1135 is propValStep, the description 1135 indicates the step value of the parameter.
[0091]
In the element whose element name is propValEnum, possible values of the parameter are listed. Since the element name of the description 1136 is propValEnum, the possible values of the parameters are listed in the description 1136.
[0092]
Here, rangeType will be described in more detail. As described above, rangeType means a range of a parameter value range, and the value may be RDH_PROPPAGE_ONE, RDH_PROPPAGE_MIN_MAX, RDH_PROPRANGE_MIN_MAX_STEP, RDH_PROPPAGE_ENUM, or the like.
[0093]
RDH_PROPPAGE_ONE indicates that the parameter takes only the value specified as the default value (description 1131). Therefore, when rangeType is RDH_PROPPAGE_ONE, other descriptions (descriptions 1133 to 1136) are ignored.
[0094]
RDH_PROPPAGE_MIN_MAX indicates that the parameter takes a value within the range specified by the minimum value (description 1133) and the maximum value (description 1134). In this case, the default value is the value of the description 1131, and the other descriptions (description 1135, description 1136) are ignored.
[0095]
RDH_PROPRANGE_MIN_MAX_STEP indicates that the parameter takes an evenly-spaced value in steps of a step value in a range between a minimum value (description 1133) and a maximum value (description 1134). In this case, the default value is the value of the description 1131, and the other description (description 1136) is ignored.
[0096]
RDH_PROPPAGE_ENUM indicates that the parameter takes the value listed in description 1136. In this case, the default value is the value of the description 1131, and the other descriptions (descriptions 1133 to 1135) are ignored.
[0097]
Accordingly, in FIG. 16, the value of rangeType is RDH_PROPPAGE_ENUM, and the paper sizes that can be specified for the paper size function (APLPAGESIZE) are “A3, A4, A5, A6, B4, B5, B6” listed in the description 1136. , And the description 1131 indicates that the default value is “A4”.
Note that parameter information of a printing function other than the paper size specification function may be managed in the same format as in FIG.
[0098]
Proceeding to step S69 following step S68, the print execution module 105 determines, with reference to the printer information file 111, a printer that can respond to the initially requested printing detailed conditions. The printing detailed conditions (simple printing 1) requested at the outset are those in which sorting processing, punching processing, and aggregate printing are specified. The printers that can correspond to these detailed printing conditions other than the printer 31 are the printers 32 and 33 from the printer information file 111. Therefore, the print execution module 105 can perform the proxy printing of the printers 32 and 33. The printer is determined as a printer (hereinafter, referred to as a “proxy printer”).
[0099]
Proceeding to step S70 following step S69, the print execution module 105 generates a Web page (hereinafter, referred to as a "proxy print page") for inquiring whether or not a proxy printer can perform proxy printing. Proceeding to step S71 following step S70, when the Web server program 101 transmits the proxy print page to the terminal 20, the proxy print page is displayed on the Web browser 21 of the terminal 20.
[0100]
FIG. 17 is a diagram illustrating a display example of the proxy print page. The proxy print page 240 includes a message 241, a check button 242, a check button 243, a check button 244, a combo box 245, an OK button 246, and the like. The message 241 indicates that printing cannot be performed because the printer 31 has an error. The check button 242 is a check button that is checked when proxy printing is performed. The check button 243 is a check button for checking when the printer 31 is forcibly executed printing. That is, when the check button 243 is checked and the OK button 246 is clicked, a print instruction to the printer 31 is spooled, and the document data is printed on the printer 31 after the printer 31 recovers. The check button 244 is a check button for checking when printing is stopped. That is, when the check button 244 is checked and the OK button 246 is clicked, the printing process is stopped.
[0101]
The combo box 245 is a combo box that can be operated when the check button 242 is checked, and displays a list of substitute printers. FIG. 17 shows an example when the combo box 245 is dropped down.
[0102]
The user can confirm from the proxy printing page 240 that the initial print request has failed and a list of proxy-capable printers.
[0103]
When the user checks the check button 242 to perform proxy printing, selects the printer 32 as a proxy printer in the combo box 245, and clicks the OK button 246, the process proceeds to step S72. Request for proxy printing (request for proxy printing).
[0104]
Proceeding to step S73 following step S72, the print execution module 105 calls the print execution method of the printer server 30 by SOAP using the printer 32 as a print destination printer and other print conditions as arguments of the same print conditions as at the beginning. This requests the printer server 30 to print the document data.
[0105]
Proceeding to step S74 following step S73, the printer server 30 transmits a document data print request to the printer 32 together with the document data and the printing conditions.
[0106]
Upon receiving a notification from the printer 31 that processing has been normally performed (S75), a response indicating that the print request has been processed normally is transmitted to the print management server 10 (S76). The print execution module 105 generates a normal processing notification page for notifying that the print request has been normally processed, and the Web server program 101 transmits the normal processing notification page to the terminal 20 (S77). The normal processing notification page is displayed on the Web browser 21, and the user can confirm that the print request has been normally processed.
[0107]
As described above, according to the print management system 1 and the print management server 10 in the present embodiment, it is possible to save the print conditions once used by the user. Therefore, even when the user wants to execute printing under the same printing conditions next time, the user does not need to set the printing conditions again, and can easily perform the print instruction operation.
[0108]
In addition, a printer (replaceable printer) that can correspond to the printing conditions initially set by the user is automatically determined, and a substitute print page 240 displaying a list of substitute printers is transmitted to the terminal 20. Can print on behalf of the printer under the initially set printing conditions.
[0109]
Further, when the proxy printing is requested, the initial printing conditions are carried over to the proxy printing process as it is, so that the user does not need to set the printing conditions on the proxy printing page 240 again. Therefore, the user can easily give an instruction for proxy printing.
[0110]
Since the print condition setting file 112 is stored for each user as described above, the storage capacity required for storing the print condition setting file 112 increases as the number of users accessing the print management server 10 increases. Become. In particular, the print management server 10 may include not only processing specialized for printing, but also various business applications and the like, like a general Web server. The pressure on storage capacity becomes more severe. Therefore, an example in which the print management file 112 is managed by a server (print condition management server) separate from the print management server 112 in order to deal with such a problem will be described.
[0111]
FIG. 18 is a diagram for explaining processing for simple printing when the printing condition management server manages the printing condition management file. The flow of processing from step S81 to step S98 in FIG. 18 is basically the same as the flow of processing from step S20 to S22 in FIG. 4 and steps S31 to S41 in FIG. The process of storing the print conditions in the print condition storage file 112 (S18 in FIG. 4) is different from the process of the print execution module 105 acquiring the print conditions stored in the print condition management file 112 (S32 in FIG. 11). .
[0112]
That is, the process corresponding to step S18 in FIG. 4 is the process from steps S82 to S84 in FIG. In step S82, when the print condition saving module 104 sends a print condition save request to the print condition management server 60, the print condition management server 60 saves the print conditions in the print condition management file 112 of the print condition management server 60. (S83), and sends a message to the print management server 10 that the data has been saved normally (S84).
[0113]
The processing corresponding to step S32 in FIG. 11 is the processing from steps S87 to S89 in FIG. In step S87, when the print execution module 105 specifies a print condition name and sends a print condition transmission request corresponding to the print condition name to the print condition management server 60, the print condition management server 60 The print condition corresponding to the print condition name is acquired (S88), and the acquired print condition is transmitted to the print management server 10.
[0114]
In the present embodiment, as described above, the print management server 10, the printer server 30, and the document management server 40 are configured by different computers. Such a system form is effective, for example, in that processing can be distributed to the respective computers and the load on one computer can be reduced, so that deterioration of the response to the terminal 20 can be avoided. However, when each computer cannot be prepared due to cost or the like, the functions of the above three computers may be mounted on one computer. The effect of the present invention can be similarly obtained in such a system form.
[0115]
Although the preferred embodiments of the present invention have been described in detail, the present invention is not limited to the specific embodiments, and various modifications may be made within the scope of the present invention described in the appended claims.・ Change is possible.
[0116]
【The invention's effect】
As described above, according to the present invention, it is possible to simplify a print instruction operation for document data or the like.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a configuration example of a print management system according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating an example of a hardware configuration of a print management server according to the embodiment of the present invention.
FIG. 3 is a diagram illustrating an example of a functional configuration of a print management server according to the embodiment of the present invention.
FIG. 4 is a sequence diagram for explaining processing of the print management system at the time of a normal print request.
FIG. 5 is a diagram illustrating a display example of a document list page.
FIG. 6 is a diagram illustrating a display example of a printing basic condition setting page.
FIG. 7 is a view showing a display example of a printing detailed condition setting page.
FIG. 8 is a diagram illustrating a display example of a print condition storage page.
FIG. 9 illustrates an example of a print condition management file.
FIG. 10 is a diagram illustrating a display example of a document list page to which a button for simple printing is added.
FIG. 11 is a sequence diagram illustrating processing of the print management system when performing simple printing.
FIG. 12 illustrates a display example of a print condition confirmation page.
FIG. 13 is a sequence diagram for explaining processing of the print management system when printing cannot be performed on a printer at the printing destination;
FIG. 14 is a sequence diagram for explaining processing of the print management system when printing cannot be performed on a printer at the printing destination;
FIG. 15 is a diagram illustrating an example of a printer information file.
FIG. 16 is a diagram illustrating an example of a printer information file when parameter information of a printing function is managed.
FIG. 17 is a diagram illustrating a display example of a proxy print page.
FIG. 18 is a diagram for describing processing for simple printing when the printing condition management server manages a printing condition management file.
[Explanation of symbols]
10 print management server
11 CPU
12 ROM
13 RAM
14 Auxiliary storage device
15 Network I / F
16 Drive device
17 Recording medium
20 terminals
21 Web Browser
30 Printer server
31, 32, 33, 34 Printer
40 Document Management Server
41 Document DB
50 Network
101 Web server program
102 Document List Page Module
103 Print Condition Setting Page Module
104 Print Condition Storage Module
105 Print execution module
111 Printer information file
112 Print condition management file

Claims (21)

A print management device that causes a printing device to print document data in response to a print request transmitted from a terminal,
A print condition registration unit that registers a print condition specified in the print request with a print condition management unit that manages the print condition;
Based on a simple print request transmitted from the terminal and requesting printing under the print conditions registered in the print condition management means, referring to the print conditions registered in the print condition management means, the document A print management apparatus comprising: a simple printing unit for printing data. A print condition display data generating unit that generates print condition display data for causing the terminal to display print conditions registered in the print condition management unit based on the simple print request;
Display data transmitting means for transmitting the printing condition display data generated by the printing condition display data generating means to the terminal,
The simple printing unit prints the document data by referring to a printing condition registered in the printing condition management unit in response to a request transmitted from the terminal based on the printing condition display data. The print management device according to claim 1. The print management apparatus according to claim 1, wherein the print condition registration unit is provided in a print condition management apparatus connected to the print management apparatus via a network. 4. The print management apparatus according to claim 1, wherein the print condition management unit manages the print conditions for each user of the terminal. 5. The print management apparatus according to claim 1, wherein the print condition management unit manages a plurality of the print conditions for the same printing device. A print disable detection unit that detects that printing cannot be performed on a printing device designated as a print destination in a first print request transmitted from the terminal,
A proxy device determining unit that determines a printing device that can correspond to the printing condition specified in the first print request;
Proxy device information display data generating means for generating proxy device information display data for causing the terminal to display information of the printing device determined to be capable of responding to the printing condition by the proxy device determining unit,
The print management apparatus according to claim 1, wherein the display data transmitting unit transmits the proxy device information display data generated by the proxy device information display data generation unit to the terminal. In response to a second print request transmitted from the terminal based on the proxy device information display data, the document is sent to the printing device specified in the print request under the printing conditions specified in the first print request. 7. The print management apparatus according to claim 6, further comprising a proxy printing unit for printing data. A print function identification information management unit that manages information for identifying a print function of each of the plurality of printing devices;
The proxy-possible-apparatus determination unit includes a print condition specified in the first print request and information for identifying a print function of each of the plurality of printing devices managed by the print-function-identification-information management unit. 8. The print management device according to claim 6, wherein a printing device that can correspond to the first printing condition is determined based on the first and second printing conditions. 9. A printing apparatus according to claim 1, wherein the document data is printed by transmitting a print instruction to the printing apparatus to a printing apparatus management apparatus that manages the printing apparatus. The print management device according to the above. The printing-impossible detecting unit detects that printing cannot be performed on a printing device specified as a printing destination in the print request based on a response from the printing-device management device to the print instruction. Item 10. The print management device according to Item 9. 11. The print management device according to claim 9, wherein the print instruction to the print device management device is transmitted by SOAP. 12. The print management apparatus according to claim 1, wherein the print condition display data and the substitute device information display data are Web pages. A printing device management device that causes a printing device to print document data in response to a print instruction transmitted from a print management device based on a print request transmitted from a terminal,
The print management device includes:
A print condition registration unit that registers a print condition specified in the print request with a print condition management unit that manages the print condition;
Based on a simple print request transmitted from the terminal and requesting printing under the print conditions registered in the print condition management means, referring to the print conditions registered in the print condition management means, the document A printing device management apparatus comprising: a simple printing instruction transmission unit that instructs the printing device management apparatus to print data. If the printing device management device cannot perform printing on the printing device specified in the print instruction, the printing device management device notifies the printing management server that printing cannot be performed on the printing device,
The print management device includes:
A print disable detection unit that detects that printing cannot be performed on a printing device designated as a printing destination in a print request transmitted from the terminal, based on a notification that printing cannot be performed on the printing device from the printing device management. When,
A proxy device determining unit that determines a printing device that can correspond to the printing condition specified in the print request;
A proxy device information display data generating unit that generates proxy device information display data for causing the terminal to display information of a printing device determined to be compatible with the printing condition by the proxy device determination unit,
14. The printing device management apparatus according to claim 13, further comprising a display data transmitting unit that transmits the proxy device information display data generated by the proxy device information display data generating unit to the terminal. The printing device management apparatus according to claim 13, wherein the print instruction is transmitted by SOAP. A print management method in a print management device that causes a printing device to print document data in response to a print request transmitted from a terminal,
A print condition registration procedure for registering a print condition specified in the print request with a print condition management unit that manages the print condition;
Based on a simple print request transmitted from the terminal and requesting printing under the print conditions registered in the print condition management means, referring to the print conditions registered in the print condition management means, the document A simple printing procedure for printing data. A print disable detection procedure for detecting that printing cannot be performed on a printing device designated as a print destination in a print request transmitted from the terminal,
A proxy device determination procedure for determining a printing device capable of responding to the printing conditions specified in the print request;
A proxy device information display data generating step of generating proxy device information display data for causing the terminal to display information of a printing device determined to be compatible with the printing condition in the proxy device determination step;
17. The print management method according to claim 16, further comprising: a display data transmitting step of transmitting said proxy device information display data generated in said proxy device information display data generating procedure to said terminal. A print management device that causes a printing device to print document data in response to a print request transmitted from a terminal,
A print condition registration procedure for registering a print condition specified in the print request with a print condition management unit that manages the print condition;
Based on a simple print request transmitted from the terminal and requesting printing under the print conditions registered in the print condition management means, referring to the print conditions registered in the print condition management means, the document A print management program for executing a simple print procedure for printing data. A print disable detection procedure for detecting that printing cannot be performed on a printing device designated as a print destination in a print request transmitted from the terminal,
A proxy device determination procedure for determining a printing device capable of responding to the printing conditions specified in the print request;
A proxy device information display data generating step of generating proxy device information display data for causing the terminal to display information of a printing device determined to be compatible with the printing condition in the proxy device determination step;
19. The print management program according to claim 18, further comprising: a display data transmission procedure of transmitting the proxy device information display data generated in the proxy device information display data generation procedure to the terminal. A print management system comprising: a terminal; and a print management device that causes a printing device to print document data in response to a print request transmitted from the terminal,
The print management device includes:
A print condition registration unit that registers a print condition specified in the print request with a print condition management unit that manages the print condition;
Based on a simple print request transmitted from the terminal and requesting printing under the print conditions registered in the print condition management means, referring to the print conditions registered in the print condition management means, the document A print management system comprising: a simple printing unit for printing data. A print management system comprising: a terminal; a printing device management device that manages printing devices; and a print management device that transmits a document data print instruction to the printing device management device in response to a print request transmitted from the terminal. hand,
The print management device includes:
A print condition registration unit that registers a print condition specified in the print request with a print condition management unit that manages the print condition;
Based on a simple print request transmitted from the terminal and requesting printing under the print conditions registered in the print condition management means, referring to the print conditions registered in the print condition management means, the document A print management system comprising: a simple print instruction transmission unit that instructs the printing device management apparatus to print data.

Images