JP2013008174A - Printing system, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a print queue management method for managing the generation order of print data in a printing system on the Internet in which the IP addresses of a printer are redundant.SOLUTION: A print server is configured to manage a printer name, IP address, and UUID (Universally Unique Identifier) in association as printer information, to accept a print data generation request including the printer name of a print destination, to acquire the UUID by referring to printer information which the printer name matches, and to, when there does not exist any print queue corresponding to the UUID in the case of accepting the print data generation request, create a print queue. A printer is configured to transmit a print data request including the UUID to the print server. The print server is configured to acquire and transmit print data by referring to the print queue corresponding to the UUID of which the print server has been notified.

Description

  The present invention relates to a print system, a method, and a program for managing a print document registered by an authenticated user and executing printing of the print document in response to a request from the user.

  2. Description of the Related Art Conventionally, a printing system that manages document data for printing and a printing destination printer is known. The printing system receives document data from a user application or another document management system, creates print document information, and holds the document data in association with the document data. The printing system holds a print queue for each printer, and manages print execution requests from users in the print queue. The printing system generates print data according to the order of the print queue and transmits the print data to the printer.

  In recent years, due to the spread of the Internet and the speeding up of the network, cases where functions provided by software are provided as services on the Internet are increasing. There may be a case where a printing system exists as a back end of such a service.

  In the case of an intranet printing system, it is common to identify a network printer by an IP address. However, since a printing system on the Internet manages network printers connected to different LANs, the printer IP addresses may overlap. As a method of solving such a problem, Patent Document 1 proposes a method of holding a USD of a WSD (Device Profile for Web Service) in association with an IP address.

JP 2009-15408 A

  When the printing system is provided as an Internet service, it is generally not possible to connect to the intranet printer from the printing system. Therefore, it is common to connect to the printing system from the printer and acquire print data. In this case, the printing order is controlled not by the printing system but by the printer. However, the order in which the print data is generated needs to be controlled by the printing system, and a print queue is required to serialize the print data generation order for each printer. If there is no print queue for each printer, the order of generating print data is biased toward a specific printer, and the order of generating print data for other printers is not easy. Further, when a print queue is created for each IP address, different printers share the print queue, and there is a problem that the print data generation order cannot be controlled for each printer.

  An object of the present invention is to provide a print queue management method capable of managing the generation order of print data in a print system on the Internet where printer IP addresses overlap.

  A printing system comprising a printing device information management server, a print queue management server, and at least one printing device connected via the Internet, wherein the printing device information management server includes a printing device name, an IP address, and a UUID A printing device information management unit that manages them as printing device information, a print data generation request reception unit that receives a print data generation request including the printing device name of the printing destination, and prints when a print data generation request is received The print queue management server includes a UUID acquisition unit that refers to the printing device information that matches the device name and acquires a UUID. The print queue management server includes a print data generation request reception unit that receives a print data generation request including the UUID of the printing device, and a print If there is no print queue corresponding to the UUID when a data generation request is received, the print queue creation unit that creates the print queue and the print queue A print job management unit that manages print jobs, a print data generation unit that generates print data according to the order of print jobs managed in the print queue, and a print queue with a UUID that is notified when a print data request is received A print data transmission unit that acquires print data and transmits the print data, and the printing apparatus transmits a print request reception unit that receives the print request and a print data request including the UUID to the print queue management server. A print data request transmission unit.

  Even in a printing system on the Internet where printer IP addresses overlap, it is possible to manage a print queue for serializing the generation of print data for each printer.

1 is a diagram illustrating an overall configuration of a printing system. It is a block diagram which shows the basic hardware constitutions of a client terminal and a server. FIG. 2 is a block diagram illustrating a basic hardware configuration of a printer. It is the figure which showed the software block diagram of the client terminal. FIG. 2 is a diagram illustrating a software configuration of a printer. It is the figure which showed the software block diagram of the request reception server. FIG. 3 is a diagram illustrating a software configuration of a print document management server. 3 is a diagram illustrating a software configuration of a print queue management server. FIG. It is the figure which showed the block diagram of the printing document data storage server. It is the figure which showed print document allocation information. FIG. 6 is a diagram illustrating print queue allocation information. It is a figure showing printer information. It is the figure which showed print document information. It is a figure which shows print queue information. FIG. 6 is a diagram illustrating print job information. FIG. 10 is a diagram illustrating a sequence until the UUID of the printer 105 is stored. It is a figure which shows the sequence until printing is performed. It is a figure which shows the sequence until printing is performed. 6 is a flowchart illustrating a processing flow of a print queue management server that has received a print data generation request. 6 is a flowchart illustrating a processing flow of a print queue management server that has received a print data request. 2 is a diagram illustrating a Web page for registering a printer 105. FIG. It is a figure which shows the web page in which the script was embedded. It is a figure which shows the web page in which the script was embedded.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

  First, a printing system which is a premise of the present invention will be described.

  FIG. 1 is a diagram showing an overall configuration of a printing system according to an embodiment of the present invention. In FIG. 1, reference numeral 101 denotes a system in an intranet such as a company. The client terminal 104 and the printer 105 are connected via a communication line (not shown). In the figure, it is assumed that a plurality of client terminals 104 and printers 105 are connected.

  Reference numeral 102 denotes a system provided in the data center. The request reception server 106, the authentication server 107, the print document management server 108, the print document data storage server 110, and the print queue management server 109 are connected via a communication line (not shown). In the figure, it is assumed that a plurality of print document management servers 108 and print queue management servers 109 are connected.

  The communication line is a so-called communication network realized by, for example, a LAN, WAN, telephone line, dedicated digital line, ATM, frame relay line, cable TV line, data broadcasting wireless line, or a combination thereof. . The communication line only needs to be able to transmit and receive data, and the communication means between the client terminal 104, the printer 105, and each server may be different.

  101 and 102 are connected via the Internet 103. In the present invention, it is assumed that there are a plurality of 101 connected to 102.

  The client terminal 104 includes, for example, a desktop personal computer, a notebook personal computer, a mobile personal computer, and a PDA (personal data assistant), but may be a mobile phone with a built-in program execution environment.

  The printer 105 is a printer (for example, a laser printer) or an MFP (Multifunction Peripheral) that can be connected to a network on which WSD is mounted.

  The request reception server 106 receives a request from the client terminal 104 or the printer 105 and returns a response.

  The authentication server 107 supports a protocol such as LDAP and provides a directory service, and manages information on users who access the printing system. The authentication server 107 receives the request from the client terminal 104 and performs user authentication.

  The print document management server 108 manages the state of print document data stored in the print document data storage server 110.

  In response to the print request, the print queue management server 109 reads the print document data stored in the print document data storage server 110 and converts it into a format that the printer 105 can interpret.

  The print document data storage server 110 is a file server that supports a file sharing protocol such as SMB (Server Message Block), or a network such as SAN (Storage Area Network) or NAS (Network Attached Storage). Storage that can be connected. The print document data storage server 110 holds print document data associated with print document information.

  FIG. 2A is a block diagram showing the basic hardware configuration of the client terminal 104, the request reception server 106, the authentication server 107, the print document data storage server 110, the print document management server 108, and the print queue management server 109.

  In FIG. 2a, a CPU 201, a RAM 202, a ROM 203, a LAN adapter 204, a video adapter 205, an input unit (keyboard) 206, an input unit (mouse) 207, a hard disk 208, and a CD-ROM drive 209 are respectively connected via a system bus 200. Are connected to each other. The system bus 200 includes, for example, a PCI bus, an AGP bus, and a memory bus. In FIG. 2a, a connection chip between each bus and a keyboard interface, that is, an input / output interface such as a so-called SCSI or ATAPI is omitted.

  The CPU 201 performs various operations such as four arithmetic operations and comparison operations based on an operation system program and application programs, and controls hardware. The RAM 202 stores an operating system program, an application program, and the like that are squeezed out from a storage medium such as a hard disk 208 or a CD-ROM or CD-R mounted in the CD-ROM drive 209. These programs are executed by the CPU 201.

  The ROM 203 stores a so-called BIOS or the like that controls input / output of data to the hard disk 208 or the like in cooperation with the operation system. The LAN adapter 204 communicates with an external device connected via a network in cooperation with an operation system communication program controlled by the CPU 201. The video adapter 205 generates an image signal to be output to the display device. A keyboard 206 and a mouse 207 are used to input instructions to the client terminal 104.

  The hard disk 208 stores an operating system and application programs (for example, a printing system program according to the present invention).

  The CD-ROM drive 209 is used to install an application program in the hard disk 208 by mounting a storage medium such as a CD-ROM, CD-R, and CD-R / W. Needless to say, a CD-R drive, a CD-R / W drive, a DVD drive, or the like may be used.

  FIG. 2B is a block diagram illustrating a basic hardware configuration of the printer 105. In FIG. 2 b, a CPU 211, a RAM 212, a ROM 213, a LAN adapter 214, a printer engine 215, a hard disk 216, an operation panel 217, and an IC card reading unit 218 are connected to each other via a system bus 210. The system bus 210 includes, for example, a PCI bus, an AGP bus, and a memory bus. In FIG. 2b, connection chips and keyboard interfaces between the buses, input / output interfaces such as so-called SCSI and ATAPI are omitted.

  The CPU 211 executes software stored in the hard disk 216 using the RAM 212 as a work memory. Further, the operation of the printer 105 is set in accordance with a user instruction input from the operation panel 217. In addition, the CPU 211 generates image data based on print data input from an external device via the LAN adapter 214, supplies the image data to the printer engine 215, and performs printing. The ROM 213 stores a so-called BIOS or the like that controls data input / output to the hard disk 216 or the like.

  FIG. 3A is a diagram showing a software configuration of the client terminal 104 constituting this system. The client terminal 104 includes a Web browser 301 that interprets HTML (HyperText Markup Language) and displays a Web page on the UI. The web browser 301 has a function of executing a script included in HTML.

FIG. 3B is a diagram showing a software configuration of the printer 105 constituting this system.
The printer 105 includes a UI unit 311 that receives input from the user via the operation panel 217. An authentication request transmission unit 312 that transmits an authentication request including a user name and a password input by the user via the UI unit 311 to the authentication server 107 is provided. A print data acquisition unit 315 that acquires print data from the print queue management server 109 is provided. The image processing apparatus includes a print execution unit 316 that generates image data based on the print data, supplies the image data to the printer engine 215, and performs printing. A print data generation request transmission unit 317 is provided that transmits a print data generation request to the request reception server 106 when printing is instructed by the user via the UI unit 311.

  FIG. 4 a is a diagram showing a software configuration of the request reception server 106. The request reception server 106 holds print document assignment information 408, print queue assignment information 409, and printer information 410. A request reception unit 401 that receives print data generation requests and print data requests from the client terminal 104 and the printer 105 is provided. According to the print document allocation information 408, a print document management server specifying unit 402 for specifying the print document management server 108 and a print data generation request transmitting unit 404 for transmitting a print data generation request to the print document management server 108 are provided. According to the print queue assignment information 409, a print document management server specifying unit 402 for specifying the print queue management server 108 and a print data request transmitting unit 405 for transmitting a print data request to the print document management server 110 are provided. A printer information management unit 406 that manages the printer information 410 is provided. A Web page generation unit 407 that generates a Web page to be returned to the client terminal 104 is provided.

  FIG. 4B is a diagram illustrating a software configuration of the print document management server 108. The print document management server 108 holds print document information 425 for managing the state of print document data stored in the print document data storage server 110. The print queue allocation information 426 is held. A print document management unit 421 that manages the print document information 425 is provided. A print data generation request receiving unit 422 that receives a print data generation request from the request reception server 106 is provided. According to the print queue allocation information 426, a print queue management server specifying unit 423 that specifies the print queue management server 109 and a print data generation request transmission unit 424 that transmits a print data generation request to the print queue management server 109 are provided.

  FIG. 5 a is a diagram showing a software configuration of the print queue management server 109. The print queue management server 109 holds print queue information 505. A print queue management unit 501 that manages the print queue information 505 is provided. A print data generation request receiving unit 502 that receives a print data generation request from the print document management server 108 is provided. A print data generation unit 504 that generates print data according to the order of the print queue information 505 is provided.

  FIG. 5 b is a diagram showing a configuration diagram of the print document data storage server 110. The print document data storage server 110 holds print document data 511.

  6 to 8 are diagrams showing information held by the servers constituting this system.

  FIG. 6A is a diagram showing the print document allocation information 408 held by the print request reception server 106. The print document allocation information includes a print document owner list 601. The owner list 601 is a list of print document allocation individual information 602 including an owner ID and a server IP address indicating the IP address of the print document management server.

  FIG. 6B is a diagram showing the print queue assignment information 426 held by the print document management server 108. The print queue assignment information 426 includes a print queue list 611. The print queue list 611 is a list of print queue allocation individual information 612 including a UUID of a printer that implements WSD and a server IP address indicating the IP address of the print queue management server.

  FIG. 7A is a diagram showing the printer information 410 held by the print request reception server 106. The printer information 410 includes a printer list 701. The printer list 701 is a list of printer individual information 702 including a printer name, a printer IP address, and a UUID of a printer that implements WSD.

  FIG. 7 b is a diagram showing print document information 425 held by the print document management server 108. The print document information 425 includes a print document owner list 711. The owner list 711 is a list of individual owner information 712 including an owner ID and a print document list. The print document list is a list of print document individual information 713 including the print document ID, the document name of the print document, the reception date and time, the number of pages, and the status.

  FIG. 8A is a diagram showing the print queue information 505 held by the print queue management server 109. The print queue information 505 includes a print queue list 801. A print queue list 801 is a list of print queue individual information 802 including a UUID of a printer that implements WSD and a print job list. The print job list is a list of individual print job information 803 including a print job ID, a print document ID, a print order, and a status.

  FIG. 8 b is a diagram showing print job information 318 held by the printer 105. The print job information 318 includes a print job list 811. The print job list 811 is a list of individual print job information 812 including a print document ID, a print order, and a status.

  FIG. 9 is a diagram showing a sequence until the UUID of the printer 105 is stored in this system. As a premise of the sequence, the user logs in to the authentication server 107 of this system via the client terminal 104, accesses the request reception server 106, and requests a Web page for registering the printer 105.

  When the user inputs the printer name and the printer IP address on the Web page displayed on the Web browser 301 of the client terminal 104, the input information is transmitted to the request reception server 106 (901). The request reception unit 401 of the request reception server 106 receives an IP address. The web page creation unit 407 generates a web page in which a script that acquires a UUID from the printer 105 of the received IP address and transmits it to the request reception server 106 is embedded. The request reception unit 401 transmits the Web page to the client terminal 104 (902). The web browser 301 of the client terminal 104 executes the script and acquires the UUID from the printer 105 (903 to 904). The web browser 301 transmits the acquired UUID to the request reception server 106 (905). The request reception unit 401 of the request reception server 106 receives the UUID, and the printer information management unit 406 stores it as printer individual information 702 in the printer list 701 of the printer information 410. The request reception unit 401 of the request reception server 106 returns a response to the client terminal (906).

  10 and 11 are diagrams showing a sequence from when a print request is made to the system until printing is executed.

  As a premise of the sequence in FIG. 10, the user logs in to the authentication server 107 of this system via the client terminal 104, accesses the request reception server 106, and requests a Web page for issuing a print instruction.

  When a print document and a print destination printer are selected and a print instruction is issued on the Web page displayed on the Web browser 301 of the client terminal 104, a print data generation request is transmitted to the request reception server 106 (1001). The print data generation request includes a print document ID, a print document owner ID, and a print destination printer name. The request reception unit 401 of the request reception server 106 receives a print data generation request. The printer information management unit 406 searches the printer list 701 with reference to the printer information 410. The printer information management unit 406 acquires the UUID by referring to the printer individual information 702 having the same printer name. Also, the print document management server specifying unit 402 refers to the print document allocation information 408 and searches the print document owner list 601. The print document management server specifying unit 402 refers to the print document assignment individual information 602 having the same owner ID, and specifies the IP address of the print document management server 108 that transmits the print data generation request. The print data generation request transmission unit 404 transmits a print data generation request to the print document management server 108 with the specified IP address (1002). The print data generation request includes the print document ID, the owner ID of the print document, and the UUID of the printer that is the print destination.

The print data generation request receiving unit 422 of the print document management server 108 receives the print data generation request. The print document management unit 421 searches the owner list 711 with reference to the print document information 425. The print document management unit 421 refers to the print document list with reference to the owner individual information 712 having the same owner ID included in the print data generation request. The print document management unit 421 refers to the print document individual information 713 with the same print document ID included in the print data generation request, and changes the status during printing. The print queue management server specifying unit 423 searches the print queue list 611 with reference to the print queue assignment information 426. The print queue management server specifying unit 423 specifies the IP address of the print queue management server 109 that transmits the print data generation request with reference to the print queue assignment individual information 612 having the same UUID. The print data generation request transmission unit 424 transmits a print data generation request to the print queue management server 109 with the specified IP address (1003).
The print queue management server 109 that has received the print data generation request returns a response to the print document management server 108 (1004). The print data generation request transmission unit 424 of the print document management server 108 receives a response from the print queue management server 109. The print data generation request reception unit 422 returns a response to the request reception server 106 (1005). The print data generation request transmission unit 404 of the request reception server 106 receives a response from the print document management server 108. The request reception unit 401 transmits a Web page in which a script for transmitting a print request is embedded to the printer 105 (1006). The web browser 301 of the client terminal 104 executes the script and transmits a print request to the printer 105 (1007). The print request includes a print document ID. The print request reception unit 313 of the printer 105 receives the print request, and the print job management unit 314 stores the print request as print job individual information in the print job list 811 of the print job information 318. The print request receiving unit 313 returns a response to the client terminal (1008).

  The print data acquisition unit 315 of the printer 105 sequentially transmits print data requests to the request reception server 106 in accordance with the print order of the print job individual information 803 registered in the print job list 811 of the print job information 318 (1009). The print data request includes a UUID and a print document ID. The request reception unit 401 of the request reception server 106 receives a print data request. The print queue management server specifying unit 403 searches the print queue list 611 with reference to the print queue assignment information 409. The print queue management server specifying unit 403 specifies the IP address of the print queue management server 109 that transmits the print data request with reference to the print queue assignment individual information 612 having the same UUID. The print data request transmission unit 405 transmits a print data request to the print queue management server 109 with the specified IP address (1010).

  The print queue management server 109 that has received the print data request transmits the print data to the request reception server 106 if the print data has been generated (1011). The print data request transmission unit 405 of the request reception server 106 receives a response from the print queue management server 109. The request reception unit 401 transmits print data to the printer 105 (1012). The print data acquisition unit 315 of the printer 105 receives the print data. The print execution unit 316 executes print processing.

  As a premise of the sequence in FIG. 11, the user logs in to the authentication server 107 of this system via the UI unit 311 of the printer 105, accesses the request reception server 106, and requests information for issuing a print instruction. .

  When a print document is selected and a print instruction is issued on the print instruction screen displayed on the UI unit 311 of the printer 105, the print data generation request transmission unit 317 transmits a print data generation request to the request reception server 106 (1101). ). The print data generation request includes a print document ID, a print document owner ID, and a printer UUID. The sequence of the request reception server 106, the document management server 108, and the print queue management server 110 that have received the print data generation request is the same as 1002 to 1005 in FIG. The print data generation request transmission unit 404 of the request reception server 106 receives a response from the print document management server 108. The request reception unit 401 transmits a response to the printer 105 (1102). The print job management unit 314 of the printer 105 adds print job individual information to the print job list 811 of the print job information 318.

  The sequence from when the printer 105 acquires print data to when the print process is executed is the same as 1009 to 1012 in FIG.

  FIG. 12 is a flowchart showing the flow of processing of the print queue management server 109 that has received the print data generation request (1003) of FIG. 10 and FIG.

  In step S1201, the print queue management server 109 that has received the print data generation request searches the print queue list 801 with reference to the print queue information 505 in step S1202. It is determined whether there is print queue individual information 802 that matches the UUID included in the print data generation request. If it is determined that the print queue individual information 802 exists, the process advances to step S1204. If it is determined in step S1202 that the print queue individual information 802 does not exist, the print queue individual information 802 corresponding to the UUID is created in step S1203. In step S1204, the print job individual information 803 is added to the print job list of the print queue individual information 802, and the process ends.

  Note that step S1201 is executed by the print data generation request receiving unit 502. Steps S1202 to 1401 are executed by the print queue management unit 501.

  The print data generation unit 504 of the print queue management server 109 sequentially performs processing according to the print order of the print job individual information 803 registered in the print job list of the print queue individual information 802. Specifically, the print document data 511 corresponding to the print document ID is acquired from the print document data storage server 110, and print data is generated.

  FIG. 13 is a flowchart showing a processing flow of the print queue management server 109 that has received the print data request (1010) of FIGS. 10 and 11.

  Upon receiving the print data request in step S1301, the print queue management server 109 searches the print queue list 801 with reference to the print queue information 505 in step S1302. The print job individual information 803 of the print queue individual information 802 having the same UUID included in the print data request is referred to. In step S1303, the status of the print job individual information 803 is referenced to determine whether print data has been generated. If it is determined that the print data has been generated, the print data is transmitted to the request reception server 106 in step S1304, and the process ends. The request reception server 106 transmits the print data received from the print queue management server 109 to the printer 105. If it is determined in step S1303 that print data has not been generated, an error response is transmitted to the request reception server 106 in step S1305, and the process ends. The request reception server 106 transmits the error response received from the print queue management server 109 to the printer 105, and the printer that has received the error response waits for a certain period of time and then sends a print data request to the request reception server 106 again. To send.

  Note that steps S1301, S1304, and S1305 are executed by the print data request receiving unit 503. Steps S1302 and S1303 are executed by the print queue management unit 501.

  FIG. 14A is a diagram showing a Web page for registering the printer 105 displayed as a premise of the sequence of FIG. Reference numeral 1401 denotes a screen for receiving an input for registering the printer 105. Reference numeral 1402 denotes an edit box for inputting a printer name. Reference numeral 1403 denotes an edit box for inputting an IP address. Reference numeral 1404 denotes a cancel button, and 1405 denotes an OK button. The user inputs an arbitrary printer name for the user to identify the printer in the edit box 1402, and inputs the printer IP address in the edit box 1403. When the OK button 1405 is pressed, the input information is transmitted to the request reception server 106 (901).

  FIG. 14B is a diagram showing a Web page in which a script is returned, which is returned by the request reception server 106 in 902 of FIG. While the web browser 301 of the client terminal 104 executes a script that acquires the UUID from the printer 105 and transmits it to the request reception server 106, the web page 1411 is displayed on the web browser 301.

  FIG. 15 is a diagram showing a Web page embedded with a script returned by the request reception server 106 in 1006 of FIG. While the Web browser of the client terminal 104 is executing a script for transmitting a print request to the printer 105, a Web page 1501 is displayed on the Web browser 301.

  In this embodiment, the request reception server 106, the authentication server 107, the print document management server 108, the print queue management server, and the print document data storage server 110 are implemented as independent servers. However, it goes without saying that any combination of these servers may be implemented as a single server.

  As described above, according to the present invention, the printing system manages printer information by associating a printer name, an IP address, and a UUID, and when a print data generation request is received, a print queue corresponding to the UUID. If there is no print queue, create a print queue. For this reason, even in a printing system on the Internet where printer IP addresses overlap, it is possible to manage a print queue for serializing the generation of print data for each printer.

  Further, according to the present invention, when receiving a printer registration request, the printing system generates a Web page in which a script for acquiring a UUID from the printer and transmitting it to the request receiving server is embedded, and the printer name, IP address , Accept UUID and save. Therefore, even in a printing system on the Internet where the printer IP address is duplicated, the printer information including the UUID can be easily registered.

  According to the invention, the printing system accepts a print data generation request including a UUID from the printer. For this reason, even in the case of a printing system on the Internet in which the IP address of the printer is duplicated, a printing instruction can be issued from the printer.

101 System 104 Client terminal 105 Printer

Claims (6)

A printing system comprising a print server (106, 109) and at least one printing apparatus (105) connected via the Internet,
The print server (106, 109) includes a printing apparatus information management unit (416) that manages printing apparatus information (420) by associating a printing apparatus name, an IP address, and a UUID, and print data including a printing apparatus name of a printing destination. A print data generation request reception unit (411) that receives a generation request, and a UUID acquisition unit (416) that refers to the printing device information (420) that matches the printing device name when receiving the print data generation request and acquires a UUID ), A print data generation request receiving unit (502) that receives a print data generation request including the UUID of the printing apparatus, refers to the print queue of the notified UUID, acquires the print data, and transmits the print data; When a data generation request is received, if there is no print queue corresponding to the UUID, a print queue is created, and a print queue management unit (501) that manages print jobs in the print queue; Includes print data generating unit that generates print data according to the order of print jobs managed by the printing queue and (504),
The printing apparatus (105) includes a print request reception unit (313) that receives a print request, and a print data request transmission unit (315) that transmits a print data request including a UUID to the print server (106, 109). Characteristic printing system. The print server (106, 109) acquires the UUID from the printing apparatus registration request receiving unit (401) that receives the printing apparatus registration request including the IP address and the printing apparatus of the IP address when the printing apparatus registration request is received. A Web page generation unit (407) that generates a Web page in which a script to be transmitted to the request reception server is embedded, a Web page transmission unit (401) that transmits a Web page, and a print including a printer name, an IP address, and a UUID The printing system according to claim 1, further comprising: a printing apparatus information receiving unit (401) that receives the apparatus information; and a printing apparatus information management unit (406) that receives and stores the printing apparatus information. A printing system comprising a print server (109) and at least one printing apparatus (105) connected via the Internet,
If there is no print data generation request reception unit (502) that receives a print data generation request including the UUID of the printing apparatus and no print queue corresponding to the UUID when the print data generation request is received, the print server (109) A print queue creation unit (501) that creates a print queue, a print job management unit (501) that manages print jobs in the print queue, and print data that generates print data according to the order of the print jobs managed in the print queue A generation unit (504), and a print data transmission unit (502) that refers to the print queue of the notified UUID when receiving a print data request, acquires the print data, and transmits the print data,
The printing apparatus (105) transmits a print data generation request transmission unit (317) that transmits a print data generation request including the UUID to the print queue management server (109), and transmits a print data request including the UUID to the print server (109). And a print data request transmission unit (315). A print queue management method for managing a print queue for performing printing with at least one printing apparatus (105) connected via the Internet,
Printing device information management means (416) that manages printing device information (420) by associating the printing device name, IP address, and UUID, and print data generation request reception that receives a print data generation request including the printing device name of the printing destination When the print data generation request is received with the means (411), the UUID acquisition means (416) for referring to the printing device information (420) having the same printing device name and acquiring the UUID, and the UUID of the printing device are included. A print data generation request receiving unit (502) that receives a print data generation request, refers to the print queue of the notified UUID, acquires the print data, and transmits the print data. When the print data generation request is received, If there is no print queue corresponding to the UUID, a print queue is created, and a print job management means (501) for managing print jobs in the print queue and a print queue managed by the print queue Print queue management method characterized in that it comprises a print data generating unit that generates print data in the order of the printing job (504). A printing apparatus registration request receiving unit (401) that receives a printing apparatus registration request including an IP address, and a script that acquires a UUID from the printing apparatus of the IP address and transmits it to the request receiving server when the printing apparatus registration request is received. Web page generating means (407) for generating an embedded Web page, Web page transmitting means (401) for transmitting a Web page, and printing apparatus information receiving means for receiving printing apparatus information including the printing apparatus name, IP address, and UUID 5. The print queue management method according to claim 4, further comprising: (401) and printing apparatus information management means (406) for receiving and storing printing apparatus information. A computer-readable storage medium storing a computer program for managing a print queue for performing printing with at least one printing apparatus (105) connected via the Internet,
A step (S1201) of receiving a print data generation request including the print device name of the print destination, and when receiving the print data generation request, refer to the print device information (420) with the matching print device name to acquire the UUID. Step (S1201), step (S1202) for determining whether there is a print queue corresponding to the UUID, step (S1203) for creating a print queue if there is no print queue corresponding to the UUID, and printing to the print queue A step of registering a job (S1204), a step of receiving a print data request (S1301), a step of specifying a print queue corresponding to the UUID included in the print data request (S1302), and acquiring and transmitting the print data A computer program for managing a print queue, comprising: a step (S1304) A computer-readable storage medium for storing the ram.