JP2007025970A - Pull print system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a pull print system for appropriately performing post-processing in response to a print result. <P>SOLUTION: The system is configured to have a print result determining means determining a print result, and to delete print data when it is determined that the print result is "OK" as a result of determination by the determining means. The print data to be spooled on a print server 605 being based on the print result by a print device by which the print is executed, accidental deletion of a print job is avoided, further, when the print is completed successfully, the job may be deleted timely and surely, and a load on the server 605 and a maintenance load thereon can be reduced. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a pull print printing system.

  2. Description of the Related Art Conventionally, a pull print system has been devised for printing a print job on a server from an operation panel on a printing apparatus or an operation terminal near the printing apparatus. In such a pull print server, it is impossible to know the timing when printing (pull printing) by the printing apparatus is completed, and thus it is not possible to smoothly perform processing after the printing is completed. Specifically, since it was not possible to determine the timing for deleting a job that has been printed, the processing is mainly performed according to an instruction from a user or an administrator, or automatically deleted after a certain period of time. It had been. However, in this case, unprinted documents are deleted, or if a large number of print jobs are submitted within a certain period, the result is that the load on the server is reduced.

In order to solve this problem, the pull print server can estimate the print completion time when printing by the printing apparatus is completed, and deletes the printed job based on the estimated print completion time Has been devised (Patent Document 1).
JP 2004-145554 A

  However, in the conventional technique, an error occurs in the printing apparatus after the print data is transmitted from the pull print server to the printing apparatus because the print job is deleted by estimation from the time when the server executes printing. In some cases, the print data may be deleted before the printing is properly completed.

  In order to solve the above-described problem, the present invention includes a print server that spools and manages print data, and a print execution instruction unit that instructs the server to execute printing. According to an instruction from the previous period print execution instruction unit, In a pull print system for printing out print data held in the print server, a print result detection unit for detecting a print result of the executed print job and a print result detected by the print result detection unit are determined. And a print result determining means, and a job erasing means for erasing the print job from the server when the print result determined by the print result determining means is successful. system.

  According to the present invention, since the print data spooled on the print server is based on the print result of the printing apparatus on which printing has been executed, there is no need to inadvertently delete the print job. When printing is successful, the job can be surely erased in a timely manner, and the load on the server and the maintenance load can be reduced.

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

<System configuration>
FIG. 1 is a block diagram showing the overall configuration of a printing system according to an embodiment of the present invention. The printing system includes clients (computers) 101 to 103 as information processing apparatuses and network printers 104 to 105 as printing apparatuses (printing devices). It is composed.

  The clients (computers) 101 to 103 store a print control program so that they can be executed. In addition to managing the network printers 104 to 105 included in the print system, the clients (computers) 101 to 103 store files used on the network. And a function of monitoring the use state of the network. Specifically, the clients (computers) 101 to 103 create a print job by themselves, issue a schedule request to the scheduler of the network printers 104 to 105, and print according to an instruction from the scheduler of the network printers 104 to 105. It has a function to start data transfer.

  The network printers 104 to 105 are print devices as physical devices that receive print jobs including print data from clients (computers) 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 using an electrophotographic method, an ink jet printer using an ink jet method, or a printer using a thermal transfer method can be used.

  Further, the network printers 104 to 105 receive print requests from a plurality of clients (computers) 101 to 104, determine the order of the received print requests, and issue a print instruction, and are transferred to the network printers 104 to 105. The print job and the status of the network printers 104 to 105 are monitored, and the client (computer) 101 to 104 is notified of the end of printing and the printer status.

  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.

<Configuration of print server and client>
FIG. 2 is a block diagram illustrating a hardware configuration of the clients (computers) 101 to 103 illustrated in FIG.

  In FIG. 2, a CPU 200 reads and executes an application program, a printer driver program, an OS, a print control program, and the like stored in an HD (hard disk) 205, and temporarily stores information, files, and the like necessary for executing the program in a RAM 202. It is a control means for performing storage control automatically.

  The ROM 201 is a storage unit that 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 is temporary storage means that functions as a main memory or work area of the CPU 200.

  The FD (flexible disk) drive 203 is a storage medium reading means for loading a program or the like stored in the FD 204 as a storage medium into the computer system as shown in FIG. The clients (computers) 101 to 103 may include other storage medium reading means instead of the FD drive 203 or together with the FD drive 203. Examples of the other storage medium include any computer-readable storage medium such as a CD-ROM, CD-R, CD-RW, PC card, DVD, IC memory card, MO, and memory stick.

  The HD 205 is an external storage unit 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 as spool means is secured here. The clients (computers) 101 to 103 secure a spooler as spool means.

  The keyboard 206 is an instruction input unit for the user to instruct the print server 101 and the clients 107 and 108 to input device control command instructions and the like.

  A display 207 is a display unit that displays commands input from the keyboard 206, the states of the printers 104 to 105, and the like. Actually, a display instruction is given to the display means via an operating system running on the clients (computers) 101 to 103, and a resource file display instruction is given to this operating system by this print processing program. Display is realized. A system bus 208 controls the data flow in the computers as the clients (computers) 101 to 103.

  The interface 209 is an input / output unit, and the print server 101 or the clients 107 and 108 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 is a memory map in a state where the print control program is loaded into the RAM 202 and can be executed.

  The print control program and the related data may be installed in advance from the FD 204 to the HD 205 and loaded from the HD 205 into the RAM 202, or may be directly loaded from the FD 204 into the RAM 202 and executed. Furthermore, it is also possible to store the print control program in the ROM 201, configure it as a part of the memory map, and execute it directly by the CPU 200. In addition, software that realizes the same function as each of the above devices can be used as an alternative to a hardware device.

  The print control program controls the client to instruct to transfer print data, instruct to change the print destination of the print job, or to change the print order.

  Reference numeral 301 denotes an area for storing a basic I / O program. The basic I / O program is an IPL (Initial Program Loading) function that starts the operation of the OS by reading the OS from the HD 205 into the RAM 202 when the apparatus (the print server 101 or the clients 107 and 108) is turned on. And so on.

  An area 302 stores an OS (operating system), and an area 303 stores a print control program. Reference numeral 304 denotes an area for storing related data. A work area 305 is an area for the CPU 200 to execute various programs.

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

  FIG. 5 is a block diagram illustrating a hardware configuration of the printing system according to the embodiment of the present invention. Reference numeral 500 denotes a printer, which is mainly composed of devices that control different control systems including a network printer server 520 and a printer controller 519. In the network print server 520, reference numeral 501 denotes a network print server CPU, which is connected to a local area network (LAN 512) via a network controller (LANC 505) connected to the system bus 504 based on a control program stored in a rewritable Flash ROM 503. By using a plurality of external devices (not shown) such as connected host computers and a predetermined network communication protocol, it collectively controls various data transmission / reception requests such as print data and printer control commands sent from the external device, Appropriate data transfer control is performed for the printer controller 519 connected via the expansion interface controller (EXPC 507).

  The RAM 502 is used as a temporary storage area such as a main memory or work area of the CPU 501.

  The LED 506 is used as a display unit indicating the operation state of the network print server. For example, the electrical connection state (LINK) between the network controller (LANC 505) and the local area network (LAN 512) and the network communication mode (10Base, 100Base, all Various operating states such as double and half duplex can be indicated by LED blinking patterns and colors.

  Furthermore, the expansion interface 517 that connects the network print server 520 and the printer controller 519 is configured with a connector (not shown), and only the network print server 520 can be attached and detached, and the network print server 520 can be attached to another printer 500 having the same configuration. Is also possible.

  In the printer controller 519, a printer controller CPU 508 is a control program stored in the ROM 509 or a control program or resource data (resource information) stored in the external memory 510 connected via the disk controller (DKC 515). And the raster controller 512 based on print data received from the network print server 520 connected via the expansion interface controller (EXPC 513). To generate output image information and output an image signal to the print engine 516.

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

  Reference numeral 518 denotes an operation panel (operation unit) on which buttons for performing operations such as setting of the operation mode of the printer 500 and cancellation of print data and a display unit such as a liquid crystal panel and LEDs indicating the operation state of the printer 500 are arranged. Yes.

  The printer engine 516 shown in the figure uses a known printing technique, and examples of suitable implementation systems include an electrophotographic system (laser beam system), an inkjet system, and a sublimation method (thermal transfer) system. .

  Reference numeral 519 denotes an external I / O interface for exchanging information with the external device 520.

  Next, the software configuration of the client of this print system will be described. FIG. 6 is a diagram illustrating an example of a software configuration in the clients 101 to 103. (In FIG. 6, Windows is a registered trademark. The same applies to FIG. 7.) The arrows between the components indicate how a print job including a drawing command issued from an application is processed. is there. The software configuration shown in each block is executed by the CPU 200 in FIG. 2 to realize a desired function.

  Normally, when a general application program 601 such as document creation software receives a print instruction, it generates a series of drawing commands via the OS. The PDL driver 602 that has received a drawing command generated via the OS 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. However, the present invention is not limited to this. For example, a BDL (Band description Language), a printer driver that creates a compression bitmap, or an application and OS Needless to say, the present invention can also be applied to a form in which print data is generated without using a printer driver.

  The PDL driver 602 passes the print job to the spooler 603 to transmit the print job to the print device.

  Here, since the OS is assumed to be Windows (registered trademark), the spooler 603 is a Windows (registered trademark) spooler. However, it goes without saying that the OS of the computer to which the present invention is applied is not limited to Windows (registered trademark), and other OSs can be applied as long as they have drawing commands.

  The spooler 603 takes a procedure of transferring a print job to the port monitor 604 selected and instructed by the user via the user interface and transmitting the print job to a print device such as the network printers 104 to 105 (arrow a).

  Here, the description will be made assuming that the user has designated the port monitor 604 (hereinafter abbreviated as job control port monitor) to transfer the print data to the pull print server 605 and instructed printing in advance.

  In addition, print setting information such as a paper size and a staple instruction set via the printer driver interface is also transmitted to the job control port monitor 604. The job control port monitor 604 transmits to the print service 605 (hereinafter referred to as a pull print server) (arrow b).

In the clients 101 to 103, the job registration application 609 of the client 608 other than the pull print server 605 inputs print data to the pull print server 605 via the API 610. (Arrow g)
The pull print server 605 has a function of managing the transferred print job and device status. It also has functions of managing information such as device status and job status notified from the print device, and giving a predetermined command to the print device. 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. When the order arrives based on the order management function, the printer device 606 Print data is transmitted to the network printers 104 to 105 (arrows c, d, e).

  Upon confirming the completion of the print data, the printer device 606 notifies the pull print server 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 what state the print job is in the pull print server 605 and to operate the print job. The print manager 607 exchanges information and instructions with the pull print server 605 via a software interface (API: Application Program Interface) of the pull print server 605.

  A function of acquiring status information of the network printers 104 to 105 managed by the pull print server 605 as an event is mainly provided. 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. Here, the pull print server 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 a network.

  As more detailed processing, the print manager 609 issues an event specifying a device to the pull print server 605, and the pull print server 605 recognizes the status of the device based on the issued event, and the result based on the monitoring. Is sent to the print manager 609.

<Print job flow>
Next, the flow of a print job from the application 601 to the print device 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 shown in FIG. 7, conceptually, a PDL driver 602, a spooler 603, and a job control port monitor 604 are prepared for each print device 104 to 105. When the OS is Windows (registered trademark), these may be collectively referred to as a Windows (registered trademark) print system 700.

  The pull print server 605 includes a number of print queues 701 and 701A and output ports 702 and 702A corresponding to the print devices 104 to 105. These print queues and output ports 702 and 702A are managed by the pull print server 605 using tables such as 1801 and 1802, respectively.

  The output port is associated with an IP address of a corresponding printing apparatus or a name used in name resolution (DNS). Based on the IP address or name, the job schedule request destination and job transmission destination are specified, and the job is transmitted (output).

  When printing, the application 601 designates a printer and issues a print instruction. When 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 pull print server 605, the print job information is first held in the print queue 701 and printed on the output port 702. An instruction to accept a job is issued. 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 for the output port. A scheduler, which will be described later, of the printer device 606 performs scheduling processing for jobs received from a plurality of pull print servers 605 based on its own scheduling function, and issues a print instruction to the output port 702. The output port 702 that has received the print instruction transmits print data to the printer device 606.

  FIG. 8 is a block diagram illustrating a software configuration in a control program stored in each storage device of the network print server 520 and the printer controller 519 which are control devices in the printer 500 in the printing system suitable for the embodiment of the present invention. It is.

  Each control program is analyzed and processed by the CPU of each control device.

  Reference numeral 801 denotes an operating system that controls basic data input / output control of the network print server 520. Further, in the operating system 801, a file system 805 that controls input / output with the program / data storage unit 509, an expansion interface driver 807 that controls communication via the printer controller 519 and the expansion interface 517, and a local area network (LAN 512). A network interface driver 806 that communicates with an external device such as a host computer (not shown) via the communication medium is included.

  Reference numeral 802 denotes an application program interface (API), which has various functions of the operating system for application programs such as a user application 803 that operates on the network print server 502, a printer 500, and a management application that registers and manages user applications. provide. The 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 that controls input / output of resource data such as bitmap images and display messages, and restart of the printer 500. A printer control API for controlling initialization and setting values, a job control API for controlling print job cancellation and reprinting instructions, restarting the network print server 520, initialization and setting of setting values, and A print server control API for starting, registering, and deleting application programs is provided.

  Reference numeral 812 denotes an operating system that supervises various processing controls of the printer controller 519. The print engine control unit 814 that controls communication with the print engine and models such as bitmap images and error messages that are referred to from the network print server 520 It includes a file system 815 that performs input / output control with a dependent resource and a model-dependent resource / program storage unit that stores a model-dependent application program that runs on the network print server.

  Reference numeral 813 denotes an extension interface control unit that controls communication with the network print server 520 via the extension interface 517. Further, the extended interface control unit includes a data transfer logical interface for controlling input / output of print data for each control type, a resource control logical interface for controlling input / output of various data stored in the model-dependent resource / program storage unit 509, A printer control logical interface that controls the restart of the printer 500, initialization of setting values, settings, and the like, and a job control logical interface that controls cancellation of a print job, a reprint instruction, and the like are provided. The command requested from the network print server 520 is transferred to the operating system 812, and the processing result is returned to the network print server 520.

  Reference numeral 818 denotes a USB control unit that acquires authentication information and presence information of the authentication information recording medium from the authentication information recording medium 821 via the authentication information reading device 820, which is an external device connected by a USB cable.

  A network control unit 811 receives a notification of reception when the network interface driver 806 receives a notification from the clients 101 to 103 via the LAN 512. The network control unit 811 determines a communication from which client and controls the communication. It is a module that can.

  A module 810 controls a protocol for receiving print data transmitted by the client, and can pass the received print data to the printer controller.

  The application 803 is stored in the program storage unit 816 of the print controller 519 or the program storage unit 808 of the network print server 520. When the printer 500 is activated, the license stored in the program storage unit 808 or the application stored in the application is compared with the licenses stored in the license storage unit 809, the program storage unit 816, and the license storage unit 817 to determine whether they match. If they match, it is determined that the application program is appropriate, and the application program is loaded into the RAM 514 of the network print server 520.

  Next, software configurations of the device scheduler 900 and the pull print agent 906, which are user applications on the device having the scheduling function of the print system and the management function of the print job received from the clients 101 to 103, will be described.

  FIG. 9 is a diagram illustrating an example of the software configuration of the user application of the printer.

  A communication connection management unit 901 manages the connection status of the clients 101 to 103 to be printed and information to be notified to the client, and manages the connected client information 1002 in the client management queue. The communication connection management unit 901 communicates with the client via the data transfer API of the program application interface 802 and the network interface driver 806.

  A schedule management unit 902 performs scheduling of print jobs received from the clients 101 to 103, and includes a job management unit 903 and a device management unit 904.

  A job management unit 903 manages schedule requests issued by the clients 101 to 103 and jobs printed by the clients 101 to 103. A job management unit 903 manages job information 1102 printed by the client in the job management queue 1101.

  A device management unit 904 receives the printer status of the printer controller 519 and the status of the received print job via the event handler 905. The event received from the printer controller 519 is sent to the communication connection management unit 901 and the job management unit 903. Notice.

  Reference numeral 907 denotes a USB management unit which acquires authentication information (job information, etc.) via the 818 USB control unit and passes it to the server management unit 908. In step 909, device address information is acquired and passed to the server management unit 908. The server management unit 908 transmits the acquired information to the pull print server 605.

  FIG. 10 is an activity diagram outlining the preferred embodiment of the present invention.

  An outline of the operation of the printing system according to the embodiment of the present invention 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 in the printer engine 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 printer 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 printer agent 906 and the device scheduler 900 enter an event waiting loop.

  In step S1003, when the pull printer agent 906 detects that the authentication information recording medium 821 has been inserted into the authentication information reading device 820, the pull printer agent 906 reads the authentication information recorded in the authentication information recording medium 821 and performs authentication means (not shown). To identify the card owner and obtain job identification information.

  In step S1004, device configuration information is acquired via the printer engine control unit 814. The configuration information acquired here includes consumable information such as the remaining amount of paper and the presence of toner, and device information such as whether or not the duplex unit and the staple device (finisher) can be used.

  In step S1005, the pull printer agent 906 notifies the pull print server 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. Upon receiving the print start, the pull print server 605 selects a printable job from the job identification information and device configuration information. This process will be described later with reference to FIG.

  In order to execute printing, the pull print server 605 first performs event registration and job schedule reservation in step S1006. This event reservation is the same as step S1002 described above. The schedule reservation will be described later with reference to FIG. In step S1007, the schedule is received. The process for receiving the schedule UP will be described later with reference to FIG. When the schedule is received in step S1007, the job is transmitted in S1008.

  The pull print agent 906 detects that the recording medium has been taken out in step S1009, and issues a job cancel instruction and a job holding instruction to the pull print server 605 in step S1010. The pull print server 605 issues a job cancel instruction to the device scheduler 900 in step S1011. Upon receiving a job cancel instruction, the device scheduler 900 issues a job cancel instruction to the printer engine control unit 814 in step S1012. When the job is cancelled in the device, the device scheduler 900 notifies the pull print server 605 of the print completion and the number of printed pages in response to the notification of the job cancel end in S1013. The pull print server 605 holds the job when the notified number of printed pages is smaller than the total number of jobs. This process will be described later with reference to FIG.

  FIG. 11 is a diagram showing processing for registering a pull print job in the pull print server 605.

  In step S1101, the application 601 generates a job. Next, the application 601 issues a print instruction by designating a printer. Based on this print instruction, the print job generated by the PDL driver 602 is passed to the job control port monitor 604 in step 1102.

  In step S1103, job identification information is acquired, and in step S1104, this information is embedded in the print job. The job identification information is the same as the information recorded in the authentication storage medium 821, and this information can be acquired by the user inputting information through a GUI (not shown).

  In step S1105, the job status is set to “stop”. In step S1106, the job whose status is "stopped" is retained in the pull printer queue.

  In addition, in the job registration method, a job can be registered from a job registration application 609 (not shown) in addition to a method of registering from the application 601. In this case, the job registration application 609 may exist on a different client PC from the pull print server 605.

  In order to register a job from the job registration application 609, a job through the PDL driver is created in step S1107, and the job created from the job registration application 609 is selected. In step S1109, job identification information is designated from the job registration application 609. This information is the same as the information recorded in the authentication storage medium 821. In step S1110, the job status is set to “stop”. In step S1106, the job is retained in the pull printer queue via the API 610.

  FIG. 12 illustrates the processing from detection of authentication information by the pull print agent 906 to notification of information necessary for pull printing from the authentication information recording medium 821 to the pull print server 605.

  In step S1201, the authentication information reading device 820 detects a change in the state of the authentication information recording medium 821, and detects the change when the state of the authentication information recording medium 821 changes. The change in the state of the authentication information recording medium 821 is change information such as when the card is removed or inserted when the authentication information reading device 820 is a card reader or the like. In addition, when the authentication information reading device 820 detects the authentication information recording medium 821, the change information indicates whether the presence of the authentication information recording medium 821 has changed. The same applies to the case of an apparatus that performs authentication by holding a hand or the like over the authentication information reading apparatus 820.

  If there is a recording medium in step S1201, the process proceeds to step S1203, and job identification information is acquired from the recording information.

  In step S1204, a device address and device configuration information for specifying the device are acquired from the device. The configuration information acquired here includes consumable information such as the remaining amount of paper and the presence of toner, and device information such as whether or not the duplex unit and the staple device (finisher) can be used.

  In step S1205, the acquired printer identification information, device address, and device configuration information are notified to the pull printer server 900.

  If the authentication information recording medium 821 does not exist in step S1202, the process advances to step S1206 to notify the pull print server 605 of a print job cancellation and job holding instruction.

  FIG. 13 is a diagram showing job information to be added to a schedule request issued for printing by the pull print service 900, a job management queue 1301 for managing a plurality of generated job information.

  Reference numeral 1302 denotes print job information added to the schedule request issued by the pull print service 900 to start printing. The job information 1302 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 job pages, the job status indicating the status of the print job, and the pull print service 900. The job data ID included in the print data to be transferred, the IP address of the printed client, and a flag indicating whether to hold the job when canceling the job are registered.

  The job status represents a status from when the pull print service 900 issues a print schedule request to when the job disappears from the printer. Status such as waiting for printing, schedule-up status, transferring, transferring completed, printing completed, etc. Exists.

  The job data ID is an ID of a job included in the print data, and is an ID to be added when a job status in the printer controller 519 is notified.

  A management queue 1301 manages a plurality of job information 1302. When a schedule request from the pull print service 900 is received, the job information 1302 is registered in the management queue, and when the print job is printed, the corresponding printer information is deleted. It has come to be.

  FIG. 14 shows information on printer queues and output ports managed by the pull print server 605.

  Reference numeral 1401 denotes information of each printer queue managed by the job control printer service, and includes information such as a printer name.

Reference numeral 1402 represents information on each output port managed by the job control printer service, and includes information such as the IP address of the device to be printed.
Reference numeral 1501 in FIG. 15 is a table indicating information that the pull print agent 906 transmits to the pull print server 605 after the authentication information reading device 820 detects the authentication information recording medium 821. The information table includes a device address, Job identification information and device configuration information.

  FIG. 16 shows the flow from the printing process shown in FIG. 21 until the pull print server 605 of the clients 101 to 103 receives the job identification information from the pull print agent 906 to the transfer of the print data. .

  In step S1601, the device address, job identification information, and device configuration information are acquired from the pull print agent 906, and the printer queue 701 that matches the device address acquired in step S1602 is specified. In step S1603, it is checked whether a job matching the job identification information is retained in the print queue identified in step S1603. If it is retained, the process proceeds to S1603. If not, an error is notified to the pull print agent 906 in S1604, and the process is terminated.

  In step S1605, it is determined whether to accept a print job from the job control port monitor or to accept a schedule UP command for instructing start of print data transfer from the device scheduler 90. The process proceeds to step S1606 for accepting a print job from the job control port monitor, and when a schedule UP command is accepted, the process proceeds to step S1611.

  In step S 1606, the received print job information is set in the job information 1302 and registered in the job management queue 1301.

  Information set in the job information 1302 can be obtained from the print system or obtained by analyzing print data.

  Next, in step S1607, connection is made to the device scheduler 900 and a connection request command is issued. When the client issues a connection request, the client information is registered in the client management queue of the device scheduler, and thereafter, information can be exchanged between the client and the device scheduler.

  In step S1608, job events and device events are registered in the device scheduler 900. When a job event is registered, the device scheduler 90 notifies 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 S1609, a list of jobs registered in the job management queue 1301 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, registration of a job to be printed is registered in the device scheduler in step S1610, and the next instruction is waited in step S1605.

  If a schedule UP command, which is a print data transfer instruction, is received from the device scheduler in step S1605, the process proceeds to step S1611. In step S1611, transfer of a job that has received a print instruction is started.

  When transmission of print data is started, a transfer start state is notified in step S1612 to notify the device scheduler that transfer has started.

  When the transfer of the print data is completed in step S1613, the device scheduler 900 is notified that the transfer has been completed in step S1614.

  FIG. 17 illustrates a processing flow of the job control print service 605 when a notification or command from the device scheduler is received.

  In step S1701, it is determined whether a job event notification or a job list is returned from the device scheduler 900. When a job event comes, the process proceeds to step S1702, and when a job list comes, the process goes to step S1709. Migrate processing.

  In step S1709, when the job list is returned, the job information obtained from the job list is set in the job management queue 1301 managed by the job control print service 605.

  In step S1702, 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 corresponding job information is determined in step S1710. Update job status for.

  If the received event notification is a job completion notification in step S1702, the completion result is determined in step S1703. If the printing result is successful, the corresponding job information and print data are stored in the job management queue in step S1704. Delete from 1301.

  In step S1705, the job management queue 1301 confirms whether the job of the client that has not been printed is left. If it remains, it is still necessary to exchange with the device scheduler 900. In order to continue the connection with, the process proceeds to step S1701.

  If it is determined in step S1705 that there is no job of the own client, the process proceeds to step S2005, and a process for terminating the connection with the device scheduler 900 is started.

  In step S1706, a request is made to cancel registration of the job event and device event registered in the device scheduler 900 when the connection is started. In response to this request, the device scheduler 90 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 S1707, 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 S1708, a process for disconnecting the session with the device scheduler 900 is performed, and the process waits in step S1701. FIG. 18 illustrates a process when the state of the authentication information recording medium 821 changes in the pull print agent 906.

  In step S1801, when the pull print server 605 receives a notification of a change in state of the authentication information recording medium 821 from the pull print agent 906, if the authentication information recording medium 821 no longer exists from the information notified in step S1802, The process moves to S1803. On the other hand, if it exists, the process proceeds to the above-described processing of FIG.

  In step 1803, the device scheduler 900 is instructed to cancel the job.

  In step 1804, the print surface number information sent from the device scheduler upon completion of job cancellation is compared with the total number of jobs. If the values match, the job storage flag 1302 is turned OFF in step S1804. If they do not match, the job storage flag is turned ON in step S1805 so that reprinting can be performed.

  In step S1807, event registration is canceled. FIG. 19 illustrates a client management queue 1901 that manages client information 1902 of the connected pull print server 605 and client information 1902 of a plurality of connected pull print servers 605 managed by the communication management unit 901.

  Reference numeral 1902 denotes client information having information such as the client ID assigned by the connection management unit for each connected client, the IP address of the pull print server 605 to be connected, and the type of event registered by the connecting client. The event type represents the type of device status event or job status event issued by the printer controller.

  Reference numeral 1901 denotes a management queue that holds client information of the connected pull print server 605 in the form of a queue. When the session with the client is started, the information of the corresponding client is registered in this management queue, and when the session is disconnected, the corresponding client information is deleted.

  FIG. 20 is a diagram showing a job management queue 2001 that manages job information added to a schedule request issued by the pull print server 605 for printing, 2002, and a plurality of job information generated.

  Reference numeral 2002 denotes print job information added to a schedule request issued by the pull print server 605 to start printing. The job information 2002 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 job pages, the job status indicating the status of the print job, and the pull print server 605. The job data ID included in the print data to be transferred and the IP address of the printed client are registered.

  The job status represents a status from when the pull print server 605 issues a print schedule request to when the job disappears from the printer, such as waiting for printing, schedule up status, transferring, transferring completed, printing completed, etc. Exists.

  The job data ID is an ID of a job included in the print data, and is an ID to be added when a job status in the printer controller 519 is notified.

  Reference numeral 2001 denotes a management queue for managing a plurality of job information 1102. When a schedule request is received from the pull print server 605, the job information 2002 is registered in the management queue, and when the print job is printed, the corresponding printer information is deleted. It has come to be.

  FIG. 21 describes the exchange from when the pull print server 605 of the clients 101 to 103 issues a schedule request to the printer device 606 after accepting the job to when the printer finishes printing.

  When receiving the print data, the job control print service 605 starts session connection with the device scheduler 900.

  A connection request command for notifying client information, an event registration for notifying the job / device status, and a job list acquisition command for acquiring information on jobs managed by the device scheduler 900 are issued.

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

  Next, the pull print server 605 issues a schedule request command for reserving printing. When the device scheduler 900 receives a schedule request, it registers job information in the job management queue. Information such as a document name is set in the job information. The device scheduler 900 issues a schedule UP when the printer device 606 can accept print data based on the determination described below, and prompts the job control print service 605 to start sending print data.

  When the schedule UP is issued, the job status of the job information is updated to the schedule UP status.

  The job control print service 605 starts transfer of print data to the LPD / RAW upon receiving the schedule UP, and notifies the device scheduler 900 of transfer start when the transfer starts. Upon receiving the transfer start notification, the device scheduler 900 updates the job status in the job information to the status being transferred.

  When the LPD / RAW receives print data, the data is transferred to the printer controller, and printing is started by the printer controller. When printing is started, the printer controller 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.

  The job control print service 605 transmits a transfer end notification to the device scheduler 900 when transfer of the print data ends. Upon receiving the transfer end notification, the device scheduler 900 updates the job information in the job status to the transferred status.

  When the printing process is completed in the printer controller, the device scheduler 900 is notified of the completion of printing as the job status. The device scheduler 900 notifies the client of the job printing completion status based on the registration information of the client information.

  When the job control print service 605 confirms that printing has been completed by the notification, the notification from the device is no longer necessary, so the event control registration registration 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 processing with the client.

  In FIG. 22, the flow of processing of the schedule management unit of the device scheduler from when the schedule request is received by the pull print server 605 to when the schedule UP is issued will be described.

In step S2201, when a notification from the pull print server 605 is received, it is determined whether the notification is a schedule request notification or a transfer completed notification.
If it is a notification of a schedule request, the process proceeds to step S2202, the job information set with the job ID issued by the job management unit 903 is created, the information added to the schedule request is set in the job information, and the schedule is set. Register in the job management queue in the order in which requests are received.

  In step S2203, 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 shifted to step S2201 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, the print data is not scheduled to be sent from the pull print server 605, so the process moves to step S2204 to prepare for issuing the schedule UP.

  In step S2204, the job management queue checks the jobs in the order in which the schedule request is received first, and if a job waiting for the schedule is found, the process proceeds to step S2205.

  In step S2205, the corresponding client is notified of a schedule UP for starting transfer of print data. In step S2206, the job status of the corresponding job information is updated to the schedule UP status, and the process proceeds to step S2201. .

  FIG. 23 shows processing of the job management unit 903 from reception of a job status notification event from device management described later to reception of a job list request from the job control print service 605.

  In step S2301, 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.

  If it is a job status notification from the device management unit 904, the process proceeds to step S2302, and the job status of the corresponding job information is updated. Further, the process proceeds to step S2303, and it is determined whether it is a notification of printing completion. If printing is not completed, the process proceeds to step S2304, and the connection management unit is notified to issue a job status event to the client.

  If it is a print completion notification in step S2303, the process proceeds to step S2305, the corresponding job is deleted from the job management queue, and a job completion event is issued to the connection management unit to the client in step S2306. The process proceeds to step S2301.

  In step S2309, when a job list request is received from the job control print service 605, in step S2309 the job information list is sent to the connection management unit so that the list of job information registered in the job management queue is transmitted to the requesting client. To be notified.

  FIG. 24 describes processing of the device management unit 904 that receives device status and job status notifications from the printer controller via the event handler and notifies the job management unit 903 and the communication connection management unit 901.

  In step S2401, when the device scheduler is activated, the device management unit 904 changes the device status to the printer controller via the event handler or when the status of the print job processed by the printer controller changes. Event registration processing is performed so as to notify the status of the event.

  In step S2402, if an event generated in the printer controller is received via an event handler, it is determined whether the event is a job event or a device event. If it is a job event, the job management unit 903 is notified of the job event in step S2403, and the process proceeds to step S2402. If the event is a device event, the process proceeds to step S2404, the device state is held in the device management unit 904, the device event is notified to the communication connection management unit 901 in step S2405, and the process proceeds to step S2402. .

  The job information list is notified to the connection management unit so that the job information list is transmitted to the requesting client.

  FIG. 25 describes a processing flow of the communication connection management unit 901 that processes requests and notifications from the pull print server 605, notifications from the device management unit 904, and requests and notifications to the job management unit 903.

  In step S2501, notifications and requests from the pull print server 605, the device management unit 904, and the job management unit 903 are received, and it is determined which notification or request.

  If the request or event accepted in step S2501 is a connection request from the pull print server 605, the process proceeds to step S2502, and the client ID issued by the communication connection management unit 901 to the client management queue and the IP of the client that issued the request. Set the address and register the client information in the client management queue.

  If the request or event received in step S2501 is event registration from the pull print server 605, the process proceeds to step S2503, and the type of event notified to the registration event of the corresponding client information is set. 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 received in step S2501 is a device event from the device management unit 904 or a job event from the job management unit 903, in step S2504, in order to recognize a client to be notified of these events, client management From all the client information registered in the queue, it is determined whether to notify by referring to the setting of the registration event of the client information. If it is determined that notification should be made, the IP address of the client is held, and an event is transmitted to all clients to be notified in step S2505.

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

1 is a block diagram showing an overall configuration of a print system as an embodiment of the present invention. 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. FIG. 2 is a block diagram illustrating a hardware configuration of a printer. It is a figure which shows the example of a software configuration of the print system of a client. FIG. 6 is a diagram illustrating a flow of a print job when printing by a client. 2 is a diagram illustrating an example of a software configuration of a printer. FIG. FIG. 3 is a diagram illustrating an example of a software configuration of a user application of a printer. FIG. 3 is an activity diagram illustrating an overview of a preferred embodiment of the present invention. 10 is a flowchart illustrating processing for registering a pull print server job. It is a flowchart which shows the process of the pull print server performed by the information detected by the pull print agent. FIG. 6 is a diagram illustrating print job information and a job management queue managed by a pull print server. FIG. 6 is a diagram illustrating information on printer queues and output ports managed by a pull print server. It is a figure which shows the information which a pull print agent notifies to a pull print server. 6 is a flowchart illustrating a flow from when the pull print server specifies print data to when the print data is transferred. It is a flowchart which shows the flow of a process of a pull print server when the notification and command from a device scheduler are received. It is a flowchart of a process after a pull print agent detects the state change of an authentication recording device until it notifies the information to a pull print server. 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 pull print server, a device scheduler, LPD / RAW, and a printer controller. It is a flowchart which shows the flow of a process of the schedule management part of a device scheduler from acceptance of the schedule request of a pull print server to issuing a schedule UP. 10 is a flowchart illustrating processing from job status notification event reception to job list request reception by a job management unit 903; 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. 10 is a flowchart illustrating processing of a communication connection management unit 901 that processes requests and notifications from clients, notifications from a device management unit, requests to a job management unit 903, and notifications.

Claims (1)

A print server that spools and manages print data;
Printing execution instruction means for instructing the server to execute printing,
In the pull print system for printing out the print data held in the print server according to the instruction from the print execution instruction means,
A print result detecting means for detecting a print result of the executed print job;
A print result determining means for determining a print result detected by the print result detecting means,
A pull printing system comprising job erasing means for erasing the print job from the server when the printing result determined by the printing result determining means is successful.

Images