JP7608908B2 - Printing system, printing method, information processing device, and program - Google Patents

Description

The present invention relates to a printing system, a printing method, an information processing device, and a program.

Image forming devices such as printers and multifunction devices can print on continuous paper or cut paper. In the case of cut paper printing, even if a "print job to print on A4 paper" and a "print job to print on A3 paper" are consecutively input to the image forming device, the image forming device automatically selects the appropriate paper tray and can print on A4 paper and A3 paper consecutively. However, in the case of continuous paper printing, only one type of paper can be loaded at a time. Suppose a "15x11 inch form" is loaded in the image forming device, and a "print job to print on 15x11 inch form" and a "print job to print on 8.5x11 inch form" are consecutively input to the image forming device. In this case, the operator stops the image forming device once the "print job to print on 15x11 inch form" is completed. The operator must then remove the "15x11 inch form" from the image forming device, load the "8.5x11 inch form" instead, and then start the "print job to print on the 8.5x11 inch form."

Therefore, technology has been devised to reduce the need to replace continuous paper (see, for example, Patent Document 1). Patent Document 1 discloses a technology in which multiple print jobs for printing on different papers are rearranged so that print jobs with the same temperature conditions or the same paper information are executed consecutively, and then input into an image forming device.

However, with conventional technology, print jobs could only be grouped if they were created using a specific model of printer driver.

For example, in Patent Document 1, the print job processed by the job controller in the DFE (Digital Front End) is RAW data generated by a printer driver for a specific model. Therefore, Patent Document 1 requires a specific upstream system that passes the RAW data to the image forming device.

In view of the above problems, the present invention aims to reduce the restrictions on models, printer drivers, etc. when grouping print jobs.

In view of the above problems, the present invention provides a printing system in which an information processing device prints a print job transmitted from an information processing terminal with an image forming device, the printing system comprising: an intermediate data generation means for converting print job data received from the information processing terminal when a real printer driver to be used for printing is selected, into EMF data using a virtual printer driver ; and a print control means for creating a plurality of job groups with print settings related to paper as grouping conditions among print settings that can be specified when executing the print job, and for allocating the EMF data to one of the job groups based on the print settings of the EMF data generated by the intermediate data generation means and the grouping conditions , the print control means converts the plurality of EMF data allocated to a predetermined job group into RAW data with the real printer driver, and after printing of the RAW data starts, if the print settings of the print job received from the information processing terminal belong to the grouping conditions of the predetermined job group, the print control means allocates the print job to the predetermined job group and prints it on the image forming device in priority over the EMF data allocated to a job group other than the predetermined job group.

This reduces restrictions on models, printer drivers, etc. when grouping print jobs.

FIG. 1 illustrates a system configuration of an example of a printing system. FIG. 2 is a diagram illustrating a hardware configuration of an example of a computer device. FIG. 1 is a diagram illustrating a hardware configuration of a multifunction peripheral that is an example of a printer. FIG. 2 is an example of a functional block diagram illustrating functions of a client PC and a print server, divided into blocks. FIG. 11 illustrates an example of a print setting screen of the virtual printer driver. FIG. 11 illustrates an example of a property screen of a virtual printer driver. FIG. 2 is an example of a functional block diagram illustrating functions of a terminal device by dividing the functions into blocks. FIG. 13 is a diagram showing an example of a screen for an operator of a web application. FIG. 13 illustrates an example of a job group list screen. FIG. 13 illustrates an example of a job group edit screen that is displayed when an edit button is pressed. FIG. 13 illustrates an example of an administrator menu screen. FIG. 11 illustrates an example of a printing system setting screen. 11A and 11B are diagrams illustrating distribution key definitions and a distribution table. 10A and 10B are diagrams illustrating an example of a login screen and a printer selection screen. FIG. 13 is a diagram showing an example of a table registration screen. FIG. 13 is a diagram illustrating what happens when the "(1) Create standard 'sorting key definition'" button is pressed. This is a diagram that explains what happens when the "(2) Add user-defined sorting key to 'Sort Key Definition'..." button is pressed. FIG. 13 is a diagram showing an example of a confirmation screen (part 1). FIG. 11 illustrates an example of a printer setting screen. FIG. 13 illustrates an example of a standard setting screen. FIG. 13 is a diagram showing an example of a confirmation screen (part 2). FIG. 13 is a diagram showing an example of the contents of a "distribution table." 11 is a flowchart illustrating an example of a procedure for creating a distribution table. FIG. 13 is a diagram showing an example of a distribution table registration screen (part 1). FIG. 13 is a diagram showing an example of a distribution table registration screen (part 2). FIG. 13 is a diagram showing an example of a distribution table registration screen (part 3). FIG. 11 illustrates an example of a printer setting screen. FIG. 13 illustrates an example of a standard setting screen. FIG. 13 is a diagram showing an example of a distribution table registration screen (part 4). FIG. 13 is a diagram showing an example of a distribution key registration confirmation screen. FIG. 13 illustrates an example of an allocation destination job group registration confirmation screen. 11 is a sequence diagram illustrating an example of a procedure in which a printing system distributes print jobs to job groups. FIG. 11 is a flowchart illustrating an example of print job distribution using a distribution table and a distribution key definition. FIG. 4 illustrates an example of a print setting screen (basic settings) of a printer driver. FIG. 13 illustrates an example of a print setting screen (extended settings) of a printer driver. FIG. 13 is a diagram showing an example of a screen on which an end user specifies a paper size on a "page setup" screen of a spreadsheet software. FIG. 13 is a diagram showing an example of a "standard settings" screen operated by a system administrator. FIG. 13 illustrates an example of a registry editor screen.

Below, we will explain a printing system and a printing method in the printing system using examples as an example of a form for implementing the present invention.

<Outline of Operation of Printing System of the Present Embodiment>
In the printing system 1 of this embodiment, a print server resident program, which will be described later, groups print jobs that share common print settings, such as paper size. Since print jobs are EMF data, restrictions on models and printer drivers can be reduced. Since the real printer driver executes print jobs in groups, the number of times paper needs to be changed can be reduced, improving the printer's operating rate. Furthermore, no upstream system is required from the printer's perspective.

<Terminology>
A group is a collection of things that have something in common. Grouping refers to sorting things that have something in common into the same group. In this embodiment, print jobs that have the same print settings are sorted into the same group.

Giving priority to intermediate data assigned to a job group over intermediate data assigned to another job group means that print jobs belonging to the same job group will be printed until printing of all print jobs belonging to the same job group is completed. However, if the operator changes the printing order of job groups, printing of print jobs belonging to the same job group may be interrupted.

<Configuration example>
1 is a system configuration diagram of an example of a printing system 1. A printer 20, a print server 30, a client PC 10, and a terminal device 50 are connected to a network N. An OS such as a Windows (registered trademark) type OS (a server OS is installed on the server) is installed on the print server 30 and the client PC 10.

A client PC 10 (an example of an information processing terminal) can request printing from this print server 30 using the printer 20. In such a system, the client PC 10 must have the same printer driver installed as the print server 30. It would be very costly for an administrator or the like to install a printer driver on each client PC 10 on the network.

Point&Print solves this problem by making it possible to download and install a printer driver from the print server 30 onto the client PC 10. This is a standard feature of Windows (registered trademark)-based operating systems. In this embodiment, the virtual printer driver and real printer driver described below are installed onto the print server 30 using the Point&Print mechanism, and then installed onto the client PC 10.

The printer 20 is an image forming device that forms and outputs an image on cut paper or continuous paper. The printer 20 may be called a printing device. In addition, if the printer 20 has the functions of the printer 20, the printer 20 may be called an MFP (Multifunction Peripheral/Printer/Product), a multifunction device, a copier, a facsimile device, a scanner device, or the like.

The print server 30 may be any information processing device on which a specific OS runs. The print server 30 may have one or more information processing devices. In this case, each information processing device may provide the functions of the print server 30, or multiple information processing devices may provide the functions of one print server 30. The print server 30 may also be compatible with cloud computing. Cloud computing refers to a form of usage in which resources on a network are used without being aware of specific hardware resources. The print server 30 may be located on-premise or on the internet.

The client PC 10 is an information processing device on which a specific OS, application, and printer driver run. Various applications for creating documents to be printed run on the OS. An end user operates the client PC 10 to request printing from the print server 30. The client PC 10 is, for example, a PC, a tablet terminal, a smartphone, a wearable PC, or a PDA (Personal Digital Assistant). In addition, as long as a specific OS, application, and printer driver run on it, it may also be a game console, a digital camera, etc.

Furthermore, a terminal device 50 is connected to the network N as necessary. A web browser runs on the terminal device 50, and executes a web application provided by the print server 30. A web application is software or a mechanism that runs on a browser and operates by cooperation between a program written in a programming language (e.g. JavaScript (registered trademark)) that runs on the browser and a program on the web server side. In this embodiment, an operator operates the terminal device 50 to change the priority order of a job group, etc. An administrator also operates the terminal device 50 to make various settings. A specific example of the terminal device 50 may be the same as the client PC 10.

<Hardware configuration example>
2 is a diagram showing an example of a hardware configuration of a computer device 500. The client PC 10, the print server 30, and the terminal device 50 have the hardware configuration of the computer device 500 shown in FIG.

As shown in FIG. 2, the computer device 500 includes a CPU 501, a ROM 502, a RAM 503, a HD 504, a HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I/F (Interface) 508, a network I/F 509, a bus line 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I/F 516.

Of these, the CPU 501 controls the operation of the entire computer device. The ROM 502 stores programs used to drive the CPU 501, such as IPL. The RAM 503 is used as a work area for the CPU 501.

HD 504 stores various data such as programs. HDD controller 505 controls the reading and writing of various data from HD 504 under the control of CPU 501.

The display 506 displays various information such as a cursor, a menu, a window, text, or an image. The external device connection I/F 508 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer 20.

The network I/F 509 is an interface for data communication using a communication network. The bus line 510 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 501 shown in FIG. 2.

The keyboard 511 is a type of input means equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving the cursor, etc. The optical drive 514 controls the reading and writing of various data from the optical media 513, which is an example of a removable recording medium. Note that the optical media may be any type, such as a CD-ROM, DVD-RW, or Blu-Ray (registered trademark). The media I/F 516 controls the reading and writing (storing) of data from the recording media 515, such as a flash memory.

＜＜Equipment＞＞
3 is a hardware configuration diagram of a multifunction peripheral that is an example of the printer 20. As shown in FIG. 3, the printer 20 includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network I/F 950.

Of these, the controller 910 has a CPU 901, which is the main part of the computer, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, a local memory (MEM-C) 907, which is a storage unit, a HDD controller 908, and a HD 909, which is also a storage unit, and is configured such that the NB 903 and the ASIC 906 are connected by an AGP (Accelerated Graphics Port) bus 921.

Of these, the CPU 901 is a control unit that performs overall control of the printer 20. The NB 903 is a bridge that connects the CPU 901 with the MEM-P 902, SB 904, and AGP bus 921, and includes a memory controller that controls reading and writing to the MEM-P 902, a PCI (Peripheral Component Interconnect) master, and an AGP target.

The MEM-P 902 is composed of a ROM 902a, which is a memory for storing programs and data that realize the various functions of the controller 910, and a RAM 902b, which is used for expanding the programs and data, and as a drawing memory during memory printing. The programs stored in the RAM 902b may be provided by recording them in an installable or executable format on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

SB904 is a bridge for connecting NB903 with PCI devices and peripheral devices. ASIC906 is an IC (Integrated Circuit) for image processing applications that has hardware elements for image processing, and acts as a bridge connecting AGP bus921, PCI bus922, HDD controller908, and MEM-C907. This ASIC906 is composed of a PCI target and AGP master, an arbiter (ARB) that is the core of ASIC906, a memory controller that controls MEM-C907, multiple DMACs (Direct Memory Access Controllers) that rotate image data using hardware logic, and a PCI unit that transfers data between scanner unit931, printer unit932, and facsimile unit via PCI bus922. In addition, ASIC 906 may have a USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface and may be connected to these.

MEM-C907 is a local memory used as an image buffer for copying and a code buffer. HD909 is a storage for storing image data, font data used during printing, and forms. HD909 controls the reading and writing of data from and to HD909 under the control of CPU901. AGP bus921 is a bus interface for a graphics accelerator card proposed to speed up graphic processing, and by directly accessing MEM-P902 with high throughput, the graphics accelerator card can be made faster.

The short-range communication circuit 920 also includes a short-range communication circuit antenna 920a. The short-range communication circuit 920 is a communication circuit such as NFC or Bluetooth (registered trademark).

The engine control unit 930 further includes a scanner unit 931, a printer unit 932, and a facsimile unit 933. The operation panel 940 includes a panel display unit 940a, such as a touch panel, that displays current settings and selection screens and receives input from the operator, and hard keys 940b, such as a numeric keypad that receives settings for image formation conditions such as density settings, and a start key that receives a copy start command. The controller 910 controls the entire printer 20, and controls, for example, drawing, communication, and input from the operation panel 940. The scanner unit 931 or the printer unit 932 includes an image processing unit such as error diffusion and gamma conversion.

The printer 20 can sequentially switch between the document box function, copy function, printer 20 function, and facsimile function using the application switching key on the operation panel 940. The printer 20 goes into document box mode when the document box function is selected, into copy mode when the copy function is selected, into printer mode when the printer 20 function is selected, and into facsimile mode when the facsimile mode is selected.

The network I/F 950 is an interface for data communication using the network N. The short-range communication circuit 920 and the network I/F 950 are electrically connected to the ASIC 906 via the PCI bus 922.

<About the function>
4 is an example of a functional block diagram for explaining the functions of the client PC 10 and the print server 30. First, the overall flow will be briefly explained.

(1) End user A inputs a print operation for the data to be printed (document file 12) into application 11. When performing the print operation, end user A selects the virtual printer driver 14. The virtual printer driver 14 is a name used to distinguish it from the real printer driver 16 that performs the actual printing, and although it appears to be a printer driver to the end user, it is used for linking with the real printer driver 16, etc. When end user A uses the real printer driver 16, printing begins without being spooled in the unique spool 41. The existence of the virtual printer driver 14 allows the print server resident program 33 to save EMF data in the unique spool 41.

(2) The GDI (Graphics Device Interface) 13 passes the EMF data to the virtual printer driver 14. EMF data is print data written in Windows (registered trademark) GDI commands. EMF data does not depend on the model of the printer 20. Since the EMF data is later converted into RAW data specific to the printer 20, it is sometimes called intermediate data.

(3) The virtual printer driver 14 stores the EMF data in the EMF spool (for client) 15.

(4) The EMF data stored in the EMF spool (for client) 15 is automatically (almost instantly) sent by Windows (registered trademark) to the EMF spool (for server) 32 using the RPC (Remote Procedure Call) protocol.

(5) The spooler (a program that manages and controls the spool) of the print server 30 communicates with the spooler of the client PC 10 via RPC, detects a print request, and calls the real printer driver 36 to request that the EMF data be printed. The virtual printer driver 31 does not have the ability to print by itself.

(6) Here, in this embodiment, the print server resident program 33 (an example of a print control means) receives the print request and saves the EMF data as a print job in the unique spool 41. The unique spool 41 is not a spool prepared by the OS, but is a spool prepared by the printing system 1 of this embodiment. Although it is called a spool, it can be any storage means that can be managed by the print server resident program 33.

The print server resident program 33 of this embodiment distributes print jobs to job groups according to the print settings and grouping conditions. In other words, the print server resident program 33 distributes EMF data with print settings that match the grouping conditions to the same job group.

In this way, because grouping is performed using EMF data that is not model-dependent, the printing system 1 of this embodiment can group print jobs without depending on the printer driver or the model of the printer 20.

(7) The printing system 1 also provides a driver setting registration program 40 (an example of a condition creation means) that accepts registration or changes to grouping conditions. The administrator C sets the registration or changes to the grouping conditions in this driver setting registration program 40. The grouping conditions (distribution table, described later) are stored in the setting information DB 38.

(8) The print server resident program 33 requests the GDI 35 to execute printing using the real printer driver 36 (an example of a printing means) based on the print order of the job groups stored in the unique spool 41. The print server resident program 33 requests the GDI 35 to give priority to printing print jobs belonging to one job group over print jobs of other job groups.

Upon receiving the request, the GDI 35 extracts the print job from the unique spool 41 and stores it in the spool 42 for the real printer driver. The real printer driver 36 converts the EMF data in the spool 42 for the real printer driver to RAW data and stores it back in the spool 42 for the real printer driver.

(9) The spooler of the print server 30 (a program that manages and controls the Windows (registered trademark) spool) passes the RAW data from the real printer driver spool 42 to the port monitor 37. When the port monitor 37 obtains the RAW data, it prints it on the printer 20.

<Explanation of each function>
4, the client PC 10 has an application 11, a GDI 13, a virtual printer driver 14, an EMF spool (client) 15, one or more real printer drivers 16, and a client PC resident program 17. The print server 30 has a virtual printer driver 31, an EMF spool (server) 32, a print server resident program 33, a Web application 34, a GDI 35, one or more real printer drivers 36, and a port monitor 37. Note that the setting information DB 38 and external user information DB 39 may be located in the print server 30 or on the network.

Below, we will mainly explain in detail the functions provided by the printing system 1 of this embodiment.

＜＜Application＞＞
First, the application 11 is software for editing a document file 12 that an end user instructs to print. The application 11 may be any type of application, such as a word processing application, a spreadsheet application, or a web browser application.

<<GDI>>
In the Windows (registered trademark) printing architecture, print settings and print instructions from the application 11 are notified to the GDI of the OS using an API. This GDI 13 is part of the OS. The GDI 13 is responsible for drawing-related processes such as drawing lines and curves, font rendering, and palette control. In this embodiment, the GDI 13 generates EMF data.

<<Virtual printer driver>>
The virtual printer driver 14 is installed in the client PC 10 when an end user uses the Point & Print function of Windows (registered trademark). The virtual printer driver 14 does not actually perform printing, but requests printing from the print server 30. On the print setting screen of the virtual printer driver 14, the end user specifies the real printer driver 16 that will actually perform printing.

Figure 5 is an example of the print settings screen 100 of the virtual printer driver 14. The print settings screen 100 in Figure 5 is displayed when the end user right-clicks on the icon of the virtual printer driver 14 and selects "Print Settings."

The printer name field 101 is a field where the end user selects the real printer driver 16 from a pull-down menu. The end user can specify any real printer driver 16, regardless of the model of the printer 20. The real printer drivers 16 that have been installed on the client PC 10 are displayed in the pull-down menu.

- The Settings button 102 is a button that allows the end user to display the print settings screen of the actual printer driver 16 currently selected in the printer name field 101.

When an end user prints using the virtual printer driver 14, the print server 30 performs the processing described in FIG. 4 on the EMF data, and the EMF data is passed to the real printer driver 36.

<< Actual printer driver >>
The real printer driver 16 is a printer driver used when actually printing from the client PC 10 to the printer 20, but is not used directly in this embodiment. However, not only the virtual printer driver 14 on the print server 30 but also all real printer drivers 16 used by the end user are installed as network printers on the client PC 10 (printer drivers installed by Point & Print). This allows the end user to display a specified screen by pressing the settings button 102.

<<Client PC resident program>>
The printing system 1 of this embodiment has a direct printing prohibition function. Direct printing means that an end user prints using the real printer driver 16 instead of using the virtual printer driver 14.

Figure 6 is an example of a properties screen for the virtual printer driver 14. The properties screen 110 in Figure 6 is displayed when the administrator right-clicks on the icon for the virtual printer driver 14 and selects "Printer Properties."

As shown in Figure 6, in the properties of the virtual printer driver 14, the administrator checks the check box 111 "Prohibit printing using other printer drivers." This prevents end users from printing directly. In other words, an error message is displayed when an attempt is made to print directly using the real printer driver 16.

The client PC resident program 17 realizes the direct printing prohibition function by monitoring the end user's operations.

Note that if the end user has administrator privileges for Windows (registered trademark), this function may be disabled because the end user may be able to terminate the client PC resident program 17. Since this is a setting that can only be performed by a Windows (registered trademark) administrator, Figure 6 must be the properties screen, not the print settings screen.

<Functions of terminal device>
7 is an example of a functional block diagram explaining the functions of the terminal device 50 by dividing them into blocks. The terminal device 50 has a communication unit 51, a display control unit 52, and an operation reception unit 53. Each of these functional units is a function or means realized by the CPU 501 executing instructions contained in one or more programs installed in the terminal device 50. Note that this program is assumed to be a web browser, but it may also be dedicated software for communicating with the print server 30.

The communication unit 51 receives screen information written in HTML, XML, CSS (Cascade Style Sheet), JavaScript (registered trademark), etc., provided by the print server 30. The web application 34 is realized by this JavaScript (registered trademark), etc. The communication unit 51 transmits information input by the administrator or operator to the terminal device 50 to the print server 30.

The display control unit 52 interprets the screen information of various screens and displays it on the display 506. The operation reception unit 53 accepts various operations by the administrator or operator on the various screens displayed on the display 506.

<<Virtual printer driver on the print server>>
The virtual printer driver 31 of the print server 30 is the same as that of the client PC 10 .

<<Web Applications>>
The web application 34 can provide a job group list screen for the operator and various screens for the administrator, as described below.

On the job group list screen, end users can view print jobs (actually EMF data) on the unique spool 41 by job group and change the printing order of the job groups.

Note that an operator must log in to the web application 34 before using the web application 34. This is because the web application 34 records the operation history for each operator in a log, making it possible to check later "who operated the print job or job group."

The user information of the web application 34 is stored in the external user information DB 39. The user information in the external user information DB 39 may be managed by the web application 34 itself, or may be provided by LDAP (Lightweight Directory Access Protocol) or the like.

<<Original spool>>
On the unique spool 41, print jobs grouped according to print settings and grouping conditions are stored for each job group. For example, in Fig. 4, print jobs are grouped into three job groups 41a according to print setting items such as paper size and strong copy. This is because the paper size and strong copy are set as grouping conditions in the sorting table described later. Details will be described later. Strong copy is a function for adjusting the strength of the impact when printing on impact printer carbon paper or non-carbon paper.

<<Web application and driver setting registration program>>
The Web application 34 and the driver setting registration program 40 are closely related to each other, so they will be described together.

Figure 8 shows an example of a screen for an operator of the web application 34. Figure 8 (a) is an example of a login screen 120 displayed by the terminal device 50.

- The user name field 121 is a field where the operator or administrator enters a user name (or user ID).

- Password field 122 is where the operator or administrator enters a password.

Figure 8 (b) is an example of the printer selection screen 130 that the terminal device 50 displays when the login button 124 is pressed (login successful). The printer selection screen 130 displays a list of printers that the operator can select. The printer selection screen 130 has a printer name 131 and a corresponding radio button 132.

In this embodiment, it is assumed that one printer is connected to the print server 30 and one type of printer driver is installed on the print server 30, so one printer is displayed on the printer selection screen 130 in Figure 8 (b).

When the operator selects this printer and presses the Next button 133, the job group list screen is displayed.

Figure 9 shows an example of the job group list screen 140. Each item will be explained below.

-Radio button 151 allows the operator to select a job group.

- The job group name 141 is the name of the job group of the print job. The printing system 1 manages the print jobs for each job group on the unique spool 41.

The job group status 142 can be any one of the following states:
a. In print
b. Waiting to print
c. Printing stopped

Note that print jobs contained in a job group also have one of the following states: "Printing," "Waiting to print," or "Printing stopped." A "Printing" job group has one internal print job that is "Printing," and all remaining print jobs are in the "Waiting to print" state. A "Waiting to print" job group has all internal print jobs in the "Waiting to print" state. A "Printing stopped" job group has all internal print jobs in the "Printing stopped" state.

- Number of jobs 143 is the number of print jobs that the job group has.

- Either "user created" or "standard" is registered in the job group type 144. "User created" is a job group created based on the distribution table described below. "Standard" is a job group created based on the paper size of the print job. Note that "non-group job" in the bottom row of Figure 9 is a job group in which a print job that does not belong to any job group is registered.

- The Up button 145 increases the priority for printing the job group.

- The Down button 146 lowers the priority for printing the job group.

- The Stop button 147 sets the job group status 142 to "Printing stopped". The Stop button 147 is only valid when the job group status 142 is "Printing" or "Waiting to print". The Stop button 147 sets the status of all jobs in the job group to "Printing stopped". If there is a "Printing" print job, the Stop button 147 sets all remaining print jobs to "Printing stopped" after printing is completed (after the print request to the real printer driver is completed). The "Printing" print job status refers to the state from when the print server resident program 33 starts to retrieve the print job from the unique spool 41 to when it completes the print request to the real printer driver 36. When the print request to the real printer driver 36 is completed, the print job disappears from the job group. However, the print job may still be "Printing" in the print queue of the real printer driver 36.

- The start button 148 changes the job group status 142 to "Waiting to print." The start button 148 is only valid when the job group status is "Printing stopped." The start button 148 changes the status of all jobs in the job group to "Waiting to print." Pressing the start button 148 changes the status of the job group that includes a job that is "Printing" to "Printing."

When a print job that is "printing" has finished printing and has been removed from the job group, the following will happen:

a. If there is a print job "waiting to print" in the top-level job group, the status of the top-level "waiting to print" job in the job group will change to "printing" and printing will begin immediately (a print request will be made to the actual printer driver).

b. If there are no remaining print jobs in the top-level job group, the job group will no longer be displayed in the job group list (it will reappear if jobs are registered in the job group in the future).

c. If the status of the top-level job group is "Printing stopped," the top-level job in the top-level job group that is "Waiting to print" transitions to "Printing," and the status of that job group also changes to "Printing."

- Edit button 149 allows the operator to move print jobs between job groups.

- The back button 150 is a button for returning to the printer selection screen 130.

Figure 10 shows an example of a job group editing screen 160 that is displayed when the edit button 149 is pressed. Note that the operator has already selected a job group with the radio button 151 in Figure 9. The job group editing screen 160 has an addition target job list field 161, a registered job list field 162, an add button 163, and a delete button 164.

- The Add target job list field 161 displays a list of print jobs that do not belong to a job group. The Add target job list field 161 displays print jobs that are "non-group jobs" to which print jobs that cannot be assigned to any job group are assigned.

- The registered job list column 162 displays a list of print jobs registered in the job group.

- The Add button 163 is a button for registering a print job from the Add target job list column 161 to the Registered job list column 162.

- The Delete button 164 is a button for deleting a print job from the registered job list column 162 and moving it to the job to be added list column 161.

Next, we will explain what happens when an administrator presses the button 123 to go to the administrator screen on the login screen 120 in Figure 8 (a).

Figure 11 shows an example of an administrator menu screen 170 that is displayed by pressing button 123 on the administrator screen. The administrator menu screen 170 is a screen for starting the configuration of the printing system 1. The administrator selects "Printing system settings" 172 and presses the Next button 171.

Figure 12 shows an example of a print system setting screen 180 that is displayed when the Next button 171 is pressed. Each item on the print system setting screen 180 is explained below.

・"Automatic creation of job groups" 181
This item is set by the administrator as to whether or not the driver setting registration program 40 automatically creates a job group. Radio button 181a accepts a setting to automatically create a "standard" type job group based on the paper name. Radio button 181b accepts a setting to not accept automatic creation of a job group.

"Automatic job allocation to job groups" 182
This item is set by the administrator as to whether or not the driver setting registration program 40 automatically distributes print jobs to job groups. The radio button 182a accepts a setting that the driver setting registration program 40 will perform automatic distribution. The radio button 182b accepts a setting that the driver setting registration program 40 will not perform automatic distribution.

"Initial state of assigned job" 183
This item is used by the administrator to set the initial state of the assigned print job. Radio button 183a accepts a setting to set the initial state of the assigned print job to waiting to print. Radio button 183b accepts a setting to set the initial state of the assigned print job to stopped printing.

"Initial state of the 'non-group job'group" 184
This item is used by the administrator to set the initial state of the "non-group job" group. Radio button 184a accepts a setting that the initial state of the print jobs in the "non-group job" group is to stop printing. Radio button 184b accepts a setting that the initial state of the print jobs in the "non-group job" group is to wait to print.

"Action when a new job group transitions to the 'printing'state" 185
This item is set by the administrator as the operation to be performed when a new job group transitions to the "printing" state. When the administrator checks the check box 185a, the driver setting registration program 40 executes the program or script specified in the program column 185b. For example, a program that displays a message to the operator urging them to change the paper may be specified.

The settings made by the administrator on the printing system setting screen 180 in FIG. 12 are stored in the setting information DB 38. The stored information is referenced by the web application and the driver setting registration program 40.

<<Settings Information DB>>
13 is a diagram explaining the sorting key definition and sorting table. The sorting key definition is a table in which the administrator registers print setting items that serve as keys for sorting print jobs into job groups. The sorting table is a table in which the administrator defines the correspondence between one or more sorting key values and the destination job groups. The sorting table determines the grouping conditions. The sorting key definition and sorting table are stored in the setting information DB 38.

A distribution key definition and a distribution table are defined for one printer driver.
(1) Distribution key definition
(2) Distribution Table Fig. 13A is a diagram for explaining the distribution key definition. The distribution key definition defines the print setting items (distribution keys) that the print server resident program 33 uses to distribute print jobs to job groups. The hatched cells in the distribution key definition are registered by the administrator using the driver setting registration program 40. The table format of the distribution key definition is made public, so the administrator can modify the contents of the created table as necessary. In Fig. 13A, the enable flag 191 for key No. = 02, 03, 09 is checked, so this is an example in which the print server resident program 33 uses the physical paper size (horizontal and vertical) and "copy enhancement" as distribution keys.

For normal cut-sheet printers, the enable flag (default is ON) for the "OS-defined paper ID" (key no. 01), described below, must remain ON. This is because it is necessary for distributing print jobs that use "A4" or "B4 (JIS)." The "OS-defined paper ID" contains the identification number of the paper that is originally managed by the OS, such as "A4" or "B4 (JIS)." (The "OS-defined paper ID" is determined by Windows (registered trademark).) The "Drv/User-defined paper name" contains the paper name defined by the printer driver (such as "15x11 inch form (13.2")") or the user-defined paper name defined by the administrator.

However, some printer drivers only support driver-defined paper (such as "15x11 inch form (13.2")") and user-defined paper. In other words, some printer drivers do not support OS-defined paper. Therefore, when distributing jobs based on paper size in a printing system 1 that uses a printer driver that does not support OS-defined paper, the enable flag for "OS-defined paper ID" (key no. 01) can be OFF. Figure 13(a) shows an example in which the administrator has turned OFF the enable flag for the OS-defined paper ID.

Each item is explained below.

Activation flag 191
The validation flag 191 specifies whether or not the distribution key corresponding to the validation flag is actually used for grouping print jobs by the print server resident program 33. If the validation flag 191 is not ON, even if a distribution key is specified in the distribution table, it is not used for grouping.

Of the standard-defined sorting keys, only "OS-defined paper ID" and "Drv/User-defined paper name" are enabled by default (Figure 13 shows the default settings disabled). The rest are disabled by default.

A user-defined distribution key is added to the distribution key definition by the administrator executing the driver setting registration program 40. At this time, the initial value of the activation flag is set to ON.

・Key No. 192
The key number is an identification number of the distribution key. The key number is automatically assigned by the driver setting registration program 40. It is used for association with the "distribution table" described later.

・Distribution key name 193
The distribution key name is an attribute that is a key for grouping print jobs. The distribution key name 193 is written in characters or the like so that the administrator can understand it. For example, when the enable flag for "OS-defined paper ID" is ON, the print server resident program 33 distributes print jobs with the same OS-defined paper name to one job group. When the enable flags for multiple distribution keys are ON, the print server resident program 33 distributes print jobs with the same values for all valid distribution keys to one job group. In the example of FIG. 13(a), a group of jobs with matching values for all of "paper width (horizontal)", "paper length (vertical)", and "enhanced copy" are distributed to one job group.

In the DEVMODE structure, only one of the following is valid: "OS-defined paper ID" (dmPaperSize) or "Paper width (horizontal) and paper length (vertical)" (dmPaperWidth and dmPaperLength). For papers defined by the OS, such as "A4" or "B4 (JIS)", only the "OS-defined paper ID" is valid ("Paper width (horizontal) and paper length (vertical)" are assumed to be cleared to zero). For papers defined by the printer driver or user, such as a "15x11 inch form (13.2")", only the "Paper width (horizontal) and paper length (vertical)" are valid ("OS-defined paper ID" is assumed to be cleared to zero).

Key type 194
The key type 194 is either "standard definition" or "user defined". "Standard definition" is a distribution key that is predefined. It does not need to be registered by the administrator. The members of the corresponding DEVMODE structure exist in the standard area. A member is each item that makes up the structure. "User defined" is a distribution key that is registered by the administrator using the driver setting registration program 40. The members of the corresponding DEVMODE structure exist in the private area.

Byte position 195 in the DEVMODE structure (an example of position information)
This item indicates in which byte on the DEVMODE structure the sorting key information exists. Byte position 195 on the DEVMODE structure is determined from the Default DevMode of the registry. For standard-defined sorting keys, the byte position is fixed, so the value of the byte position is already entered. For details on the DEVMODE structure, see Figures 34 to 38.

- Method of obtaining byte position 196
In the case of a user-defined distribution key, the administrator executes the driver setting registration program 40, which determines the byte position and writes it into the distribution key definition. The "tool" in "execute tool" refers to the driver setting registration program 40.

・Data length 197
For standard members of the DEVMODE structure, the data length is always short (2 bytes) except for the "Drv/User defined paper name." For members of the private area, the data length depends on the printer driver and is determined by the driver setting registration program 40.

・Default ON/OFF 198
When a sorting key definition is created by the driver setting registration program 40, the only activation flags that are initially ON are "OS defined paper ID" and "Drv/User defined paper name." The example in Fig. 13A shows a state in which an administrator has edited an already created sorting key definition, changing the activation flags for "OS defined paper ID" and "Drv/User defined paper name" to OFF. In this example, jobs are sorted using the physical paper size as a key, so there is no need to use "Drv/User defined paper name" as a sorting key.

・Note 199
This item indicates which member of the DEVMODE structure the value of the distribution key name is registered in.

Figure 13 (b) shows an example of an allocation table. The allocation table defines the correspondence between one or more allocation key values and the destination job group. The administrator registers the shaded cells using the driver setting registration program 40. The table format of the "allocation table" is made public, so the administrator can modify the contents of a created table as necessary.

・ID201
The ID 201 is identification information for each row of the distribution table, and is automatically assigned by the driver setting registration program 40 .

Distribution key 202
The key number is defined in the "sorting key definition." The value is defined by the printer driver, but is not publicly available. As will be described later, the administrator can register it by using the driver setting registration program 40.

· Destination job group name 203
This item is the name of the job group to which a print job having matching values for all distribution keys is distributed.

As an example, it is assumed that the values associated with the key numbers are as follows:
It is assumed that the value 01 of sorting key No. 02 [paper width (horizontal)] means "15 inches."

The value 02 of sorting key No. 02 [Paper width (horizontal)] is assumed to mean "8.5 inches."

The value 01 of sorting key No. 03 [Paper length (vertical)] is assumed to mean "11 inches."

The value 00 for sorting key No. 09 [Copy Enhancement] is assumed to mean "no copy enhancement."

The value 01 of sorting key No. 09 [Copy Enhancement] is assumed to mean "Copy Enhancement enabled."

<Define distribution keys and create distribution tables>
The following describes how to define a distribution key and create a distribution table using the driver setting registration program 40. The driver setting registration program 40 operates the registry using Windows (registered trademark) administrator privileges. Therefore, the driver setting registration program 40 is implemented as a desktop application rather than a web application.

When the administrator starts the driver setting registration program 40, he or she is first prompted to enter a user name and password.

Figure 14 (a) shows a login screen 210 for an administrator to execute the driver setting registration program 40. The administrator's username or user ID is entered in the username field 211. The password is entered in the password field 212. The login button 213 is a button that the terminal device 50 uses to request authentication using the username and password from the driver setting registration program 40.

Figure 14(b) is an example of the printer selection screen 220 that is displayed when the login button 213 is pressed. In this embodiment, one printer and one type of printer driver are assumed, so a single printer is displayed on the screen in Figure 14(b). The administrator selects which printer the settings to be made are for. The printer name specified here is stored in the settings information DB 38 in association with the distribution key definition and distribution table.

15 shows an example of a table registration screen 230 that is displayed when the Next button 221 is pressed. The table registration screen 230 has the following three buttons.
(1) "Create standard 'sort key definition'" button 231
(2) “Add user-defined sorting key to ‘sorting key definition’…” button 232
(3) "Create a distribution table..." button 233
These buttons will be explained below.

Figure 16 is a diagram explaining what happens when the "(1) Create standard 'sorting key definition'" button 231 is pressed. When this button is pressed, the driver setting registration program 40 automatically creates the "sorting key definition" in Figure 16 for the specified printer 20. In other words, the driver setting registration program 40 creates a sorting key definition that associates the position and size of the print setting items in the DEVMODE structure with sorting keys (print setting items).

If the administrator thinks that "it is sufficient to group jobs by paper name," and has selected "Automatically create 'Standard' type job groups based on paper name (default)" on the printing system setting screen 180 in FIG. 12, then the above is all that is required. Grouping jobs based on paper name can be easily achieved by following the flowchart in FIG. 33, which will be described later.

Figure 17 is a diagram explaining what happens when the "(2) Add user-defined sorting key to 'sorting key definition'..." button 232 is pressed. As an example, Figure 17 explains the case where the administrator adds the last line (No. 09 "Copy Enhancement") to the "sorting key definition."

When the administrator presses the "(2) Add user-defined sorting key to 'sorting key definition'..." button 232, the driver setting registration program 40 temporarily saves the current Default DevMode contents corresponding to the specified printer driver in memory.

The driver setting registration program 40 displays the confirmation screen (part 1) 240 shown in FIG. 18. The confirmation screen (part 1) 240 displays an explanation 241 of the screen to be displayed and instructions 242 on how to use the screen.

The screen description 241 is as follows:
Printer setting screen 250
・Confirmation screen (part 2) 270

The screen usage 242 is as follows.
First, click the [Default Settings...] button on the printer settings screen, then
Change the setting value to be used for the distribution key and click the [OK] button.

Next, enter the name of the distribution key on the "Confirmation Screen (Part 2)" and click the [OK] button."
When the administrator presses the OK button 243, the screen in FIG. 19 and the screen in FIG. 21 are displayed simultaneously.

Figure 19 shows an example of the printer settings screen 250 that is displayed when the administrator presses the OK button 243. The administrator presses the Standard Settings button 251.

Figure 20 shows an example of a standard settings screen 260 that is displayed when the standard settings button 251 is pressed. The standard settings screen 260 is a screen on which the administrator specifies a user-defined sorting key. The administrator checks the enhanced copy checkbox 261 as an example of a user-defined sorting key. In other words, the administrator changes the state of the enhanced copy checkbox 261. The administrator presses the OK button 262.

21 is an example of a confirmation screen (type 2) 270 that is displayed by pressing the OK button 243. The confirmation screen (type 2) 270 displays subsequent operation details and points to note 272. The operation details and points to note 272 are as follows.
When this "Confirmation Screen (Part 2)" is displayed, the "Printer Settings Screen" is also displayed.

First, on the "Printer Settings" screen, click the "Default Settings..." button, then change the setting value to be used for the distribution key and click the "OK" button.

To change print settings, click the Default Settings... button on the Advanced tab.

Please note that this is not the "Preferences..." button on the "General" tab.

After changing the settings on the printer settings screen and clicking the [OK] button, enter the distribution key name below on this "Confirmation Screen (Part 2)" and then click the [OK] button (please be sure to follow this order)."
When you click the [OK] button on this "Confirmation Screen (Part 2)", the setting information after changing the setting value on the "Printer Setting Screen" will be recorded.

Furthermore, this "driver setting registration program" compares data before and after the setting change, and stores the analysis results in the "distribution key definition" of the "setting database."
The confirmation screen (2) 270 also displays a sorting key name field 271. The administrator can enter the name of a user-defined sorting key in the sorting key name field 271. When the administrator clicks the OK button 273 in FIG. 21, the driver setting registration program 40 records the byte position and length of the registry key (Default DevMode) where the value has changed in the "sorting key definition" in association with the sorting key name. As will be described in FIG. 34 to FIG. 38, the byte position and length of the registry key where the value has changed is the private area where the "copy enhancement" setting is stored. With this, (No. 09 "copy enhancement") has been added to the last line of the "sorting key definition" in FIG. 17.

If there are multiple distribution keys to add, the administrator will repeat the above steps.

<<Creating a distribution table>>
22 to 31 are diagrams for explaining a case where the "(3) Create distribution table..." button 233 is pressed. The following describes a case where the administrator registers the contents of the "distribution table" in FIG.

The administrator repeatedly displays the screen described below and registers all the contents of the "distribution table" in Figure 22 using the following procedure. Since the table format of the "distribution table" is made public, the administrator may create a "distribution table" for, for example, only one row and add the remaining rows manually.

- Row ID 101 in the distribution table
[A] The administrator specifies the destination job group name "15x11 inches (no copy enhancement)".

[A-1] The administrator specifies distribution key 1 "Paper width (horizontal)" (key No. is 02).
→The administrator specifies the corresponding setting value "15 inches" (value 01).
[A-2] The administrator specifies distribution key 2, “Paper length (portrait)” (key No. is 03).
→The administrator specifies the corresponding setting value "11 inches" (value 01).
[A-3] The administrator specifies distribution key 3, “Enhanced Copy” (key No. 09).
→The administrator specifies the corresponding setting value as "None" (value is 00).

・Row ID 102 in the distribution table
[B] The administrator specifies the destination job group name "15x11 inches (with enhanced copy)".
[B-1] The administrator specifies distribution key 1 "Paper width (horizontal)" (key No. is 02).
→The administrator specifies the corresponding setting value "15 inches" (value 01).
[B-2] The administrator specifies distribution key 2, “Paper length (portrait)” (key No. is 03).
→The administrator specifies the corresponding setting value "11 inches" (value 01).
[B-3] The administrator specifies distribution key 3, “Enhanced Copy” (key No. 09).
→The administrator specifies the corresponding setting value as "Yes" (value is 01).

- Row ID 103 in the distribution table
[C] The administrator specifies the destination job group name "8.5x11 inches (no copy enhancement)".
[C-1] The administrator specifies distribution key 1 "Paper width (horizontal)" (key No. is 02).
→The administrator specifies the corresponding setting value "8.5 inches" (value 02).
[C-2] The administrator specifies distribution key 2, “Paper length (portrait)” (key No. is 03).
→The administrator specifies the corresponding setting value "11 inches" (value 01).
[C-3] The administrator specifies distribution key 3, “Enhanced Copy” (key No. 09).
→The administrator specifies the corresponding setting value as "None" (value is 00).

・Row ID 104 in the distribution table
[D] The administrator specifies the destination job group name "8.5x11 inches (with enhanced copy)".
[D-1] The administrator specifies distribution key 1 "Paper width (horizontal)" (key No. is 02).
→The administrator specifies the corresponding setting value "8.5 inches" (value 02).
[D-2] The administrator specifies distribution key 2, “Paper length (portrait)” (key No. is 03).
→The administrator specifies the corresponding setting value "11 inches" (value 01).
[D-3] The administrator specifies distribution key 3, “Enhanced Copy” (key No. 09).
→The administrator specifies the corresponding setting value as "Yes" (value is 01).

The overall flow ([A] to [D] above) by which an administrator creates a distribution table will be described with reference to FIG. 23. FIG. 23 is an example of a flowchart illustrating the procedure for creating a distribution table. Note that the process in FIG. 23 is performed by the client PC 10 executing the driver setting registration program 40.

First, the administrator operates the client PC 10, causing the client PC 10 to display the table registration screen 230 shown in FIG. 15 (S1).

Next, the administrator presses the "(3) Create distribution table..." button 233 (S2).

As a result, the client PC 10 displays the allocation table registration screen (part 1) 280 described below (S3).

Next, the administrator inputs the destination job group name and presses the Next button (S4). This causes the client PC 10 to display the allocation table registration screen (part 2) 290 (S5), which will be described later.

Next, the administrator selects a distribution key and presses the Next button (S6).

As a result, the client PC 10 displays the allocation table registration screen (part 3) 300 described below (S7).

Next, the administrator presses the OK button (S8). This causes the client PC 10 to simultaneously display the printer setting screen 310 and the allocation table registration screen (part 4) 330 (S9, S11), which will be described later.

Next, the administrator selects the distribution key value on the printer settings screen 310 and presses the OK button (S10).

The administrator also presses the OK button on the distribution table registration screen (part 4) 330 (S12).

This causes the client PC 10 to display the allocation key registration confirmation screen 340 described below, so the administrator can determine whether there are other allocation keys to register in the same destination job group and press either the Yes button or the No button (S13).

When the Yes button is pressed, the driver setting registration program 40 causes the client PC 10 to display the allocation table registration screen (part 2) 290 again.

When the No button is pressed, the client PC 10 displays the destination job group registration confirmation screen 350 described below, so the administrator can decide whether to register another destination job group and press the Yes button or the No button (S14).

When the Yes button is pressed, the driver setting registration program 40 causes the client PC 10 to display the allocation table registration screen (part 1) 280 again.

When the No button is pressed, the driver setting registration program 40 causes the table registration screen 230 to be displayed on the client PC 10.

The driver setting registration program 40 transitions through the screens in this way, allowing the administrator to register a distribution table.

The following describes each screen shown in Figure 23 in detail.

Figure 24 shows an example of an allocation table registration screen (part 1) 280 that is displayed by pressing the "(3) Create an allocation table..." button 233. The allocation table registration screen (part 1) 280 has a destination job group name field 281. The administrator enters a desired (arbitrary) destination job group name and presses the Next button 282.

Figure 25 shows an example of an allocation table registration screen (part 2) 290 that is displayed by pressing the Next button 282. The administrator uses radio button 291 to select an allocation key to be used for allocation to the destination job group entered in Figure 24.

Figure 26 is an example of a distribution table registration screen (part 3) 300 that is displayed when the Next button 292 is pressed. The distribution table registration screen (part 3) 300 displays a description 301 of the screen to be displayed and instructions on how to use the screen 302.

The screen description 301 is as follows:

Printer setting screen 310
・Allocation table registration screen (part 4) 330
The screen usage 302 is as follows.
First, click the [Default Settings...] button on the printer settings screen, then
Set the value to be used for the distribution key and click the [OK] button.

Next, click the [OK] button on the distribution table registration screen (part 4)."
When the administrator presses the OK button 303, the screen in FIG. 27 and the screen in FIG. 29 are displayed simultaneously.

Figure 27 is an example of the printer settings screen 310. Figure 27 is the same as Figure 19.

Figure 28 is an example of a standard settings screen 320 that is displayed when the standard settings button 311 is pressed. On the standard settings screen 320, the administrator specifies, for example, the value in the paper size field 321 as the sorting key value. The administrator selects paper of "15x11 inches" in the paper size field 321 of the standard settings screen 320. As a result, the paper size "15x11 inches" becomes the sorting key value selected on the sorting table registration screen (part 2) 290 of Figure 25.

29 is an example of a distribution table registration screen (4) 330 displayed by pressing the OK button 322. The distribution table registration screen (4) 330 displays subsequent operation contents and points to note 331. The subsequent operation contents and points to note 331 are as follows.
When this "Distribution Table Registration Screen (Part 4)" is displayed, the "Printer Settings Screen" is also displayed.

First, on the "Printer Settings" screen, click the "Default Settings..." button, then set the values to be used for distribution and click the "OK" button.

To change print settings, click the Default Settings... button on the Advanced tab.

Please note that this is not the "Preferences..." button on the "General" tab.

After configuring the settings on the printer settings screen and clicking the [OK] button, click the [OK] button on this "Distribution Table Registration Screen (Part 4)" (please be sure to follow this order).

When you click the [OK] button on this "Distribution Table Registration Screen (Part 4)", the settings on the "Printer Settings Screen" will be recorded in the "Distribution Table" in the "Settings Database."
When the OK button 332 is pressed, the driver setting registration program 40 reads the value on the Default DevMode corresponding to the distribution key name designated by the administrator, records it in the "distribution table", and then displays the following dialog.

Figure 30 is an example of an allocation key registration confirmation screen 340. The job group name field 341 contains the destination job group name (such as "15x11 inches (no copy enhancement)") entered by the administrator in the destination job group name field 281 of the allocation table registration screen (part 1) 280 in Figure 24.

When the administrator presses the Yes button 342, the allocation table registration screen (2) 290 is displayed again. When the administrator presses the No button 343, the driver setting registration program 40 displays the following dialog: Fig. 31 is an example of an allocation destination job group registration confirmation screen 350. When the administrator presses the Yes button 351, the allocation table registration screen (1) 280 is displayed again. When the administrator presses the No button 352, the table registration screen 230 of Fig. 15 is displayed again.

<Overall Processing Flow of Printing System>
The processing of the printing system 1 will be described with reference to Fig. 32. Fig. 32 is an example of a sequence diagram showing a procedure in which the printing system 1 distributes print jobs to job groups.

S41: The end user uses the virtual printer driver 14 on the client PC 10 to print the document file 12 generated by the application 11.

S42: The GDI 13 passes the job data (EMF data) generated from the document to the virtual printer driver 14 of the client PC 10. The EMF data is stored in the EMF spool (client) 15.

S43: The virtual printer driver 14 of the client PC 10 sends the EMF data to the virtual printer driver 31 of the print server 30 (moving from the EMF spool (for client) 15 to the EMF spool (for server) 32 using RPC).

S44: The virtual printer driver 31 of the print server 30 stores the EMF data in the EMF spool (server) 32.

S45: The virtual printer driver 31 requests the print server resident program 33 to execute the print job. The print server resident program 33 distributes the print jobs stored in the EMF spool (server) 32 to job groups. Details are explained in Figure 33.

S46: The print server resident program 33 moves the print job from the EMF spool (for server) 32 to its own spool 41.

S47: Operator P operates Web application 34 to change the job group to which the print job belongs. In this way, operator P can change the assignment destination of the automatically assigned print job. This operation is not necessarily performed at this timing, and the operation timing is one example.

S48: The web application 34 accepts the job group change. The web application 34 notifies the print server resident program 33 of the job group change.

S49: The print server resident program 33 changes the job group to which the print job stored in the unique spool 41 belongs in accordance with the notification from the web application 34.

S50: The print server resident program 33 starts printing the EMF data of the job group with the highest priority in the unique spool 41. The print server resident program 33 starts printing the print jobs belonging to one job group in order of the date and time of receipt, etc. In other words, the print server resident program 33 starts printing on a job group basis. In other words, the print server resident program 33 gives priority to printing print jobs belonging to one job group over print jobs of other job groups.

S51: The print server resident program 33 requests the GDI 35 to print the EMF data on a job group basis using the real printer driver 36. Upon receiving the request, the GDI 35 extracts the EMF data from the unique spool 41 and stores it in the spool 42 for the real printer driver.

S52: The real printer driver 36 converts the EMF data in the real printer driver spool 42 to RAW data and re-stores it in the real printer driver spool 42.

S53: The spooler of the print server 30 passes the RAW data from the real printer driver spool 42 to the port monitor 37.

S54: The port monitor 37 inputs the RAW data to the printer 20. This allows the printer 20 to execute the print job and print the RAW data.

As a result, print jobs can be grouped without relying on a specific model of printer driver, and the print server 30 can execute print jobs on a job group basis.

<Print Job Allocation Using Allocation Table>
33 is an example of a flowchart for explaining the distribution of print jobs using a distribution table and a distribution key definition. Note that in the setting information DB 38, "Automatically distribute jobs to job groups" is ON.

First, the print server resident program 33 retrieves one print job from the EMF spool (server) 32 (S21).

The print server resident program 33 determines whether a distribution table has been created (exists) (S22).

If the determination in step S22 is Yes, the print server resident program 33 determines whether the print job has a sorting key value registered in the sorting table and whether the enable flag for the sorting key registered in the sorting key definition is ON (S23). The print settings of the print job are stored in a DEVMODE structure. The position of the value in the DEVMODE structure of the item specified by the sorting key is registered in the sorting key definition. The print server resident program 33 obtains the print setting item identified by the above position from the DEVMODE structure and determines whether the EMF data matches the sorting table (grouping conditions).

If the determination in step S23 is Yes, the print server resident program 33 determines whether a destination job group already exists (S24). The destination job group is identified, for example, by the ID of the distribution table.

If the determination in step S24 is Yes, the print server resident program 33 registers the print job in the job group to which it is assigned in the unique spool 41 (S25).

If the determination in step S24 is No, the print server resident program 33 creates a new job group using the destination job group name in the distribution table, and registers the job in the created job group (S24-2).

If the determination in step S22 is No, the print server resident program 33 determines whether the "enable flag" of the distribution key definition is in the default state (only key No. 01 and 04 are ON) (S26).

If the determination in step S26 is No, the print server resident program 33 causes the client PC 10 to display an error message stating "If a distribution table has not been created, please use the distribution key definition in its default state" (S27). This is because without a distribution table, there is no destination job group, and therefore distribution may not be possible unless the "enablement flag" is in its default state. In this case, the print job is distributed to a job not belonging to a group.

If the determination in step S26 is Yes, the print server resident program 33 determines whether a destination job group specified by the paper name of the print job already exists (S28). This is because when the "enable flag" is in the default state, assignment is based on the paper name. Note that since a paper name is assigned to the job group, the print server resident program 33 can determine whether a destination job group has already been created.

If the determination in step S28 is Yes, the print server resident program 33 saves the print job in an existing job group that has the paper name as the job group name (S29). In this way, the print server resident program can distribute EMF data to job groups without the administrator having to create an "allocation table."

If the determination in step S28 is No, and if the determination in step S23 is No, the print server resident program 33 determines whether "Automatically create a 'standard' type job group based on the paper name" is selected in the setting information DB 38 (S30).

If the determination in step S30 is Yes, the print server resident program 33 creates a new job group with the paper name as the job group name and saves the print job (S31). The print server resident program 33 automatically creates a job group based on the paper name, reducing the burden on the administrator without the administrator having to define a job group each time.

If the determination in step S30 is No, the print server resident program 33 saves the print job in the non-group jobs (S32).

As described above, the print server resident program 33 can group together print jobs that share common print settings such as paper size. In this embodiment, the end user or administrator does not need to create "bibliographic information XML that describes job attributes."

<About the DEVMODE structure>
The following provides additional information about the DEVMODE structure. The DEVMODE structure is a memory structure that stores print setting information (paper size, number of copies, print orientation, paper feed tray, resolution, etc.) specified by the end user when printing. The DEVMODE structure is provided by the OS, but applications can also reference it.

The DEVMODE structure contains an area called the private area (extension area). The printer's unique setting information is stored in this private area.

For example, Figure 34 shows an example of a print settings screen (basic settings) for a certain printer driver. The end user can set various print settings, such as "paper size" 321 and "number of copies" 323. The print setting information for these basic settings is stored in a standard area of the DEVMODE structure.

Figure 35 is an example of a print settings screen (extended settings) for a certain printer driver. Information such as "Enhanced Copy" in Figure 35 (improving density when copying) is not a function found on typical printers, so there is no corresponding member in the standard area of the DEVMODE structure. Print setting information related to such extended settings is stored in the private area of the DEVMODE structure.

Basic settings such as "paper size" can also be set by end users in application-specific settings screens (such as "Page Setup").

Figure 36 shows an example of a screen where an end user specifies the paper size on the "Page Setup" screen of a spreadsheet program. In many applications, the "Paper Size" 361 specification on the application-specific setting screen and the "Paper Size" specification on the driver setting screen displayed by the application are automatically synchronized and saved in the DEVMODE structure.

For applications where settings are not synchronized, the "paper size" in the application-specific settings screen generally takes priority and is saved in the DEVMODE structure (the "paper size" specified in the driver settings screen is ignored).

By the way, settings such as "paper size" and "copy enhancement" are set by the end user when printing by changing the default settings that are already displayed on the settings screen. The default values that are displayed on the settings screen immediately after installing the printer driver are determined by the printer driver.

The initial values displayed on the setting screen can be changed by the system administrator on the Windows (registered trademark) "Standard Settings" screen (the "Standard Settings" screen can be operated only by a system administrator with administrator privileges).
By changing the settings on the "Standard Settings" screen, the end user can change the initial values on the print settings screen that is displayed when printing.
The "Default Settings" screen can be displayed by right-clicking the printer on the Windows (registered trademark) "Devices and Printers" screen and clicking the "Default Settings..." button on the "Advanced Settings" tab.

Figure 37 is an example of the "Standard Settings" screen operated by a system administrator. On the "Standard Settings" screen, the system administrator changes the initial value of "Enhanced Copy" 362 from "Off" to "On." On this screen, when the system administrator checks the check box for "Enhanced Copy" 362 and then presses the [Apply] button, the initial value of "Enhanced Copy" 362 is changed to "On."

The changed initial value is saved in the following location in the registry:
Registry key name:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Print \ Printers \ (Printer name)
Registry key value:
Default DevMode
Figure 38 shows an example of the Registry Editor screen. Since "paper size" and the like are standard members of the DEVMODE structure, the byte in Default DevMode in which they appear is fixed. What value represents what paper is also usually fixed (the situation is slightly different for paper defined by the printer driver or user-defined paper, but these can be treated as known in advance).

However, printer driver-specific settings such as "Enhanced Copy" are stored in the private area (extension area) of the DEVMODE structure. Information such as which byte of Default DevMode 363 indicates "Enhanced Copy", what value means "Yes" and what value means "No" is determined independently by the printer manufacturer and is not publicly available.

However, by changing and saving the "Enhanced Copy" setting on the "Standard Settings" screen in Figure 37 and having the driver setting registration program 40 monitor the changes in the Default DevMode data, it is possible to determine information such as which byte is "Enhanced Copy," what value is "Yes," and what value is "No."

In this embodiment, as described above, the driver setting registration program 40 monitors changes in the Default DevMode data and registers the printer driver setting item values in the "settings database."

<Major Effects>
As described above, in the printing system 1 of this embodiment, the print server resident program 33 groups together print jobs that have common print settings such as paper size.
Since the print job is EMF data, restrictions on the model, printer driver, etc. can be reduced. Since the real printer driver 36 executes print jobs in groups, the number of paper changes can be reduced, improving the printer's operating rate. In addition, an upstream system is not required from the printer 20's perspective.

The print server resident program 33 also automatically obtains print settings such as paper name and paper size from the DEVMODE structure. End users do not need to set print settings for grouping each time.

In addition, in this embodiment, the print server resident program 33 can group print jobs based on the print settings stored in the private area of the DEVMODE structure.

<Other application examples>
The above describes the best mode for carrying out the present invention using examples, but the present invention is not limited to these examples in any way, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention.

For example, in this embodiment, the roles of the end user, operator, and administrator are clearly stated, but any one of the end user, operator, and administrator may perform all of the operations described in this embodiment.

The configuration examples in FIG. 4 and other figures are divided according to the main functions to make it easier to understand the processing by the client PC 10 and the print server 30. The method of dividing the processing units or the names of the processing units does not limit the present invention. The processing by the client PC 10 and the print server 30 can be divided into even more processing units depending on the processing content. It can also be divided so that one processing unit includes even more processes.

Furthermore, the devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, the print server 30 includes multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other over any type of communication link, including a network, shared memory, etc., and perform the processes disclosed herein.

Furthermore, the print server 30 can be configured to share the processing steps disclosed in this embodiment, such as those shown in FIG. 32, in various combinations. For example, a process executed by a specific unit can be executed by multiple information processing devices possessed by the print server 30. Furthermore, the print server 30 may be integrated into a single server device, or may be divided into multiple devices.

Each function of the embodiments described above can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and devices such as an ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), FPGA (Field Programmable Gate Array), and conventional circuit modules designed to execute each function described above.

The GDI 13 is an example of an intermediate data generating means, and the print server resident program 33 is an example of a print control means. The driver setting registration program 40 is an example of a condition creating means.

1 Printing system 10 Client PC
20 Printer 30 Print server 50 Terminal device

JP 2020-113115 A

Claims (14)

A printing system in which an information processing device prints a print job transmitted from an information processing terminal using an image forming device,
an intermediate data generating means for converting print job data received from the information processing terminal by selecting a real printer driver to be used for printing into EMF data using a virtual printer driver ;
a print control means for creating a plurality of job groups using a print setting related to paper as a grouping condition among print settings that can be specified when executing the print job, and for allocating the EMF data to one of the job groups based on the print setting of the EMF data generated by the intermediate data generating means and the grouping condition ;
the print control means converts the plurality of EMF data assigned to the predetermined job group into RAW data by the real printer driver, and after starting printing of the RAW data, if print settings of a print job received from the information processing terminal belong to grouping conditions of the predetermined job group, assigns the print job to the predetermined job group and prints the print job on the image forming device in priority over the EMF data assigned to a job group other than the predetermined job group.
A printing system comprising : 2. The printing system according to claim 1, wherein the print control means distributes the EMF data having the print settings that match the grouping condition to the same job group. The printing system according to claim 2, wherein the printing control means generates the job group to which the EMF data that meets the grouping conditions is assigned when the EMF data meets the grouping conditions and when there is no job group that meets the grouping conditions . The information processing device provides a web application to a terminal device;
the terminal device displays, via the Web application, a screen for accepting settings for automatically generating the job group, and accepts the settings for automatically generating the job group from an administrator;
The printing system according to claim 3 , wherein a setting for automatically generating the job group is transmitted to the information processing device. a condition creating means for automatically creating the print setting items;
the condition creation means creates a sorting key definition in which position information of the print setting item in a DEVMODE structure is associated with the print setting item;
A printing system according to any one of claims 2 to 4, wherein the printing control means obtains the print setting items identified by the position information from the DEVMODE structure of the EMF data according to the grouping conditions, and determines whether the EMF data conforms to the grouping conditions. The information processing device provides an application to a terminal device;
the terminal device displays, via the application, a screen for accepting settings of the print setting items stored in a private area of a DEVMODE structure, and accepts the settings of the print setting items from an administrator;
Transmitting the settings of the print setting items stored in a private area of a DEVMODE structure to the information processing device;
6. The printing system according to claim 5, wherein the condition creating unit registers the print setting items stored in a private area of a DEVMODE structure in the sorting key definition. The printing system according to claim 6, wherein the condition creation means detects position information of the print setting item in the private area of the DEVMODE structure based on a registry key that changes when receiving the setting of the print setting item stored in the private area of the DEVMODE structure, and associates the position information with the print setting item stored in the private area of the DEVMODE structure. the terminal device displays a screen for accepting settings of the grouping condition via a Web application provided by the information processing device, and accepts the settings of the grouping condition from an administrator;
The printing system according to claim 6 or 7, wherein the grouping condition is transmitted to the information processing device. the terminal device displays a screen for receiving a name of a job group to which the EMF data is to be distributed, a screen for receiving items of the print setting of the distribution key definition, and a print setting screen for receiving values of the items;
the terminal device transmits to the information processing device a name of the job group, an item of the print setting of the distribution key definition, and a value of the item;
A printing system according to any one of claims 6 to 8, wherein the condition creation means creates the grouping conditions by associating the name of the job group, the print setting items of the distribution key definition, and the values of the items. A printing system as described in claim 8, wherein when the grouping condition does not exist, the printing control means assigns the EMF data generated by the intermediate data generation means to the job group having the paper name of the print setting contained in the EMF data as the name of the job group. If the grouping condition does not exist and the job group having the paper name of the print setting included in the EMF data as the job group name does not exist,
9. The printing system according to claim 8, wherein the print control means distributes the EMF data generated by the intermediate data generating means to a job not belonging to a group. A printing method performed by a printing system in which an information processing device prints a print job transmitted from an information processing terminal using an image forming device, comprising:
a step in which intermediate data generating means converts print job data received from the information processing terminal by selecting a real printer driver to be used for printing into EMF data using a virtual printer driver ;
a step in which a print control means creates a plurality of job groups using a print setting related to paper as a grouping condition among print settings that can be specified when executing the print job, and allocates the EMF data to one of the job groups based on the print setting of the EMF data generated by the intermediate data generation means and the grouping condition ;
the print control means converts the plurality of EMF data assigned to the predetermined job group into RAW data by the real printer driver, and after starting printing of the RAW data, if a print setting of a print job received from the information processing terminal belongs to a grouping condition of the predetermined job group, assigns the print job to the predetermined job group and prints the print job on the image forming device in priority over the EMF data assigned to a job group other than the predetermined job group;
A printing method comprising the steps of: An information processing apparatus that prints a print job transmitted from an information processing terminal by an image forming apparatus,
an intermediate data generating means for converting print job data received from the information processing terminal by selecting a real printer driver to be used for printing into EMF data using a virtual printer driver ;
a print control means for creating a plurality of job groups using a print setting related to paper as a grouping condition among print settings that can be specified when executing the print job, and for allocating the EMF data to one of the job groups based on the print setting of the EMF data generated by the intermediate data generating means and the grouping condition ;
The printing control means converts the multiple EMF data assigned to a specific job group into RAW data using the real printer driver, and after printing of the RAW data begins, if the print settings of the print job received from the information processing terminal belong to the grouping conditions of the specific job group, assigns the print job to the specific job group and prints it on the image forming device in priority over the EMF data assigned to a job group other than the specific job group. An information processing apparatus that prints a print job transmitted from an information processing terminal using an image forming apparatus,
an intermediate data generating means for converting print job data received from the information processing terminal by selecting a real printer driver to be used for printing into EMF data using a virtual printer driver ;
a print control means for creating a plurality of job groups using a print setting related to paper as a grouping condition among print settings that can be specified when executing the print job, and distributing the EMF data to one of the job groups based on the print setting of the EMF data generated by the intermediate data generating means and the grouping condition;
The printing control means converts a plurality of the EMF data assigned to a specific job group into RAW data using the real printer driver, and after starting printing of the RAW data, if the print settings of the print job received from the information processing terminal belong to the grouping conditions of the specific job group, assigns the print job to the specific job group and prints it on the image forming device in priority over the EMF data assigned to a job group other than the specific job group.

Images