JP2014142734A - Batch printing control in cloud printing - Google Patents

Abstract

In a print system as a cloud service, authentication is required when pull printing is performed. The printer acquires print data from the print server using an authorization token previously authenticated by an authentication service. Batch printing in the cloud print service is realized by automatically executing authentication printing with a dedicated user registered in advance at a printing execution timing scheduled in advance. However, when another user logs in to the printer for authentication printing during batch printing, the dedicated user logs out. In that case, there is a problem that a job reserved for batch printing cannot be executed correctly.
During batch printing, a printer is controlled so as not to accept an authentication print login of another user. By doing so, it is possible to prevent a user dedicated to batch printing from logging out and to execute a batch print job reliably.
[Selection] Figure 1

Description

  The present invention relates to a printing system, a method, and a program for realizing batch printing in a printing system, particularly a pull printing system.

  In recent years, business development has been carried out to publish services on the Internet as cloud services. Among them, the print server is also required to provide a function as a print service on the Internet.

  By arranging a print server on a large-scale data center and providing a print service as a cloud service, hardware management for each customer becomes unnecessary. In addition, there are various merits that it is easy to add resources according to the load of the server. In addition, since this print service needs to manage a large amount of user information at once, more robust and safe user management is performed by using an external authentication service. The user can receive the service by authenticating with this authentication service and using the authentication token issued at that time.

  A print service deployed on the Internet as a cloud service has an environment in which a print server and a printer are located over a firewall. For this reason, the printer performs printing in the pull print method in which print data is acquired from the print server via the Internet. At this time, an authorization token that is authorized by the print execution user who has been authenticated by the authentication service is registered in the printer, and by using this, print data can be acquired as a correctly authenticated request.

  Further, the business printing system requires batch printing that automatically executes a large number of pages and a large number of jobs at night. In the cloud print service, the same method as the authentication printing is used in the batch printing in order to perform pull printing while using the external authentication service and maintaining security. Authentication printing is a method in which a user logs in from a printer operation screen, selects his / her job, and executes printing. Cloud print batch printing is realized by repeatedly performing this operation using a dedicated user.

  However, in this batch printing, generally, a large number of pages and a large number of jobs are executed, and it takes time to complete the processing. Therefore, during batch printing, even if another user executes a print job, the user waits for a long time until batch printing is completed and printing of the job is actually started. As a prior art aiming at solving such a problem, a system has been proposed in which printing of print data in a print queue is postponed to give an authentication recipient exclusive control of the printing apparatus ( Patent Document 1).

JP 2002-287932 A

  In the prior art method, when an authentication printing operation is performed, the print queue is temporarily postponed, and the authentication print job is preferentially executed.

  However, since batch printing with cloud printing uses the same method as authentication printing, when another user logs in to the printer, a batch printing dedicated user logs out. In that case, there is a problem that a job reserved for batch printing cannot be executed correctly. In batch printing, a large number of jobs are executed unattended at night, and if a large number of jobs that should have been completed result in an error against the user's intention, the impact on the business is large.

  An object of the present invention is to reliably execute batch printing with cloud printing.

In a printing system including a client terminal (101 to 103) having a Web browser (301), a print server (104), a printer (105 to 108), and an authentication server (112),
The printer (105 to 108) communicates with the authentication server (112) based on user information input from the user, and authenticates the user.
Means for the printer (105-108) to obtain from the print server (104) print job information associated with the authenticated user or the printer (105-108);
Means for the printer (105-108) to acquire and print print job data from the print server (104) using the authenticated user information;
The printer (105 to 108) acquires print job data from the print server (104) using the authenticated user information and printer identification information set in advance at a preset time or period, and prints the print job data. Means,
The printer (105 to 108) acquires print job data from the print server (104) using the authenticated user information and printer identification information set in advance at the preset time or period, and prints them. Means for prohibiting user authentication by user information input from the user,
A printing system comprising:

  In the present invention, during batch printing in cloud printing, other users' authentication printing operations are prohibited. By doing so, it is possible to prevent a user dedicated to batch printing from logging out and to execute a batch print job reliably.

Block diagram showing network configuration Hardware diagram of print server, authentication server, client terminal, printer Module diagram of print server, authentication server, client terminal, and printer Software configuration of print server and authentication server Software configuration diagram of authenticated printing application and pull printing application Configuration diagram of information managed by the printing system Sample screen generated by the authentication printing application Operation flow of printer in embodiment 1

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

  FIG. 1 is a diagram showing an overall configuration of a printing system according to an embodiment of the present invention.

  In FIG. 1, client terminals 101 to 103, a print server 104, printers 105 to 108, and an authentication server 112 are connected via networks 109 to 111.

  In the figure, it is assumed that a plurality of client terminals 101 to 103 and printers 105 to 108 are connected. The networks 109 to 111 are, for example, a LAN such as the Internet, a WAN, a telephone line, a dedicated digital line, an ATM, a frame relay line, a cable television line, a data broadcasting wireless line, or the like. It is a so-called communication network realized by a combination of these.

  The networks 109 to 111 only need to be able to transmit and receive data. The communication means from the client terminals 101 to 103 to the print server 104 and the printers 105 to 108 and the communication means from the printers 105 to 108 to the print server 104 may be different.

  The client terminals 101 to 103 are, for example, a desktop personal computer, a notebook personal computer, a mobile personal computer, a PDA (personal data assistant), or the like, but may be a mobile phone with a built-in program execution environment. Each of the client terminals 101 to 103 includes an environment for executing a program such as a Web browser (Internet browser, WWW browser, browser used for World Wide Web).

  The authentication server 112 issues an authorization token in response to a request from the printers 105 to 108.

  Upon receiving a print job list acquisition request from the printers 105 to 108, the print server 104 confirms the validity of the authorization token included in the request with the authentication server. When the authorization token is valid, the print server 104 returns a print job list existing on the print server 104 based on the request content.

  When the print server 104 receives a print request from 105 to 108, the print server 104 confirms the validity of the authorization token included in the request with the authentication server. If the authorization token is valid, the print server 104 registers a print execution job and generates print data based on the content of the request. At this time, the printers 105 to 108 register the pull print job.

  The printers 102 to 108 transmit a print data acquisition request to the print server 104 according to the contents of the pull print job. When the print server 104 receives print data acquisition requests from the printers 102 to 108, the print server 104 confirms the validity of the authorization token included in the request with the authentication server. If the authentication token is valid, the print server 104 transmits the generated print data to the printers 102 to 108.

  FIG. 2 is a hardware configuration diagram of the client terminals 101 to 103, the print server 104, the authentication server 112, and the printers 105 to 108 of the printing system according to the embodiment of the present invention.

  In FIG. 2, 202 is a CPU that controls the entire apparatus, executes an application program, OS, and the like stored in a hard disk (HDD) 205, and temporarily stores information, files, and the like necessary for executing the program in a RAM 203. Control to store in.

  Reference numeral 204 denotes a ROM as storage means, which stores programs such as a basic I / O program, various data such as print data and printer information used in print processing.

  Reference numeral 203 denotes a RAM as temporary storage means, which functions as a main memory, work area, and the like for the CPU 202.

  Reference numeral 205 denotes one of external storage means, which is a hard disk (HDD) that functions as a large-capacity memory. An application program such as a Web browser, a print server program, an authentication server program, an OS, and related programs are stored.

  A display 206 is a display unit that displays commands input from the keyboard 207, printer status, and the like.

  An external device I / F 208 is an I / F for connecting a printer, a USB device, and a peripheral device.

  Reference numeral 207 denotes a keyboard as instruction input means.

  A system bus 201 controls the data flow in the print server, authentication server, and client terminal of the printing system.

  A network interface card (NIC) 209 exchanges data with external devices via the interface 209 and the networks 109 to 111.

  Note that the configuration of the computer is an example thereof, and is not limited to the configuration example of FIG. For example, the storage location of data and programs can be changed by ROM, RAM, HDD, etc. according to the characteristics.

  Reference numeral 209 denotes a controller for the printers 105 to 108, which is a device that controls the printer control system.

  A CPU 210 controls the entire apparatus, and comprehensively controls access to various devices connected to the system bus 218. This control is based on a control program or the like stored in the ROM 212 or a control program or resource data (resource information) stored in the external memory 223 connected via the disk controller (DKC 216).

  Reference numeral 211 denotes a RAM that functions as a main memory, a work area, and the like of the CPU 210, and is configured such that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown).

  Reference numeral 213 denotes external storage means that functions as a large-capacity memory, and stores a pull print application program and related programs.

  A user interface 221 for performing a pull print operation and a pull print switching button are arranged on an operation panel (operation unit) 221. In addition, buttons for performing operations such as setting of operation modes of the printers 105 to 108, display of operation states of the printers 105 to 108, and designation of copying, and display units such as a liquid crystal panel and LEDs 214 are also arranged.

  A network interface card (NIC) 219 exchanges data with an external device via the interface 219.

  The print engine 220 shown in this figure uses a known printing technique, and examples of suitable implementation systems include an electrophotographic system (laser beam system), an ink jet system, and a sublimation method (thermal transfer) system. .

  A raster controller 215 is a controller that converts print data in PDL language / PDF language into image data. A device I / F 217 is a connection I / F with an external device that can be connected by USB or the like.

  FIG. 3 is a system configuration diagram of the printing system according to the embodiment of the present invention.

  The print server 104 includes a print job management service 306 that manages print jobs. This service manages document data and the like input from other services or other programs in the storage 307 as print data. The data format of the print data is a format such as PDL or PDF. The storage 307 is a storage device such as an HDD built in the information processing apparatus of the print server 104, an externally connected HDD, or a network storage.

  A print management service 305 manages the printers 105 to 108, and manages printer information described later for each printer.

  The Web service 303 returns print data in response to a print job acquisition request from the pull print application 304 of the printers 105 to 108, and receives a job status in print processing.

  Further, the Web service 303 returns corresponding print job list information in response to a print job list acquisition request from the authenticated printing application of the printers 105 to 108.

  The pull print application 304 of the printers 105 to 108 receives a printer control command and a print instruction command from the authentication print application 302. The authentication print application 302 generates a Web page that can be displayed by the Web browser 301 operating on the client terminals 101 to 103, and sends it back.

  The print job management service 306, the printer management service 305, and the web service 303 are independent programs, and can be arranged in different information processing apparatuses. Each of these programs is arranged in an information processing apparatus connected to a network, and communicates between the programs. It is also possible to place these programs in the information processing apparatus.

  The authentication server 112 includes a user management service 308 that manages user information. This service manages information on users who use the printing system in the storage 311. The storage 311 is also a storage device such as an HDD built in the information processing apparatus of the authentication server, an externally connected HDD, or a network storage.

  The Web application 310 generates a Web page that can be displayed by the Web browser 301 operating on the client terminals 101 to 103, responds to a request from the Web browser 301, and returns the generated Web page. The authorization information management service 309 issues and manages authorization tokens.

  FIG. 4 is a software configuration diagram of the printing system according to the embodiment of the present invention.

  A print job management unit 401 of the print job management service 306 located in the print server 104 manages print job information including information on print data managed by the storage 307. Upon receiving job information and print data acquisition requests from the Web service 303, the print job management unit 401 acquires specified job information and print data from the storage 307 and passes them to the Web service 303. A printer information management unit 403 of the printer management service 305 manages printer information shown in FIG. The execution job management unit 402 manages job information being executed.

  The Web service 303 includes a request reception unit 409, a print status reception unit 408, and a print data acquisition unit 407. The request reception unit 409 receives a print job list acquisition request or print execution request from the authenticated print application 302, a print data acquisition request from the pull print application 304, or a print job status. When receiving various requests, the request reception unit 409 inquires the authentication server 112 about the validity of the authorization token included in the request. When receiving a print execution request, the request reception unit 409 acquires job information from the print job management unit 401 based on information included in the request. Further, at this time, the printer management service 305 registers execution job information in the execution job information of FIG. 5 described later managed by the execution job information management unit 422 based on the printer information included in the request of FIG.

  When the request reception unit 409 receives a print job acquisition request, the print data acquisition unit 407 acquires print data to the print job management service 306 and returns it. When the request reception unit 409 receives the status of the print job, the print status reception unit 408 of the Web service 303 notifies the printer management service 306 of the status.

  The Web application 310 of the authentication server 112 receives a request for authentication from the printers 105 to 108. In the authorization token issuing unit 419, the user information received by the Web application 310 is collated by the user management unit 421, and after the authentication is established, an authorization token is issued.

  The authorization token information management unit 420 manages the authorization token information of FIG. 5 described later including the authorization token issued by the authorization token issuing unit 419. Also, the authorization token information management unit 420 returns whether or not it is valid in response to an inquiry about the validity of the authorization token.

  FIG. 5 is a software configuration diagram of an application operating on the printer according to the embodiment of the present invention.

  The Web service transmission unit 501 of the authenticated print application 302 transmits a print job list acquisition request or a print execution request to the Web service 303. The screen display unit 502 displays a later-described authentication print login screen 700 and an authentication print job list screen 710 on the display unit on the printer.

  The Web application 503 is an application that generates a batch print management screen 720 (to be described later) that can be displayed on the Web browser 301 in response to a request from the Web browser 301 of the client terminals 101 to 103, and sets batch printing. The authentication print controller 504 manages the operation of the entire authentication print application 302, and issues operation instructions to each unit via this controller.

  The Web service reception unit 510 of the pull print application 304 receives a print instruction command, a printer control command, and the like from the authentication print application 302.

  The Web service transmission unit 511 issues a print job acquisition request or print status notification to the Web service 303.

  Upon receiving a print command or the like from the authenticated print application 304, the print data acquisition unit 512 acquires print data from the Web service 303 through the service transmission unit 511 and sends it to the print data transmission unit 513.

  The print data transmission unit 513 transmits print data to the controller 209.

  The print control unit 514 receives the status of the print job from the controller 209 and notifies the Web service 303.

  The pull print controller 515 performs operation management of the entire pull print application 304, and operation instructions to each unit are performed via this controller.

  FIG. 6 is an example of information managed by the printing system according to the embodiment of the present invention.

  The authorization token management information 601 is managed by the authorization token information management unit 420 of the authentication server 112, and includes a user ID for identifying a user, an authorization token issued after the authentication is established, and the like.

  The printer information 602 manages a plurality of printer information of the printers 105 to 108 managed by the print server 104. The printer name, printer identification information, status, and the like are included.

  The printer identification information is information for uniquely identifying each printer, and is an IP address, a MAC address, a URI, or the like. The status is the printer status, out of paper, jammed, cover open, no toner, paper output bin full, hard disk full, other errors, warming up, calibration, initializing, offline, sleeping, printing, printing There are statuses such as possible and unknown.

  The print job information 603 is job management information stored in the storage 307 managed by the print job management unit 401. The print job information includes a job ID for identifying the job, a document name, a print status, and the like. The print status includes statuses such as standby, transfer, printing, canceling, normal end, cancel end, and error end.

  Execution job information 604 is information related to a job that is being printed and received a print instruction, which is managed by the execution job management unit. The execution job information includes an execution job ID for identifying the execution job, an execution user ID, a job ID for identifying the print job information 503 to be printed, printer identification information, and the like.

  Print queue information 605 is print job information managed by the pull print application 304. Information used by the print data acquisition unit 512 when acquiring print data, such as a job ID for identifying a job, a print data acquisition destination URI, and a job execution user authorization token, is included.

  The printer login user information 606 is user information that is currently logged in and managed by the authentication printing application 302. An authorization token issued after the authentication is established by the authentication server 112, a user name, and the like are included, and the authorization token is used at the time of a print job list acquisition request and a print execution request.

  The administrator user information 607 is user information dedicated to batch printing for which batch printing settings have been executed on the batch printing management screen 720 described later. An authorization token, a user name, and the like are included and used as printer login user information when executing batch printing.

  The batch print setting information 608 holds batch print execution schedule information set on a batch print management screen 720 described later, and includes an execution time and the like.

  FIG. 7 is a screen generated by the authentication print application of the printing system according to the embodiment of the present invention.

  The authentication print login screen 700 includes a form 701 for inputting a user ID and password, and when the login button 702 is pressed, the input user ID and password are transmitted to the authentication service 112 to perform authentication.

  The authenticated print job list screen 710 is a screen that is displayed after user authentication is performed on the above-described login screen 700, and acquires a print job list related to the authenticated user from the print server 104 and displays it. The acquired print job list can be selected by a check box 711. When a print job is selected and the print execution button 712 is pressed, a print execution request is transmitted to the print server 104 based on the print job information. Further, at this time, a print execution command is transmitted to the pull print application 302 and the print queue information 605 is registered.

  The batch print management screen 720 is a screen that is displayed when the Web application 503 is accessed from the Web browser 301 of the client terminals 101 to 103. The display of this screen also requires user authentication. Before the screen is displayed, a screen similar to the above-described login screen 700 is displayed and the authentication server 112 authenticates the user. At this time, the authentication information of the authenticated user is stored in the administrator user information 607.

  The batch print management screen 720 displays a time setting form 721 for executing automatic printing, and is held in the batch print setting information 608 when an update button 722 is pressed. The setting of the execution time may be any content that can represent a specific execution timing including hours, minutes, or dates. In addition, an execution history 723 for batch printing is displayed in the execution history.

  FIG. 8 shows an operation flow when the printers 105 to 108 perform authentication printing and an operation flow when batch printing.

  In the authentication print login, the authentication print application 302 first checks in step S801 whether batch printing is currently being executed.

  If it is determined in S801 that batch printing is not being executed, a login screen 700 is displayed in S802.

  When the user information input on the login screen 700 is received in S603, the user information is transmitted to the authentication server 112 in S804, and user authentication is attempted.

  In S805, when user authentication is established in the authentication server 112, an authorization token is received in S806 and stored as printer login user information 606.

  In the print job list acquisition, the authenticated print application 302 transmits a print job list acquisition request including the authorization token stored in the printer login user information 606 to the print server 104 in step S811.

  In step S812, the print job list received as a response to the request in step S811 is displayed as an authentication print job list screen 710. In step S821, the authentication print application 302 transmits a print execution request including the print job information to be executed and the authorization token stored in the printer login user information 606 to the print server.

  In step S822, based on the information included in the reply to the request in step S821, a print execution command is transmitted to the pull print application 304, and the print queue information 605 is registered.

  The print data acquisition is executed in the pull print application 304 when the print queue information 605 is registered with reference to the print queue information 605.

  In step S831, a print data acquisition request including the authorization token stored in the printer login user information 606 is transmitted to the print server 104 based on the contents of the print queue information 605. As a reply in S831, print data is received in S832, and printing is executed in S833.

  The batch print execution is executed according to the execution time registered in the batch print setting information 608. When the execution of batch printing is started, first, in the authentication printing application 302, the information of the administrator user information 607 is stored in the printer login user information 606 in S841.

  By S842, the user dedicated to batch printing enters the state where the authentication printing logins S801 to S806 have been performed.

  In S842, the above-described print job list acquisition S811 to S812, print execution instructions S821 to S822, and print data acquisition S831 to S832 are repeated until the number of print job lists becomes zero.

  Finally, in S843, the execution result of batch printing for displaying the execution history of the batch printing management screen 720 is recorded.

101 to 103 Client terminal 104 Print server 105 to 108 Printer 109 to 111 Network 112 Authentication server

Claims (1)

In a printing system including a client terminal (101 to 103) having a Web browser (301), a print server (104), a printer (105 to 108), and an authentication server (112),
The printer (105-108)
Means for receiving input of user information, transmitting the user information to the authentication server (112), and acquiring authentication information about the user;
Means for acquiring print job information associated with the user by transmitting authentication information about the user to the print server (104);
Means for storing user authentication information and a print execution schedule;
Means for executing printing in accordance with a print execution schedule specified in advance;
Means for controlling not to accept input of the user information during printing according to the print execution schedule specified in advance;
A printing system comprising: