JP2008077355A - Information processor, print system, and transfer control method of print job - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent interruption of others print among two or more print jobs, even when two or more target pull print jobs exist at pull print starting. <P>SOLUTION: An information processor connectable to a print system registers a print job by giving an identification information relevant to a user. If a specific information for choosing a print job for a print target is input, a print job in which the given identification information matches the input specific information is retrieved from the registered print jobs. When two or more print jobs are retrieved, a common identification information is added to these two or more print jobs, and these two or more print jobs are registered into a print queue relevant to the print system of an output destination. When transferring the print job registered into this print queue is permitted, the two or more print jobs to which the common identification information is given are collectively transmitted to the print system. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a network print system in which at least one client and a printing apparatus that receives a print request from the client and executes printing are connected to each other via a network.

  In recent years, network printing systems that output print data created by an information processing apparatus such as a personal computer to a printing apparatus via a network have become common. In such a network print system, print data is transmitted together with a print request from an information processing apparatus as one or more clients connected to the network via the network. The printing apparatus sequentially receives print data, forms an image, and prints it on a medium such as paper. As described above, in the network print system, a print system that makes a print request from the information processing apparatus to the printing apparatus via the network has become mainstream.

  In the system described above, the printing apparatus receives a print request from a plurality of information processing apparatuses connected via the network, so that there are many cases where the discharged printed matter is mixed with the printed matter of another person. This situation becomes a problem particularly when a confidential document or a highly confidential document is printed. In other words, when printing a confidential document, the user must issue a print request while paying attention not to mix it with the prints of others. Further, in order not to leak confidential information, it is necessary to prevent the printed matter discharged from touching the eyes of others. For this reason, after the user operates the information processing apparatus to issue a print request to a printing apparatus connected via a network, the user needs to go to the installation place of the printing apparatus and watch the printing apparatus until it is discharged. is there.

  However, since printing apparatuses connected to the network are shared by a plurality of people, the printing is not started immediately after a print request. For example, if another person's print job has already been registered in the printing apparatus, the printing of the confidential information is awaited until all the print jobs are printed. Therefore, it is necessary for the user to measure the timing of visiting the printing apparatus after a print request, and there is a problem that usability is poor.

In order to solve such problems, Patent Document 1 suggests the possibility of solving these problems by using a pull-type printing system (pull print method). In the pull printing method, printing is not performed according to a print request transmitted from the information processing apparatus to the printing apparatus via the network, but is performed by searching for a document to be printed from the printing apparatus. According to Patent Document 1, a normal print queue and a pull-dedicated print queue (hereinafter referred to as pull print queue) are provided in a gateway, and a print job with no output destination set is queued in the pull print queue. The printing apparatus is provided with a start button for executing a job in the pull print queue. When this button is pressed, the job to be executed and its output destination are transmitted to the gateway. Then, the designated job is transmitted from the pull print queue to the designated output destination and printed.
JP 2004-220354 A

  However, the above-described prior art does not describe a problem that may occur when there are a plurality of print jobs. In an environment in which a printing apparatus is shared by a network, when there are a plurality of print jobs, there is a possibility that another person's print job may interrupt between the plurality of jobs. If you are interrupted by another person's printing, the other person's printed matter will be mixed into the ejected document, so you may accidentally take it or take it by mistake. there is a possibility. As described above, the mixing of confidential documents or highly confidential documents with other people's printed matter creates a possibility that a person who does not have the right to obtain information will acquire information.

  Further, in the above-described conventional technology, since there is only a single print queue, it is difficult to register print jobs for a plurality of groups (users or departments). That is, printing of all print jobs registered in the pull print queue is started when the start button is pressed, so that it is difficult for a plurality of people to use the same pull print queue. Therefore, in order to perform pull printing by a plurality of people, it is necessary to prepare pull print queues for the number of users.

  The present invention has been made in view of the above problems, and an object of the present invention is to be able to print a plurality of print jobs collectively even when there are a plurality of target pull print jobs at the start of pull printing. It is to be. Another object is to prevent another person's printing from interrupting a plurality of print jobs.

In order to achieve the above object, an information processing apparatus according to an aspect of the present invention includes the following arrangement. That is,
An information processing apparatus that can be connected to a printing apparatus,
A first registration means for registering a print job with identification information associated with the user;
An input means for inputting specific information for selecting a print job to be printed;
A search unit for searching for a print job in which the identification information given by the first registration unit corresponds to the specific information input by the input unit from the print job registered by the first registration unit;
When a plurality of print jobs are retrieved by the retrieval unit, common identification information is given to the plurality of print jobs, and the plurality of print jobs are registered in a print queue associated with an output destination printing apparatus. A second registration means;
Transfer means for collectively transferring the plurality of print jobs to a printing apparatus when one transfer of the plurality of print jobs to which the common identification information registered in the print queue is given is permitted; Is provided.

In order to achieve the above object, a printing system according to another aspect of the present invention comprises the following arrangement. That is,
A printing system in which a printing device and an information processing device are connected,
The information processing apparatus is
A first registration means for registering a print job with identification information associated with the user;
Input means for inputting specific information for selecting a print job to be printed from the printing apparatus;
A search unit for searching for a print job in which the identification information given by the first registration unit corresponds to the specific information input by the input unit from the print job registered by the first registration unit;
When a plurality of print jobs are searched by the search unit, common identification information is given to the plurality of print jobs, and the plurality of print jobs are registered in a print queue having the printing apparatus as an output destination. 2 registration means;
A transfer unit configured to transfer the plurality of print jobs to the printing apparatus collectively when the transfer permission is notified from the printing apparatus to one of the plurality of print jobs to which the common identification information is assigned; Is provided.

  According to the present invention, even when a plurality of target pull print jobs exist at the start of pull printing, a plurality of print jobs can be printed together. In addition, it is possible to prevent another person's printing from interrupting a plurality of print jobs.

  Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings.

<System configuration>
FIG. 1 is a block diagram showing an example of the overall configuration of a print system according to an embodiment of the present invention. The print system according to the first embodiment includes clients (computers) 101 to 103 realized by an information processing apparatus and network printers 104 to 105 as printing apparatuses (printer devices). The clients 101 to 103 and the network printers 104 to 105 are communicably connected to each other via a network (LAN) 106, thereby constituting a printing system as a whole.

The clients 101 to 103 store the print control program so that they can be executed.
A function for managing the network printers 104 to 105 in the print system;
-Realize functions for accumulating files used on the network and monitoring network usage.

Regarding printing by pull printing, the clients 101 to 103 execute a print control program, thereby
A function for creating a print job by itself and issuing a schedule request to a scheduler built in or connected to the network printers 104 to 105;
A function of starting transfer of print data according to an instruction from the scheduler of the network printers 104 to 105.
Here, the scheduler may be constructed by operating software on the apparatus, or may be constructed by dedicated hardware.

  The network printers 104 to 105 are printer devices as physical devices that receive print jobs including print data from the clients 101 to 103, analyze the received print jobs, and print. As the network printers 104 to 105, any type of printing apparatus such as a laser beam printer employing an electrophotographic system, an inkjet printer employing an inkjet system, or a printer utilizing a thermal transfer system can be employed.

The network printers 104 to 105 are
A function of accepting print requests from a plurality of clients 101 to 103, determining the order of the accepted print requests, and issuing a print instruction;
A function of monitoring the print job transferred to the network printers 104 to 105 and the status of the network printers 104 to 105 and notifying the clients 101 to 103 of the end of printing and the status of the printer.

  Communication between apparatuses included in the print system may be wired communication using an Ethernet (registered trademark) cable or wireless communication using radio waves or light.

<Client configuration>
FIG. 2 is a block diagram illustrating the hardware configuration of the clients 101 to 103 illustrated in FIG. In FIG. 2, a CPU 200 reads an application program, a printer driver program, an OS, a print control program, and the like stored in an HD (hard disk) 205, loads them into the RAM 202, and executes them. The ROM 201 stores programs such as a basic I / O program, various data such as font data and template data used for document processing. The RAM 202 functions as a main memory or work area for the CPU 200. The RAM 202 stores information, files, and the like necessary for program execution under the control of the CPU 200 on a regular basis.

  An FD (floppy (registered trademark) disk) drive 203 reads a program stored in the FD 204 as a storage medium, and writes data to the FD 204. Note that the clients 101 to 103 may include a drive for accessing another storage medium instead of the FD drive 203 or together with the FD drive 203. As other storage media, any computer-readable storage media such as CD-ROM, CD-R, CD-RW, PC card, DVD, IC memory card, MO, and memory stick can be used.

  The HD 205 is an external storage device that functions as a large-capacity memory, and stores an application program, a printer driver program, an OS, a print control program, a related program, and the like. Furthermore, a spooler for spooling print data is also secured in the HD 205.

  A keyboard 206 is an instruction input device for a user to input device control command instructions and the like to the client computers 101 to 103. A display 207 is a display device that displays commands input from the keyboard 206, the status of the network printers 104 to 105, and the like. In practice, a display instruction is given to the display 207 via an operating system running on the clients 101 to 103. A resource file display instruction is issued to the operating system by the print processing program, and each display described later is realized. A system bus 208 controls the flow of data between the above components in the computers as the clients 101 to 103. The interface 209 connects the clients 101 to 103 to the network. The clients 101 to 103 exchange data with other devices on the network via the interface 209.

<Explanation of memory map>
FIG. 3 is a diagram illustrating an example of a memory map of the RAM 202 illustrated in FIG. 2, and illustrates a memory map in a state in which the print control program is loaded into the RAM 202 and can be executed by the CPU 200.

  A basic I / O program 301 is stored in the RAM 202. The basic I / O program 301 is a program having an IPL (Initial Program Loading) function for starting the operation of the OS by loading the OS from the HD 205 to the RAM 202 when the power of the clients 101 to 103 is turned on. It is. The RAM 202 stores an OS (Operating System) 302, a print control program 303, and related data 304. The work area 305 is an area used when the CPU 200 executes various programs.

  The print control program 303 and related data 304 may be installed in advance from the FD 204 to the HD 205 and loaded from the HD 205 to the RAM 202 for execution, or may be loaded directly from the FD 204 to the RAM 202 for execution. Good. Further, it is possible to store the print control program 303 in the ROM 201, configure it as a part of the memory map, and execute it directly by the CPU 200. In addition, each function can be configured as software instead of a hardware device. By executing the print control program 303, the CPU 200 realizes a function of transferring print data, instructing to change the print destination of the print job, or instructing to change the print order.

  FIG. 4 is a diagram illustrating an example of a memory map of the FD 204 illustrated in FIG. In FIG. 4, 400 is the data content of the FD 204. The data content 400 includes volume information 401 indicating data information, directory information 402, a print control program 403, and related data 404.

<Network printer configuration>
FIG. 5 is a block diagram illustrating a hardware configuration example of the network printers 104 to 105 that can be applied to the print system according to the present embodiment.

  The control system of the network printers 104 to 105 is divided into a network print server 521 and a printer controller 522. In the network print server 521, the network print server CPU 501 mainly communicates with a client connected to the network based on a control program stored in the rewritable Flash ROM 503. That is, it comprehensively controls transmission and reception of various data such as print data and printer control commands transmitted from a plurality of external devices such as clients 101 to 103 connected to the network 106 using a predetermined network communication protocol. Then, data transfer control is performed for the printer controller 522 connected via the expansion interface controller (EXPC) 507. Reference numeral 517 denotes an interface connecting the extended interface controller 507 and the extended interface controller (EXPC) 513.

A RAM 502 is used as a temporary storage area such as a main memory and work area of the CPU 501. The LED 506 is used as a display unit indicating the operation state of the network print server, and various operation states can be indicated by LED blink patterns and colors. As an operation state indicated by the LED 506, for example,
The electrical connection state (LINK) between the network controller (LANC) 505 and the local area network (LAN) 523,
-Network communication mode (10Base, 100Base, full duplex, half duplex) and the like.

  The external I / O interface 519 realizes information exchange with an external device 520 that can be recognized by the network print server 521. Examples of the external device 520 include an ID card reader that reads ID card information, a memory stick that is a portable storage medium, a display auxiliary panel display, and the like.

  In the printer controller 522, the printer controller CPU 508 comprehensively controls access to various devices connected to the system bus 511 in accordance with a control program stored in the ROM 509 and executes various controls. Note that the control program executed by the CPU 508 and the resource data (resource information) referred to when executing various controls may be acquired from the external memory 510 connected via the disk controller (DKC) 515. A raster controller 512 generates output image information based on print data received from a network print server 521 connected via an extended interface controller (EXPC) 513, and outputs an image signal to the print engine 516.

  A RAM 514 functions as a main memory, work area, and the like for the CPU 508. Note that the memory capacity of the RAM 514 can be expanded by an optional RAM connected to an expansion port (not shown). An operation panel (operation unit) 518 includes buttons for operating the network printers 104 to 105 such as operation mode settings and canceling print data, and liquid crystal panels and LEDs indicating the operation status of the network printers 104 to 105. The display part is arranged.

  The print engine 516 shown in FIG. 5 uses a known printing technique, and examples thereof include an electrophotographic method (laser beam method), an ink jet method, and a thermal transfer method (sublimation) method.

<Client software configuration>
Next, the software configuration of the clients 101 to 103 of the print system will be described. FIG. 6 is a diagram illustrating an example of a software configuration in the clients 101 to 103. The arrows between the components indicate how a print job including a drawing command issued from an application is processed. The software configuration shown in each block is executed by the CPU 200 of FIG.

  Normally, when receiving an instruction for printing, an application 601 such as Microsoft Word (registered trademark) generates a series of drawing commands via the OS. The PDL driver 602 receives a drawing command generated via the OS, and generates a print job including a PDL file that can be interpreted by the network printers 104 to 105 based on a series of drawing commands. In the following description, a PDL driver will be described as an example, but the present invention is not limited to this. For example, the present invention can be applied to a printer driver that creates a BDL (Band Description Language) or a compressed bitmap, or a form in which print data is generated by an application and OS without using a printer driver.

  The PDL driver 602 passes the print job to the spooler 603 in order to transmit the print job to the printer device. Here, since the OS is assumed to be Windows (registered trademark), the spooler 603 is a Windows (registered trademark) spooler. However, the OS of the computer to which the present invention is applied is not limited to Windows (registered trademark), and it goes without saying that other OSs can be applied as long as they have a drawing command.

  The spooler 603 takes a procedure of transferring a print job to the job control port monitor 604 selected and instructed by the user via the user interface and transmitting it to the printer device 606 such as the network printers 104 to 105 (arrow a). Hereinafter, the network printers 104 to 105 and the printer device 606 are synonymous. Here, the description will proceed assuming that the user has designated the job control port monitor 604 for transferring print data to the job control print service 605 and instructed printing in advance. In addition, print setting information such as a paper size and a stapling instruction set via the printer driver interface is also transmitted to the job control port monitor 604. The job control port monitor 604 transmits a print job to the job control print service 605 (arrow b).

  In addition, in the clients (computers) 101 to 103, the job registration application 609 of another client 608 can input print data to the job control print service 605 via the API 610 (arrow g).

  The job control print service 605 has a function of managing the transferred print job and device status. Further, it also has a function of managing information such as a device state and a job state notified from the printer device 606, and issuing a predetermined command to the printer device 606. This corresponds to a function for managing device information and job information of a plurality of network printers 104 to 105. Before sending the print data to the printer device 606, a print request is issued to the print job order management function of the printer device 606 (arrow c). When the execution order of printing has arrived based on the order management function of the printer device 606, print data is transmitted to the printer device 606 (arrow e) according to a print instruction (arrow d) from the printer device 606. Upon confirming the completion of the print data, the printer device 606 notifies the job control print service 605 of a print completion notification (arrow f), and notifies the status of the printer device 606 (arrow f).

  The print manager 607 is a program that provides a user interface for the user to check the state of the print job in the job control print service 605 and to operate the print job. The print manager 607 exchanges information and instructions with the job control print service 605 via a software interface (API: Application Program Interface) of the job control print service 605.

  The print manager 607 mainly has a function of acquiring status information of the network printers 104 to 105 managed by the job control print service 605 as an event. Event notification types include warnings when the amount of toner is low, communication failure between the client and the device, memory shortage, full output tray, and other error / warning information notifications. Notification of normal information is assumed. The job control print service 605 has a function of receiving notification of statuses such as a power control state and failure information (paper jam) during printing of each device (printing apparatus) that can communicate via the network. Further, the print manager 607 issues an event specifying a device to the job control print service 605. The job control print service 605 recognizes the device status based on the issued event and notifies the print manager 607 of the monitoring result.

<Flow of print jobs from client to printer device>
Next, the flow of a print job from the application 601 to the printer device 606 will be described with reference to FIG. Here, the same reference numerals are assigned to the same software configurations as those in FIG. 6, and the functions thereof will not be described in detail.

  As illustrated in FIG. 7, conceptually, a PDL driver 602, a spooler 603, and a job control port monitor 604 are prepared for each printer device 104 to 105. When the OS is Windows (registered trademark) Windows (registered trademark), these may be collectively referred to as a Windows (registered trademark) print system 700.

  The job control print service 605 includes a number of print queues 701 and 701A and output ports 702 and 702A corresponding to the network printers 104 to 105. Further, a pull print queue 705 and a pull print port 706 which are features of the present embodiment are provided. Note that the print queue and output port of the job control print service 605 correspond to the number of connected printer devices, and are not limited to two. These print queues 701 and 701A, output ports 702 and 702A, and pull print port 706 have tables as shown in 1401 and 1402 in FIG. 14 described later, respectively, and are managed by the job control print service 605.

  The output ports 702 and 702A are associated with IP addresses of corresponding printing apparatuses or names used in name resolution (DNS: Domain Name System). Based on the IP address or name, the job schedule request destination and job transmission destination are specified, and the job is transmitted (output). Also, no job transmission destination is set in the pull print port 706, and no job transmission is performed.

  When printing, the application 601 designates a printer and issues a print instruction. A print job generated by the PDL driver 602 based on this print instruction is transferred from the job control port monitor 604 to the job control print service 605. The job control print service 605 first holds the passed print job information in the print queue 701 and instructs the output port 702 to accept the print job. When receiving a job to be printed, the output port 702 issues a schedule request to a scheduler (to be described later) of the printer device 606 corresponding to the IP address set to the output port. The scheduler of the printer device 606 performs scheduling processing for jobs received from a plurality of job control print services 605 based on its own scheduling function, and issues a print instruction (job transmission permission) to the output port 702. . The output port 702 that has received the print instruction transmits print data to the printer device 606.

  When printing is instructed by specifying the pull print port 706, the print job is registered in the pull print queue 705 and is retained in the pull print port 706. When a pull print request described later is received from the printer device, the print job specified by the received information is requeued to the print queue specified by the received information, and the print job is output from the corresponding output port. To do. Note that the re-queueing means that a job queued in the pull print queue 705 is queued in the print queue (701 or 701A).

<Network printer software configuration>
FIG. 8 is a block diagram illustrating a software configuration for realizing each control function in the network print server 521 and the printer controller 522 in the network printers 104 to 105. Each control function is realized by the CPU 501 and 508 executing a control program.

  The operating system 801 controls basic data input / output control of the network print server 521. In the operating system 801, the file system 805 performs input / output control with the program / data storage unit 808. The extension interface driver 807 controls communication with the printer controller 522 via the printer controller 522 and the extension interface 517. The network interface driver 806 communicates with external devices such as the clients 101 to 103 via a communication medium of a local area network (LAN 106).

An application program interface (API) 802 provides various functions of the operating system to an application program operating on the network print server 521. Examples of application programs that operate on the network print server 521 include a user application 803 and a management application 804. The management application 804 registers and manages network printers 104 to 105 and user applications. Examples of functions provided by the application program interface 802 include
A data transfer API that provides a print data transmission / reception function,
A resource control API for performing input / output control of resource data such as bitmap images and display messages,
A printer control API for controlling restart of the network printers 104 to 105, initialization of setting values, setting, etc.
-Job control API that controls cancellation of print jobs, reprint instructions, etc.
A print server control API for restarting the network print server 521, initializing and setting setting values, and starting, registering, and deleting application programs.

  The operating system 812 of the printer controller 522 controls various processing controls in the printer controller 522. The operating system 812 includes a print engine control unit 814 that controls communication with the print engine 516 and a file system 815 that performs input / output control with the model-dependent resource / program storage unit 816. The model-dependent resource / program storage unit 816 stores model-dependent resources such as bitmap images and error messages referenced from the network print server 521, model-dependent application programs that operate on the network print server, and the like.

The extension interface control unit 813 controls communication with the network print server 521 via the extension interface 517. Further, the extended interface control unit 813 transfers the command requested from the network print server 521 to the operating system 812 via various logical interfaces, and returns the processing result to the network print server 521. As a logical interface provided in the extended interface control unit 813,
-Data transfer logical interface that controls the input and output of print data for each control type,
A resource control logic interface for controlling input / output of various data stored in the model-dependent resource / program storage unit 509;
A printer control logic interface for controlling the restart of the network printers 104 to 105, initialization of setting values, setting, etc.
A job control logical interface that controls cancellation of print jobs, reprint instructions, and the like.

  An authentication information reading device 820 connected by a USB control unit 818 and a USB cable is a specific example of the external I / O interface 519 and the external device 520 in FIG. The USB control unit 818 can acquire authentication information from the authentication information recording medium 821 via the authentication information reading device 820.

  In the network control unit 811, the network interface driver 806 receives notifications from the clients 101 to 103 via the LAN 106. The network control unit 811 can determine which client the communication is from and can control the communication. The LPD / RAW 810 is a module that controls a protocol that accepts print data transmitted by a client, and has a function of passing the accepted print data to the printer controller 522.

  Further, the user stores the control program of the application 803 in the model-dependent resource / program storage unit 816 of the printer controller 522 or the program / data storage unit 808 of the network print server 521. When the network printers 104 to 105 are activated, the license held by the application stored in the storage unit 808 or 816 and the license held by the license storage units 809 and 817 are compared. If the licenses match as a result of the comparison, the application program is determined to be an appropriate application program, and the application program is loaded into the RAM 502 of the network print server 521.

<Application software configuration of network print server>
Next, a software configuration of the device scheduler and pull print agent that realizes pull printing according to the present embodiment will be described. These software are a part of the user application 803 and have a scheduling function of the print system and a function of managing print jobs received from the clients 101 to 103. FIG. 9 is a block diagram illustrating functional configurations of the device scheduler 900 and the pull print agent 906 according to the present embodiment.

  In the device scheduler 900, the communication connection management unit 901 manages the connection status of the clients 101 to 103 and information to be notified to the clients. The communication connection management unit 901 manages connected clients using the client information 2002 and the client management queue 2001 shown in FIG. The communication connection management unit 901 communicates with the client via the data transfer API of the application program interface 802 and the network interface driver 806.

  The schedule management unit 902 includes a job management unit 903 and a device management unit 904, and schedules print jobs received from the clients 101 to 103. The job management unit 903 manages schedule requests issued by the clients 101 to 103 and jobs executed by the clients 101 to 103 (sending print jobs). The job management unit 903 manages job information 2102 printed by the client in the job management queue 2101 (FIG. 21). The device management unit 904 receives the printer status of the printer controller 522 and the received print job status from the printer controller 522 via the event handler 905. The device management unit 904 notifies the communication connection management unit 901 and the job management unit 903 of the event received from the printer controller 522.

  In the pull print agent 906, the USB management unit 907 acquires authentication information (job information and the like) via the USB control unit 818 and passes it to the server communication unit 908. The device management unit 909 acquires device address information and the like and passes them to the server communication unit 908. The server communication unit 908 acquires job specifying information based on the acquired authentication information and transmits the information to the job control print service 605.

<Outline of printing system operation (activity diagram)>
FIG. 10 is an activity diagram showing a schematic operation of the printing system according to the present embodiment. An outline of the operation of the printing system according to the present embodiment will be described with reference to FIG.

  First, in step S1001, tasks of the pull-pull print agent 906 and the device scheduler 900 are initialized. In the initialization process, the device scheduler 900 registers an event to be notified to the printer controller 522 in step S1002. This is to notify a registered client (device scheduler 900) of a job status change when a job is processed in the print engine, or a device status change such as an error such as a printer jam or cover open. belongs to. When the initialization process is completed, the pull print agent 906 and the device scheduler 900 enter an event waiting loop.

In step S1003, when the pull print agent 906 detects that the authentication information recording medium 821 has been inserted into the authentication information reading device 820, the pull print agent 906 reads the authentication information recorded on the authentication information recording medium 821. Then, job specifying information for specifying a job is obtained based on the authentication information. As a method of obtaining job specific information,
A method of using the information written in the authentication information storage medium 821 as it is, or
A method for obtaining an authentication server for authentication, transmitting information written in the authentication information storage medium 821, and obtaining job specifying information from the authentication server, etc.

  In step S1004, the pull print agent 906 acquires device configuration information via the printer controller 522. The configuration information acquired here includes consumable information such as the remaining amount of paper and the presence / absence of toner, and device information such as whether or not the duplex unit and the staple device (finisher) can be used. Further, the device network address and the like can be included in the device configuration information.

  In step S1005, the pull print agent 906 notifies the job control print service 605 of the job identification information acquired in step S1003 and the device configuration information acquired in step S1004. This notification is defined as a print start notification. Note that this print start notification may include either job specifying information or device configuration information. Upon receiving the print start notification, the job control print service 605 selects a printable job from the job identification information and device configuration information. This process will be described later with reference to FIGS. 17A and 17B.

  In order to execute printing, the job control print service 605 first performs event registration and job schedule reservation in step S1006. This event registration is the same as step S1002 described above. Schedule reservation will be described later with reference to FIG. 17A. In step S1007, the schedule is received. The processing when receiving the schedule UP will be described later with reference to FIG. Upon receiving the schedule UP in step S1007, the job control print service 605 transmits the corresponding job to the printer controller 522 in step S1008 (strictly speaking, the job is transmitted to the LPD / RAW 810). The processing at the time of job transmission will be described later with reference to FIG.

<Job registration sequence in the job control print service>
FIG. 11A is a flowchart showing processing until a job generated by the application 601 is registered in the job control print service 605 as a pull print job.

  In step S1101, the application 601 generates a job. Next, the application 601 issues a print instruction by designating a printer. In step S1102, the print job generated by the PDL driver 602 is transferred to the job control port monitor 604 based on the print instruction. The job control port monitor 604 acquires job identification information in step S1103, and embeds the job identification information in the print job in step S1104. Specifically, the job identification information is written in the job information 1402 in FIG. This job identification information is information corresponding to the job identification information acquired in step S1003 in FIG. 10, and is input by the user using a GUI (Graphic User Interface) 1201 as shown in FIG.

  FIG. 12 is a diagram illustrating an example of a GUI for a user to input job identification information as job specifying information. When the user selects whether or not to register job identification information when issuing a print instruction, that is, whether or not to perform pull printing, a window 1201 is opened when the user selects pull printing. In window 1201, the embedding candidate list 1205 displays job identification information that is actually embedded in the print job. As shown in the job information 1402 in FIG. 14, a plurality of job identification information can be embedded in one print job. Therefore, a user who can obtain job specifying information corresponding to any of the job identification information can perform pull printing of the print job. The registration list 1203 is an example of a display for improving usability, and job identification information registered in the past is displayed as a list. By selecting desired job identification information from the registration list 1203, the user can easily register the job identification information. The registration list 1203 may be automatically displayed depending on the authority of the user. Further, the user can freely input and register job identification information using the registration button 1202. By pressing a job embedding button 1206, job identification information is embedded in the print job.

  Note that FIG. 12 is an example. For example, an attribute called the number of times of pull printing may be added to the job identification information so that the number of times that a single print job can be printed can be set. In the present embodiment, basically, one pull printing is possible for one job identification information, and an interface for setting the number of times of pull printing is not shown. Note that the job identification information stored in the authentication information recording medium 821 may be acquired from the authentication information reading device 820 connected to the clients 101 to 103, and this may be used as job identification information to be embedded. In this way, job identification information is automatically acquired from the authentication information recording medium 821 and embedded in the print job. Therefore, there is no need to set job identification information using a GUI as shown in FIG. .

  When the job identification information is embedded in the print job, the process proceeds to step S1105, and the job status of the job information 1402 is set to “stop”. In step S 1106, the job whose status is “stopped” is retained in the pull print queue 705. The pull print queue 705 is the same as the print queue 701 described above, but the output port to the corresponding printer is not set.

  As a method for registering a job in the job control print service 605, there is a method for registering a job from the job registration application 609 in addition to a method for registering from the application 601. In this case, the job registration application 609 may exist on a different client PC from the job control print service 605.

  FIG. 11B is a flowchart for explaining a job registration procedure from the job registration application 609. In order to register a job from the job registration application 609, first, in step S1107, a job through the PDL driver is created, and the job created from the job registration application 609 is selected. In step S1108, job identification information of the selected print job is acquired from the job registration application 609. This job identification information is information corresponding to the job identification information acquired in step S1003 in FIG. 10, and can be set by the user using the GUI of FIG. 12, for example, as in step S1103. In step S1109, the job identification information is embedded in the print job. Details of the process for embedding the job identification information in the print job will be described later. In step S1110, the job status is set to “stop”. In step S 1106, the job is retained in the pull print queue 705 of the job control print service 605 via the API 610.

<Job identification from pull print agent (print start notification)>
FIG. 13 is a flowchart illustrating a process in which the pull print agent 906 detects authentication information and notifies the job control print service 605 of information necessary for pull printing from the authentication information recording medium 821 (print start notification).

  In step S1301, the pull print agent 906 checks whether the authentication information reading device 820 has detected a change in the state of the authentication information recording medium 821. For example, when the authentication information reading device 820 is a card reader, the state change of the authentication information recording medium 821 is detected as a state change when a card is inserted. When the authentication information recording medium 821 is detected by a sensor in the authentication information reading device 820, a change in the presence of the authentication information recording medium 821 is detected as a change in state. Also, in the case of a biometric authentication device that performs authentication by holding a hand or the like over the authentication information reading device 820, the state change may be that the biometric to be authenticated is detected as described above.

  If a change in the state of the authentication information recording medium 821 is detected, it is checked in step S1302 whether authentication information exists in the authentication information recording medium 821, and if it exists, the authentication information is acquired. In step S1303, the pull print agent 906 acquires job specifying information based on the acquired authentication information. As a method for acquiring the job specification information, for example, information written in the authentication information storage medium 821 may be used as it is, or the authentication information is transmitted to a separately provided authentication server, and the job specification is performed from the authentication server. Information may be obtained. If the job identification information cannot be obtained, the process is terminated, and the user is notified that the format of the authentication information storage medium is invalid. As means for this notification, means for displaying as a character string on the LED section of the printer, means for notifying by sound when there is a mechanism for generating a BEEP sound, means for printing an error message, and the like are conceivable.

  When the job specifying information is obtained, in step S1304, a device address for specifying the device and device configuration information are acquired from the device. The configuration information includes consumable information such as the remaining amount of paper and the presence / absence of toner, and device information such as the availability of the duplex unit and the stapler (finisher).

In step S1305, the destination of the job control print service 605 is acquired. As a means for acquiring the destination of this job control print service 605,
-A method of storing the information in the authentication information storage medium and specifying the authentication information at the time of acquisition,
・ A method to obtain job specific information from the authentication server at the same time,
A method of storing a fixed destination in the pull print agent and using the destination is conceivable. In the present embodiment, a description will be given using a method of specifying when authentication information is acquired.

  In step S1306, the acquired job specification information, device address, and device configuration information are notified to the acquired destination job control print service 605.

<Schedule Registration by Job Control Print Service 605 by Print Start Notification>
FIG. 14 is a diagram showing job information 1402 held in the pull print queue and a job management queue 1401 for managing a plurality of generated job information 1402 in the job control print service 605 of the clients 101 to 103.

  The job information 1402 is print job information added to a schedule request issued by the clients 101 to 103 to start printing. The job information 1402 includes the document name of the print job, the job ID issued by the job management unit 903, the user name that started printing on the client, the number of pages of the job, and the job status indicating the status of the print job. In the job information 1402, the job data ID included in the print data transferred by the clients 101 to 103 and the IP address of the printed client are also registered. Note that some of the items in the job information 1402 also include response information from the scheduler in response to a schedule request issued from the clients 101 to 103 to the scheduler. For example, the job ID issued by the job management unit 903 is response information from the scheduler corresponding to the schedule request. Therefore, for example, the job ID issued by the job management unit 903 has not been set yet when the schedule request is issued by the job control print service 605.

  The job status represents a status from when the client 101 to 103 issues a print schedule request until the job disappears from the printer, and is in a print standby state, in a schedule UP state, in a transfer state, in a transferred state, or in a print complete state. Exists. The job data ID is an ID of a job included in the print data, and is an ID added when a job status is notified in the printer controller 522. As described above, one or a plurality of job identification information is registered.

  The job management queue 1401 is a management queue that manages a plurality of job information 1402. When the job control print service 605 receives a print job from the job control port monitor 604 or the like, the job control print service 605 registers the job information 1402 in the management queue 1401. In addition, when a print end notification of a print job is received from the printer device 606, the corresponding job information is deleted.

  FIG. 15 shows information on print queues and output ports managed by the job control print service 605. The printer information 1501 represents information about each printer managed by the job control print service 605, and includes information such as a printer name. The port information 1502 represents information of each output port managed by the job control print service 605, and includes information such as an IP address of a device to be printed.

  FIG. 16 is an information table attached to a print start notification transmitted to the job control print service 605 by the pull print agent 906 that has detected the authentication information recording medium 821 by the authentication information reading device 820 and acquired the job specifying information. is there. The contents of the information table 1601 are a device address, job specifying information, and device configuration information.

  FIG. 17A shows a flow from when the job control print service 605 of the client receives a print start notification (job identification information or the like) from the pull print agent 906 until the corresponding print job is registered in the scheduler.

  In step S1701, the device address, job identification information, and device configuration information are acquired from the pull print agent 906 (information table 1601 is acquired). In step S1702, a print queue (701 or 701A in this example) that matches the acquired device address is specified. In step S1703, the print job held in the pull print queue 705 managed in the job control print service 605 is checked, and the print job to be output is specified from the received job specifying information.

  Details of the job specifying process in step S1703 will be described with reference to the flowchart of FIG. 17B.

  In step S1801, job identification information is acquired from the information acquired in step S1701. In step S1802, all jobs in the pull print queue managed in the job control print service 605 are sequentially searched. In step S1803, it is determined whether or not all searches are completed, and the processes in steps S1804 to S1807 are repeated until all searches are completed. If the search for all jobs in the pull print queue is completed, the process advances from step S1803 to step S1808.

  In step S1804, job information 1402 corresponding to each print job is searched, and one or a plurality of job identification information included in each job information is compared with job specifying information acquired from the pull print agent 906. If there is no job identification information that matches the job identification information, the process returns to step S1803 to target the next job information. If there is job identification information that matches the job identification information, the process advances to step S1805 to check whether a plurality of job identification information is registered in the job information 1402. If single job identification information is registered, in step S1806, the searched print job is registered in the print registration candidate list, and the process returns to step S1803. On the other hand, if a plurality of job identification information are registered, the process advances to step S1807 to extract the matched job identification information, duplicate the print job, and extract only the job identification information extracted in the job information 1402 of the duplicated print job. Embed. In step S1806, the copied print job is registered in the print registration candidate list.

When all searches for print jobs in the pull print queue have been completed, in step S1808, when (A) is 0 jobs, (B) is 1 job, (C) If there are more than one, the process branches.
(A) In the case of 0: In step S1809, an error (that there is no registered job) is returned to the pull print agent 906, and the process ends.
(B) If the number is one: In step S1810, the process proceeds to a process for registering a print job in the print registration candidate list (requeueing: the process in S1704).
(C) If there are a plurality of print jobs: In step S1811, all the print jobs are grouped into one group, and a group job ID is registered in the job information 1402. A different group job ID is set for each group. In the present embodiment, consecutive numbers are simply assigned as group IDs. In step S1812, registration processing (requeueing: processing in step S1704) of the first print job in the print candidate list is started.

  With the above processing, the jobs in the print registration candidate list include single job identification information and the same group ID when a plurality of jobs exist. An example of such job identification information is shown at 1403 in FIG.

  Returning to FIG. 17, in step S <b> 1704, all accepted print jobs are requeued to the print queue 701 (or 701 </ b> A) specified in step S <b> 1702 and deleted from the pull print queue 705. The job control print service 605 registers the information of the requeued print jobs in the job management queue of the print queue 701 (or 701A).

  In step S1705, the job control print service 605 connects to the device scheduler 900 and issues a connection request command. When the client issues a connection request, the client information 2002 is registered in the client management queue 2001 of the device scheduler 900, and thereafter, information can be exchanged between the client and the device scheduler 900. In step S1706, the job control print service 605 registers a job event and a device event in the device scheduler 900. When the job event is registered, the device scheduler 900 notifies the client of a change in the status of a job printed by the own client or a job printed by another client. When a device event is registered, a change in the state of the printer device 606 is notified.

  In step S1707, a list of jobs registered in the job management queue 2101 managed by the device scheduler 900 is acquired. With this job list and job event, it is possible to grasp the print status of a job managed by the device scheduler 900.

  With the above processing, preparation for printing is completed, and the job control print service 605 registers all jobs to be printed in the device scheduler 900 in step S1708 and requests a schedule. In response to the schedule request, a job ID issued by the job management unit 903 is returned from the scheduler and set as job information 1402. Thereafter, the process returns to step S1704 and waits for the next instruction (schedule UP).

<Start printing with schedule UP>
When the job control print service 605 receives a schedule UP command from the device scheduler 900 after finishing the schedule request as described above, the job control print service 605 transmits a corresponding print job (print data) to the printer device 606. Hereinafter, processing when the job control print service 605 receives the schedule UP will be described with reference to the flowchart of FIG.

  This process is divided depending on whether or not a group job ID is set in the job information 1403 registered in the print queue 701 (or 701A). If the group job ID is not set (A), the process proceeds to step S1710. If the group job ID is set (C), the process proceeds to step S1714.

(A) A group job ID is not set for a print job.
When a schedule UP command is received from the device scheduler 900 in step S1709A, the process proceeds to step S1709B. In step S1709B, the job control print service 605 checks whether a group job ID is set in the job information 1403 of the print job. If not set, the process proceeds to step S1710.

  In step S1710, the job control print service 605 starts transferring the print job that has received the transfer instruction. When transmission of print data is started, a transfer start state is notified in step S1711 to notify the device scheduler 900 that transfer has started. In step S1712, when the transfer of the print data is completed, in step S1713, the device scheduler 900 is notified that the transfer has been completed.

(B) When a group job ID is set for a print job On the other hand, if a group job ID is set for the job information 1402 of the print job specified by the schedule UP, the process advances from step S71709B to step S1714. In step S <b> 1714, the job control print service 605 checks whether the same group job ID is set in the job information 1402 for all jobs registered in the job management queue 1401. Then, all jobs having the same group job ID are selected. In step S1715, transfer of all selected print jobs is started. At this time, the job control print service 605 transfers all the print jobs in the same session using the RAW protocol. That is, a plurality of print jobs having the same group ID are transferred in a batch.

  In step S1716, the device scheduler is notified that transfer of all print jobs has started. Until the transfer of all print jobs having the same group ID is completed in step S1717, the processes in steps S1718 and S1719 are executed. That is, in step S1718, every time job transfer ends, the process proceeds to step S1719, and a transfer end notification of the print job transferred in step S1719 is transmitted to the device scheduler 900.

  In this way, when all the print jobs having the same group ID are transmitted in the same session and the network printer can accept the transfer of the print job for only one session, the printing of the other person interrupts between the print jobs. Can be prevented. In addition, if the network printer allows multiple sessions at the same time, it is possible to prevent other people from interrupting printing by setting up a temporary session that does not send print data and printing only one session. It is. Alternatively, it is possible to prevent another person's printing interruption by providing a function that allows the network printer to set the one-session mode.

  As described above, when the RAW protocol is used, it is possible to prevent interruption of a print job by another person by transmitting the print job in a batch by the above-described method. On the other hand, when a print job is transferred using the LPD protocol, batch printing is performed by transmitting the start and end of LPD transmitted for each print job only at the start of the first print job and at the end of the last print job, respectively. Job transmission can be realized. By sending such batch print jobs, it is possible to execute printing of a plurality of print jobs having the same group ID without being interrupted by others.

<Other processing in the job control print service>
FIG. 19 is a flowchart for explaining the processing flow of the job control print service 605 when a notification or command is received from the device scheduler.

  In step S1901, it is determined whether the data received from the device scheduler 900 is a job event notification or a job list return. If it is a job event, the process proceeds to step S1902, and if it is a job list, the process proceeds to step S1908. In step S1908, when the job list is returned, the job information obtained from the job list is set in the job management queue 1401 managed by the job control print service 605.

  In step S1902, it is determined whether the job event notification notified from the device scheduler is a job completion notification or a job status change notification. If it is a job status change notification, the job status of the corresponding job information is updated in step S1909. In step S1902, if the received event notification is a job completion notification, the process advances to step S1903. In step S1903, the job control print port 605 deletes the corresponding job information from the job management queue 1401.

  In step S1904, it is confirmed whether or not the job of the own client that has not finished printing remains in the job management queue 1401. If it remains, since it is still necessary to exchange with the device scheduler 900, the process proceeds to step S1901 in order to continue the connection with the device scheduler. If it is determined in step S1904 that there is no job of the own client, the process proceeds to step S1905, and a process for terminating the connection with the device scheduler 900 is started. That is, in step S1905, when connection is started, the device scheduler 900 is requested to cancel registration of the registered job event and device event. In response to this request, the device scheduler 900 deletes the event registration contents of the client information. Without this event registration information, no event is notified even if the status of the job managed by the device scheduler 900 changes. In step S1906, a disconnection request is issued to the device scheduler 900. When the device scheduler 900 receives the disconnection request, the corresponding client information is deleted from the client management queue. In step S1907, a process for disconnecting the session with the device scheduler 900 is performed, and the process waits in step S1901.

<Client and job management by device scheduler>
FIG. 20 illustrates a client management queue 2001 that manages the client information 2002 of the connected job control print service 605 and a plurality of client information 2002 managed by the communication connection management unit 901. The client information 2002 includes information such as the client ID assigned by the communication connection management unit 900 for each connected client, the IP address of the job control print service 605 to be connected, and the type of event registered by the connected client. Here, the event type represents the type of device status event or job status event issued by the printer controller 522. The client management queue 2001 holds client information of the connected job control print service 605 in a queue format. When a session with a client is started, the information of the corresponding client is registered in this management queue, and when disconnected, the corresponding client information is deleted.

  FIG. 21 is a diagram showing job information to be added to a schedule request issued by the job control print service 605 for printing, a job management queue 2101 for managing job information 2102, and a plurality of generated job information.

  The job information 2102 is print job information added to a schedule request issued by the job control print service 605 to start printing. This job information 2102 includes the document name of the print job, the job ID issued by the job management unit 903, the name of the user who started printing on the client, the number of pages of the job, and the job status indicating the status of the print job. Further, in the job information 2102, the job data ID included in the print data transferred by the job control print service 605 and the IP address of the printed client are registered. The job status represents the status from when the job control print service 605 issues a print schedule request until the job disappears from the printer, and is in print standby, schedule UP status, being transferred, transferred, and printing completed. There exists a state such as. The job data ID is an ID of a job included in the print data, and is an ID added when a job status in the printer controller 522 is notified.

  The job management queue 2101 is a queue for managing a plurality of job information 2102. When a schedule request from the job control print service 605 is received, the job information 2102 is registered in the job management queue 2101. When the print job is finished printing, the corresponding job information 2102 is deleted.

<Outline of pull print operation in print system>
FIG. 22 is a diagram for explaining exchanges from when the job control print service 605 of the clients 101 to 103 receives a job to issue a schedule request to the printer device 606 until printing ends at the printer device.

  When receiving the print data, the job control print service 605 starts session connection with the device scheduler 900. The job control print service 605 then registers an event for notifying the device scheduler 900 of a connection request for notifying client information and a job / device status. In addition, the job control print service 605 issues a job list acquisition command for acquiring information on jobs that the device scheduler 900 schedules.

  When the device scheduler 900 accepts a connection request, it registers the client information 2002 in the client management queue 2001, and when accepting event registration, it sets it as a registration event of the corresponding client information. When a job list request is received, a list of job information registered in the job management queue 2101 is transmitted.

  Next, the job control print service 605 issues a schedule request command for reserving printing. Upon receiving the schedule request, the device scheduler 900 registers the job information 2102 in the job management queue 2101. When there are a plurality of jobs having the same group ID, the print data transfer indicated by 2201 in FIG. 22 sequentially transfers the print data corresponding to all of the plurality of jobs in one TCP / IP session. To go. Also, when the transfer start notification and transfer end notification correspond to the start and end of LPD, the transfer start notification is notified at the start of the transfer of the first data of a plurality of print jobs, and the transfer end notification is the data of the last print job. Notified when transfer ends. Information such as a document name is set in the job information 2102. When the device scheduler 900 determines that the printer device 606 can accept print data, the device scheduler 900 issues a schedule UP and prompts the job control print service 605 to start sending print data. The determination that the print data can be received will be described later. When the device scheduler 900 issues a schedule UP, the device scheduler 900 updates the job status of the job information 2102 to the schedule UP status.

  Upon receiving the schedule UP, the job control print service 605 starts transferring print data to the LPD / RAW 810. When the job control print service 605 starts transferring the print data, the job control print service 605 notifies the device scheduler 900 of the transfer start. Upon receiving a transfer start notification from the job control print service 605, the device scheduler 900 updates the job status in the job information 2102 to a status that is being transferred.

  When the LPD / RAW 810 receives the print data, the LPD / RAW 810 transfers the print data to the printer controller 522 and starts printing by the printer controller 522. When printing starts, the printer controller 522 notifies the device scheduler 900 of the job status. The device scheduler 900 notifies the client of the print status of the job based on the registration information of the client information.

  When the job control print service 605 finishes transferring the print data to the LPD / RAW 810, it sends a transfer end notification to the device scheduler 900. Upon receiving the transfer end notification, the device scheduler 900 updates the job status of the job information to the transferred status.

  When the printer controller 522 finishes the printing process, it notifies the device scheduler 900 of a print completion notification. The device scheduler 900 notifies the client of the job printing completion status based on the registration information of the client information. The job control print service 605 confirms that processing of all print jobs having the same group ID is completed by this notification. Since notification from the device is no longer necessary, an event notification registration cancellation request from the device scheduler 900 is issued. The device scheduler 900 that has received the event cancellation request sets information not to notify the event to the registration event of the client information.

  Thereafter, the job control print service 605 issues a disconnection request for ending the connection with the device scheduler 900 and ends the session. When the device scheduler 900 receives the disconnection request, the device scheduler 900 deletes the corresponding client information from the client management queue and ends the process with the client.

  FIG. 23 is a flowchart for explaining processing of the schedule management unit 902 of the device scheduler 900 from when a schedule request is received from the job control print service 605 to when a schedule UP is issued.

  In step S2301, upon receiving a notification from the job control print service 605, the schedule management unit 902 determines whether the notification is a notification of a schedule request or a notification of a transferred state. If it is a notification of a schedule request, the process proceeds to step S2302. In step S2302, the schedule management unit 902 creates job information in which the job ID issued by the job management unit 903 is set, and sets the information added to the schedule request as job information. The job information is registered in the job management queue in the order in which the schedule requests are received.

  In step S2303, the job status of the job information registered in the job management queue is confirmed. If the job status is schedule UP and there is a job that is being transferred, the process is returned to step S2301 because an instruction to transfer print data to an existing client is given. If the job status is schedule UP and there is no job being transferred, there is no plan to send print data from the job control print service 605, so the process shifts to step S2304 to prepare for issuing the schedule UP.

  In step S2304, the job management queue 2101 confirms jobs in the order in which the schedule request is first received, and determines whether there is a job waiting for the schedule. If there is no job waiting for the schedule, the process returns to step S2301. If a job waiting for a schedule is found, the process proceeds to step S2305. In step S2305, a schedule UP for starting transfer of print data is notified to the corresponding client. In step S2306, the job status of the corresponding job information is updated to the schedule UP status, and the process proceeds to step S2301.

  FIG. 24 shows processing of the job management unit 903 for accepting a job status notification event from the device management unit 904 and accepting a job list request from the job control print service 605.

  In step S2401, upon receiving a notification from the communication connection management unit 901 or the device management unit 904, it is determined whether the job status notification is from the device management unit 904 or a job list request from the job control print service 605. . If it is a job status notification from the device management unit 904, the process proceeds to step S2402, and the job status of the corresponding job information is updated. In step S2403, it is determined whether the communicated job status is a notification of printing completion. If the printing is not completed, in step S2404, the communication connection management unit 901 is notified to issue a job status event to the client. If it is determined in step S2403 that printing has been completed, the process proceeds to step S2405. In step S2405, the corresponding job is deleted from the job management queue 2101. In step S2406, the communication connection management unit 901 is notified to issue a job completion event to the client. Then, the process returns to step S2401.

  On the other hand, if the received notification is a job list request from the job control print service 605 in step S2401, the process advances to step S2407. In step S2407, the communication connection management unit 901 is notified of the list of job information registered in the job management queue 2101 and is transmitted to the requesting client.

  FIG. 25 is a flowchart for explaining processing of the device management unit 904 that receives a device status or job status notification from the printer controller 522 via the event handler 905 and notifies the job management unit 903 or the communication connection management unit 901. .

  When the device scheduler 900 is activated, the device management unit 904 performs event registration processing for the printer controller 522 via the event handler 905 in step S2501. When the event registration changes the status of the device or the status of the print job processed by the printer controller 522, the printer controller 522 notifies the device scheduler 900 (device management unit 904) of the status. .

  When the event generated by the printer controller 522 is received via the event handler 905, the device management unit 904 determines whether the event is a job event or a device event in step S2502. If it is a job event, in step S2503, the job event is notified to the job management unit 903, and the process proceeds to step S2502. If the event is a device event, the process proceeds to step S2504, and the device management unit 904 holds the device state. In step S2505, the communication event management unit 901 is notified of the device event, and the process proceeds to step S2502.

  FIG. 26 is a flowchart for explaining a processing flow of the communication connection management unit 901 that processes a request and notification from the job control print service 605, a notification from the device management unit 904, and a request and notification to the job management unit 903. .

  In step S2601, the communication connection management unit 901 determines the type of notification or request received from the job control print service 605, device management unit 904, or job management unit 903. If the request or event received in step S2601 is a connection request from the job control print service 605, the process proceeds to step S2602. In step S2602, the communication connection management unit 901 generates client information 2002 in which the client ID issued by the communication connection management unit 901 and the IP address of the client that issued the request are set, and registers them in the client management queue 2001.

  If the request or event accepted in step S2601 is event registration from the job control print service 605, the process proceeds to step S2603. In step S2603, the communication connection management unit 901 sets the type of event to be notified to the registration event of the corresponding client information. The event types include a job event that notifies a change in the job state and a device event that notifies a change in the device state.

  If the request or event accepted in step S2601 is a device event from the device management unit 904 or a job event from the job management unit 903, the process advances to step S2604. In step S2604, in order to recognize the client to be notified of these events, it is determined whether or not to notify all the client information registered in the client management queue 2001 by referring to the setting of the registered event of the client information. Then, the IP address of the client determined to be notified is held. Thereafter, in step S2605, an event is transmitted to all clients whose IP addresses are held in step S2605.

  If the request or event accepted in step S2601 is a disconnection request from the client, the process proceeds to step S2606, and the client information of the corresponding client is deleted from the client management queue.

  As described above, according to the present embodiment, it is possible to register a pull print job having a plurality of printing conditions in a single pull print queue. In other words, a job having a specific ID (job specification information) can be extracted from a plurality of jobs registered in the pull print queue, and the job extraction can be performed by changing the ID for each user. Can behave differently. In addition, even when there are a plurality of target pull print jobs at the start of pull printing, it is possible to print without interrupting the printing of another person between the plurality of print jobs.

  Further, according to the present embodiment, it is possible to improve usability when printing a confidential document, a highly confidential document, or the like. In other words, the user does not need to go to the printing device in order to keep track of the paper discharge status, and when printing multiple print jobs, the printed material can be used as a safe and secure document without being mixed with other people's printed materials. It can be acquired.

  Although the embodiment has been described in detail above, the present invention can take an embodiment as a system, apparatus, method, program, storage medium, or the like. Specifically, the present invention may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.

  In the present invention, the functions of the above-described embodiments are achieved by supplying a software program directly or remotely to a system or apparatus, and the computer of the system or apparatus reads and executes the supplied program code. Including the case. In this case, the supplied program is a program corresponding to the flowchart shown in the drawing in the embodiment.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, or the like.

  Examples of the recording medium for supplying the program include the following. For example, floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, CD-RW, magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD- R).

  As another program supply method, a client computer browser is used to connect to a homepage on the Internet, and the computer program of the present invention is downloaded from the homepage to a recording medium such as a hard disk. In this case, the downloaded program may be a compressed file including an automatic installation function. It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer is also included in the present invention.

  Further, the program of the present invention may be encrypted, stored in a storage medium such as a CD-ROM, and distributed to users. In this case, a user who has cleared a predetermined condition is allowed to download key information for decryption from a homepage via the Internet, execute an encrypted program using the key information, and install the program on the computer. You can also.

  In addition to the functions of the above-described embodiment being realized by the computer executing the read program, the embodiment of the embodiment is implemented in cooperation with an OS or the like running on the computer based on an instruction of the program. A function may be realized. In this case, the OS or the like performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.

  Furthermore, the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, so that part or all of the functions of the above-described embodiments are realized. May be. In this case, after a program is written in the function expansion board or function expansion unit, the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program.

1 is a block diagram illustrating an overall configuration of a print system according to an embodiment. It is a block diagram explaining the hardware constitutions of a client. It is a figure which shows an example of the memory map of RAM202 shown in FIG. FIG. 3 is a diagram illustrating an example of a memory map of the FD 204 illustrated in FIG. 2. It is a block diagram explaining the hardware constitutions of the network printer by embodiment. It is a figure which shows the example of the software structure regarding the print system of the client by embodiment. FIG. 6 is a diagram illustrating a flow of a print job when printing by a client. It is a figure which shows the example of a software configuration of a network printer. It is a figure which shows the example of a software configuration of the user application of a network printer. FIG. 6 is an activity diagram illustrating a schematic operation in the print system of the embodiment. 6 is a flowchart of processing for accepting a job in a pull print queue by a job control print service according to the embodiment. 6 is a flowchart of processing for accepting a job in a pull print queue by a job control print service according to the embodiment. 6 is a diagram illustrating an example of a GUI for allowing a user to set job identification information to be embedded in a print job. FIG. FIG. 10 is a process flowchart illustrating job identification processing by a pull print agent. FIG. FIG. 6 is a diagram illustrating print job information and a job management queue managed by a job control print service. FIG. 6 is a diagram illustrating information on printer queues and output ports managed by a job control print service. It is a figure showing the information which a pull print agent transmits to a job control print service. 10 is a flowchart for describing processing in which a job control print service registers a job specified from a pull print agent in a device scheduler. 6 is a flowchart illustrating processing for specifying a print job on a job control print service. 10 is a flowchart for explaining processing when a job control print service receives a schedule UP command from a device scheduler. 6 is a flowchart illustrating a flow of processing of a job control print service when a notification or command is received from a device scheduler. It is a figure which shows the client information and client management queue which are managed by a device scheduler. It is a figure which shows the job information and job management queue which are managed by a device scheduler. FIG. 4 is a diagram illustrating a print sequence between a job control print service, a device scheduler, LPD / RAW, and a printer controller. 10 is a flowchart in the device scheduler from when a job control print service schedule request is accepted until when a schedule UP is issued. 6 is a flowchart illustrating processing from reception of a job status notification event to reception of a job list request of a job management unit. 6 is a flowchart illustrating processing of a device management unit when a device status and job status notification is received from a printer controller. It is a flowchart which shows the process of the communication connection management part which processes the request | requirement and notification from a client, the notification from a device management part, and the request | requirement and notification to a job management part.

Claims (12)

An information processing apparatus that can be connected to a printing apparatus,
A first registration means for registering a print job with identification information associated with the user;
An input means for inputting specific information for selecting a print job to be printed;
A search unit for searching for a print job in which the identification information given by the first registration unit corresponds to the specific information input by the input unit from the print job registered by the first registration unit;
When a plurality of print jobs are retrieved by the retrieval unit, common identification information is given to the plurality of print jobs, and the plurality of print jobs are registered in a print queue associated with an output destination printing apparatus. A second registration means;
Transfer means for collectively transferring the plurality of print jobs to a printing apparatus when one transfer of the plurality of print jobs to which the common identification information registered in the print queue is given is permitted; An information processing apparatus comprising:   The information processing apparatus according to claim 1, wherein the transfer unit transfers the plurality of print jobs in one session. The first registration means can register a plurality of identification information related to the user for one print job,
The information processing apparatus according to claim 1, wherein the search unit searches for a print job including identification information corresponding to the specific information.   When a plurality of identification information is given to the print job searched by the search means, the second registration unit duplicates a print job having only the identification information corresponding to the specific information and registers it in the print queue The information processing apparatus according to claim 3.   The information processing apparatus according to claim 1, further comprising means for providing a user interface for causing the user to set identification information related to the user.   The information processing apparatus according to claim 1, wherein the identification information related to the user is generated based on user authentication information.   The information processing apparatus according to claim 1, wherein the first registration unit registers a print job in an undecided print queue by an output destination printing apparatus. A printing system in which a printing device and an information processing device are connected,
The information processing apparatus is
A first registration means for registering a print job with identification information associated with the user;
Input means for inputting specific information for selecting a print job to be printed from the printing apparatus;
A search unit for searching for a print job in which the identification information given by the first registration unit corresponds to the specific information input by the input unit from the print job registered by the first registration unit;
When a plurality of print jobs are searched by the search means, common identification information is given to the plurality of print jobs, and the plurality of print jobs are registered in a print queue having the printing apparatus as an output destination. 2 registration means;
A transfer unit configured to transfer the plurality of print jobs to the printing apparatus in a batch when transfer permission is notified from the printing apparatus to one of the plurality of print jobs to which the common identification information is assigned; A printing system comprising: A print job transfer control method by an information processing apparatus connectable to a printing apparatus,
A first registration step of adding identification information related to the user to the print job and registering it in a predetermined queue;
An input process for inputting specific information for selecting a print job to be printed;
A search step of searching for a print job in which the identification information given in the first registration step corresponds to the specific information input in the input step from the print jobs registered in the predetermined queue;
When a plurality of print jobs are searched by the search step, common identification information is given to the plurality of print jobs, and the plurality of print jobs are registered in a print queue related to the output destination printing apparatus. A second registration step;
A transfer step of collectively transferring the plurality of print jobs to a printing apparatus when one transfer of the plurality of print jobs to which the common identification information registered in the print queue is given is permitted; A transfer control method for a print job, comprising: A print job transfer control method in a print system in which a printing apparatus and an information processing apparatus are connected,
A first registration step in which the information processing apparatus assigns and registers identification information related to a user to a print job;
An input step in which the information processing apparatus inputs specific information for selecting a print job to be printed from the printing apparatus;
A search step in which the information processing apparatus searches for a print job in which the identification information given in the first registration step corresponds to the specific information input in the input step from the print job registered in the first registration step. When,
When the information processing apparatus searches for a plurality of print jobs in the search step, the information processing apparatus assigns common identification information to the plurality of print jobs, and uses the plurality of print jobs as the output destination. A second registration step of registering in the print queue;
A transfer step of collectively transferring the plurality of print jobs to the printing device when transfer permission is notified from the printing device to one of the plurality of print jobs to which the common identification information is assigned; A transfer control method for a print job, comprising:   A control program for causing a computer to execute the print job transfer control method according to claim 9.   A computer-readable medium storing a control program for causing a computer to execute the print job transfer control method according to claim 9.

Images