Multifunctional printing system with queue management

This invention relates generally to a multifunctional printing system with one or more queues and, more particularly, to a contention management scheme which contemplates both the prioritization of one or more jobs, on the basis of the source at which the one or more jobs were developed, for the sake of managing insertion of the prioritized one or more jobs into the one or more queues, and that jobs will be processed in accordance with a preprogrammed set of rules.

Electronic printing systems typically include an input section, sometimes referred to as an input image terminal ("IIT"), a controller, and an output section or print engine, sometimes referred to as an image output terminal ("IOT"). In one type of electronic printing system, manufactured by Xerox® Corporation, known as the DocuTech® electronic printing system, a job can be inputted to the printing system from, among other sources, a network or a scanner.

The concept of a print queue is integral to the operation of various digital reproduction systems. Through appropriate queue management, a job currently in the process of being printed can be interrupted with an interrupt job in a manner disclosed in US-A-5,206,735.

Referring particularly to the '735 Patent, a special job is obtained from a mass memory, shown by way of a "job file", and inserted into the queue at a "logical point" with respect to the job currently being processed. When printing reaches the logical point at which the special job was inserted, the job currently being processed is interrupted so that the special job is processed. Upon completion of the processing of the special job, processing of the interrupted job is resumed.

The queue disclosed in the '735 Patent is managed, in the normal case, on a first-come-first-serve ("FIFO") basis except when special or interrupt jobs are inserted into the queue. In the illustrated embodiment of the '735 Patent, the interrupt job is inserted into the queue as described above except when an interrupt job is currently in the process of printing. When an interrupt job is currently printing, a second interrupt job is placed behind the interrupt job in process. Essentially, priority is given to the interrupt job currently in process. The concerns associated with interrupting a first interrupt job with a second interrupt job are also addressed in US-A-5,535,009.

The queue management arrangement of the '735 Patent is not optimally suited for use in a multifunctional context because it does not differentiate among job types for the purpose of managing the queue. Consequently, a print job cannot, in many common instances, be given priority over a copy job, or <i>vice versa.</i> Systems particularly well suited for use with a multifunctional printing systems are disclosed in US-A-4,947,345 and Japanese Application 58-152821.

Referring particularly to the '345 Patent, a first queue is used to store copy and print jobs, while a second queue, communicating with the first queue, is used to store facsimile ("fax") jobs in parallel with the first queue. After a preselected number of one or more fax jobs is stored in the second queue, the stored job(s) is placed in front of the jobs of the first queue so that the one or more fax jobs can be printed ahead of the currently queued copy/print jobs.

While the queue management scheme of the '345 Patent accommodates for job differentiation, it only does so in a limited manner. For instance, the fax queue can be given preferential treatment relative to the copy/print queue , so that one or more fax jobs can be printed ahead of a copy or print jobs. No mechanism for treating a given copy or print job preferentially, however, is suggested. Additionally, in the approach of the '345 Patent, a copy or print job can get "stuck" in the copy/print job queue when multiple fax jobs are given preferential processing treatment relative to the copy/print jobs

Essentially, the '345 Patent, while well intended for its limited purpose, lacks the sort of flexible queue management that is required by multifunctional printing systems whose capabilities and uses are increasing at an ever-increasing rate. It would be desirable to provide a multifunctional printing system that provides a wide range of queue management so that the corresponding system can accommodate for both the specific needs of many different users and the many different types of uses demanded by those users. At the same time, it would desirable to provide a queue management system for a multifunctional printing system facilitating the appropriate thruput of all types of jobs which might be encountered by the multifunctional printing system.

In accordance with the presently disclosed invention there is provided a method a multifunctional printing system with a queue for holding a plurality of jobs in anticipation of processing the same. The multifunctional printing system includes a controller, for facilitating placement of the plurality of jobs into the queue, and the queue receives one or more jobs of a first user type or a second user type. The method comprises: a) placing a first job and a second job in the queue, each of the first and the second jobs being of the first user type; b) determining, with the controller, whether a third job is of the first user type or the second user type; c) in response to determining that the third job is of the first user type, processing the third job after each of the first and second jobs; and d) in response to determining that the third job is of the second user type, processing the third job prior to at least the second job.

A particular embodiment of the present invention will now be described with reference to the accompanying drawings, in which:- <ul id="ul0001" list-style="none" compact="compact"><li>Figure 1 is a perspective view of a networked digital copier suitable for receiving a job developed in accordance with the present invention;</li><li>Figure 2 is a block diagram depicting a multifunctional, network adaptive printing machine;</li><li>Figure 3 is a block diagram of a video control module for the printing machine of Figure 2;</li><li>Figure 4 is a block diagram of a transfer module used in conjunction with the printing machine of Figure 3;</li><li>Figure 5 is a block diagram of a facsimile card used in conjunction with the video control module of Figure 3;</li><li>Figure 6 is a block diagram of a network controller for the printing machine of Figure 2;</li><li>Figure 7 is an elevational view of a queue used to store jobs pursuant to processing thereof;</li><li>Figure 8 is a schematic view of a job placement table stored in memory and used to place jobs in, among other places, the queue of Figure 7; and</li><li>Figures 9 and 10 comprise a schematic view depicting a manner in which jobs progress in a queue (see e.g., Figure 7) as a function of one aspect of a contention management scheme embodied in the present invention.</li></ul>

Referring to Figure 1 of the drawings, a digital copier system of the type suitable for use with the preferred embodiment is shown. As shown, the system includes a document feeder 1 and an operation (and display) panel 2. After desired conditions have been entered on the operation panel 2, the document feeder 1 conveys a document to a predetermined reading position on an image reading device 3 and, after the document has been read, drives it away from the reading position. The image reading device 3 illuminates the document brought to the reading position thereof. The resulting reflection from the document is transformed to a corresponding electric signal, or image signal, by a solid state imaging device, e.g., a CCD (Charge Coupled Device) image sensor. An image forming device 4 forms an image represented by the image signal on a plain paper or a thermosensitive paper by an electrophotographic, thermosensitive, heat transfer, ink jet or similar conventional system.

As a paper is fed from any one of paper cassettes 7 to the image on forming device 4, the device 4 forms an image on one side of the paper. A duplex copy unit 5 is constructed to turn over the paper carrying the image on one side thereof and again feed it to the image forming device 4. As a result, an image is formed on the other side of the paper to complete a duplex copy. The duplex copy unit 5 has customarily been designed to refeed the paper immediately or to sequentially refeed a plurality of papers stacked one upon the other, from the bottom paper to the top paper. The papers, or duplex copies, driven out of the image forming device 4 are sequentially sorted by a output device 6 in order of page or page by page.

Applications, generally 8, share the document feeder 1, operation panel 2, image reading device 3, image forming device 4, duplex unit 5, output device 6, and paper cassettes 7 which are the resources built in the copier system. As will appear, the applications include a copier application, a printer (IOT) application, a facsimile (Fax) application and other applications. Additionally, the digital copier system is coupled with a network by way of a conventional network connection 9.

Referring to Figure 2, a multifunctional, network adaptive printing system is designated by the numeral 10. The printing system 10 includes a printing machine 12 operatively coupled with a network service module 14. The printing machine 12 includes an electronic subsystem 16, referred to as a video control module (VCM), communicating with a scanner 18 and a printer 20. In one example, the VCM 16, which will be described in further detail below, coordinates the operation of the scanner and printer in a digital copying arrangement. In a digital copying arrangement, the scanner 18 (also referred to as image input terminal (IIT)) reads an image on an original document by using a CCD full width array and converts analog video signals, as gathered, into digital signals. In turn, an image processing system 22 (Figure 3), associated with the scanner 18, executes signal correction and the like, converts the corrected signals into multi-level signals (e.g. binary signals), compresses the multi-level signals and preferably stores the same in electronic precollation (EPC) memory 24.

Referring again to Figure 2, the printer 20 (also referred to as image output terminal (IOT)) preferably includes a xerographic print engine. In one example, the print engine has a multi-pitch belt (not shown) which is written on with an imaging source, such as a synchronous source (e.g. laser raster output scanning device) or an asynchronous source (e.g. LED print bar). In a printing context, the multi-level image data is read out of the EPC memory 24 (Figure 3) while the imaging source is turned on and off, in accordance with the image data, forming a latent image on the photoreceptor. In turn, the latent image is developed with, for example, a hybrid jumping development technique and transferred to a print media sheet. Upon fusing the resulting print, it may be inverted for duplexing or simply outputted. It will be appreciated by those skilled in the art that the printer can assume other forms besides a xerographic print engine without altering the concept upon which the disclosed embodiment is based. For example, the printing system 10 could be implemented with a thermal ink jet or ionographic printer.

Referring specifically to Figure 3, the VCM 16 is discussed in further detail. The VCM 16 includes a video bus (VBus) 28 with which various I/O, data transfer and storage components communicate. Preferably, the VBus is a high speed, 32 bit data burst transfer bus which is expandable to 64 bit. The 32 bit implementation has a sustainable maximum bandwidth of approximately 60 MBytes/sec. In one example, the bandwidth of the VBus is as high as 100 Mbytes/sec.

The storage components of the VCM reside in the EPC memory section 30 and the mass memory section 32. The EPC memory section includes the EPC memory 24, the EPC memory being coupled with the VBus by way of a DRAM controller 33. The EPC memory, which is preferably DRAM, provides expansion of up to 64 MBytes, by way of two high density 32 bit SIMM modules. The mass memory section 32 includes a SCSI hard drive device 34 coupled to the VBus by way of a transfer module 36a. As will appear, other I/O and processing components are coupled respectively to the VBus by way of transfer modules 36. It will be appreciated that other devices (e.g. a workstation) could be coupled to the VBus by way of the transfer module 36a through use of a suitable interface and a SCSI line.

Referring to Figure 4, the structure of one of the transfer modules 36 is discussed in further detail. The illustrated transfer module of Figure 4 includes a packet buffer 38, a VBus interface 40 and DMA transfer unit 42 . The transfer module 36, which was designed with "VHSIC" Hardware Description Language (VHDL), is a programmable arrangement permitting packets of image data to be transmitted along the VBus at a relatively high transfer rate. In particular, the packet buffer is programmable so that the segment or packet can be varied according to the available bandwidth of the VBus. In one example, the packet buffer can be programmed to handle packets of up to 64 Bytes Preferably, the packet size would be reduced for times when the VBus is relatively busy and increased for times when activity on the bus is relatively low.

Adjustment of the packet size is achieved with the VBus interface 40 (Figure 4) and a system controller 44 (Figure 6). Essentially, the VBus interface is an arrangement of logical components, including, among others, address counters, decoders and state machines, which provides the transfer module with a selected degree of intelligence. The interface 40 communicates with the system controller to keep track of desired packet size and, in turn, this knowledge is used to adjust the packet size of the packet buffer 38, in accordance with bus conditions. That is, the controller, in view of its knowledge regarding conditions on the VBus 28, passes directives to the interface 40 so that the interface can adjust packet size accordingly. Further discussion regarding operation of the transfer module 36 is provided below.

More particularly, image transfer is facilitated with a DMA transfer unit which employs a conventional DMA transfer strategy to transfer the packets. In other words, the beginning and end addresses of the packet are used by the transfer unit in implementing a given transfer. When a transfer is complete, the interface 40 transmits a signal back to the system controller 44 so that further information, such as desired packet size and address designations, can be obtained.

Referring to Figures 2 and 3, three I/O components are shown as being coupled operatively to the VBus 28, namely a FAX module 48, the scanner or IIT 18, and the printer or IOT 20; however, it should be recognized that a wide variety of components could be coupled to the VBus by way an expansion slot 50. Referring to Figure 5, an implementation for the FAX module, which is coupled to the VBus 28 by way of transfer module 36b, is discussed in further detail. In the preferred embodiment, a facsimile device (FAX) 51 includes a chain of components, namely a section 52 for performing Xerox adaptive compression/decompression, a section 54 for scaling compressed image data, a section 56 for converting compressed image data to or from CCITT format, and a modem 58, preferably manufactured by Rockwell Corporation, for transmitting CCITT formatted data from or to a telephone, by way of a conventional communication line.

Referring still to Figure 5, each of the sections 52, 54 and 56 as well as modem 58 are coupled with the transfer module 36b by way of a control line 60. This permits transfers to be made to and from the FAX module 48 without involving a processor. As should be understood, the transfer module 36b can serve as a master or slave for the FAX module in that the transfer module can provide image data to the FAX for purposes of transmission or receive an incoming FAX. In operation, the transfer module 36b reacts to the FAX module in the same manner that it would react to any other I/O component. For example, to transmit a FAX job, the transfer module 36b feeds packets to the section 52 through use of the DMA transfer unit 42 and, once a packet is fed, the transfer module transmits an interrupt signal to the system processor 44 requesting another packet. In one embodiment, two packets are maintained in the packet buffer 38 so that "ping-ponging" can occur between the two packets. In this way, the transfer module 36b does not run out of image data even when the controller cannot get back to it immediately upon receiving an interrupt signal.

Referring again to Figure 3, the IIT 18 and IOT 20 are operatively coupled to the VBus 28 by way of transfer modules 36c and 36d. Additionally, the IIT 18 and the IOT 20 are operatively coupled with a compressor 62 and a decompressor 64, respectively. The compressor and decompressor are preferably provided by way of a single module that employs Xerox adaptive compression devices. Xerox adaptive compression devices have been used for compression/decompression operations by Xerox Corporation in its DocuTech® printing system. In practice, at least some of the functionality of the transfer modules is provided by way of a 3 channel DVMA device, which device provides local arbitration for the compression/decompression module.

As further illustrated by Figure 3, the scanner 18, which includes the image processing section 22, is coupled with an annotate/merge module 66. Preferably, the image processing section includes one or more dedicated processors programmed to perform various desired functions, such as image enhancement, thresholding/screening, rotation, resolution conversion and TRC adjustment. The selective activation of each of these functions can be coordinated by a group of image processing control registers, the registers being programmed by the system controller 44. Preferably, the functions are arranged along a "pipeline" in which image data is inputted to one end of the pipe, and image processed image data is outputted at the other end of the pipe. To facilitate throughput, transfer module 36e is positioned at one end of the image processing section 22 and transfer module 36c is positioned at another end of the section 22. As will appear, positioning of transfer modules 36c and 36e in this manner greatly facilitates the concurrency of a loopback process.

Referring still to Figure 3, arbitration of the various bus masters of the VCM 16 is implemented by way of a VBus arbiter 70 disposed in a VBus arbiter/bus gateway 71. The arbiter determines which bus master (e.g. FAX module, Scanner, Printer, SCSI Hard Drive, EPC Memory or Network Service Component) can access the VBus at one given time. The arbiter is made up of two main sections and a third control section. The first section, i.e., the "Hi-Pass" section, receives input bus requests and current priority selection, and outputs a grant corresponding to the highest priority request pending. The current priority selection input is the output from the second section of the arbiter and is referred to as "Priority Select". This section implements priority rotation and selection algorithm. At any given moment, the output of the logic for priority select determines the order in which pending requests will be serviced. The input to Priority Select is a register which holds an initial placement of devices on a priority chain. On servicing requests, this logic moves the devices up and down the priority chain thereby selecting the position of a device's next request. Control logic synchronizes the tasks of the Hi-Pass and the Priority Select by monitoring signals regarding request/grant activity. It also prevents the possibility of race conditions.

Referring to Figure 6, the network service module 14 is discussed in further detail. As will be recognized by those skilled in the art, the architecture of the network service module is similar to that of a known "PC clone". More particularly, in the preferred embodiment, the controller 44, which preferably assumes the form of a SPARC processor, manufactured by Sun Microsystems, Inc., is coupled with a standard SBus 72. In the illustrated embodiment of Figure 6, a host memory 74, which preferably assumes the form of DRAM, and a SCSI disk drive device 76 are coupled operatively to the SBus 72. While not shown in Figure 6, a storage or I/O device could be coupled with the SBus with a suitable interface chip. As further shown in Figure 6, the SBus is coupled with a network 78 by way of an appropriate network interface 80. In one example, the network interface includes all of the hardware and software necessary to relate the hardware/software components of the controller 44 with the hardware/software components of the network 78. For instance, to interface various protocols between the network service module 14 and the network 78, the network interface could be provided with, among other software, Netware® from Novell Corp.

In one example, the network 78 includes a client, such as a workstation 82 with an emitter or driver 84. In operation, a user may generate a job including a plurality of electronic pages and a set of processing instructions. In turn, the job is converted, with the emitter, into a representation written in a page description language, such as PostScript. The job is then transmitted to the controller 44 where it is interpreted with a decomposer, such as one provided by Adobe Corporation.

Referring again to Figure 3, the network service module 14 is coupled with the VCM 16 via a bus gateway 88 of the VBus arbiter/bus gateway 71. In one example, the bus gateway comprises a field programmable gate array provided by XILINX corporation. The bus gateway device provides the interface between the host SBus and the VCM VBus. It provides VBus address translation for accesses to address spaces in the VBus real address range, and passes a virtual address to the host SBus for virtual addresses in the host address range. A DMA channel for memory to memory transfers is also implemented in the bus gateway. Among other things, the bus gateway provides seamless access between the VBus and SBus, and decodes virtual addresses from bus masters, such as one of the transfer modules 36, so that an identifier can be obtained from a corresponding slave component. It will be appreciated by those skilled in the art that many components of the printing system 10 are implemented in the form of a single ASIC.

Referring to Figures 3, 4 and 6, further discussion regarding DMA transfer of each of the transfer modules 36 is provided. In particular, in one example, the images of a job are stored in the host memory 74 as a series of blocks. Preferably, each block comprises a plurality of packets. In operation, one of the transfer modules 36 is provided, by the controller 44, with the beginning address of a block and the size of the block. In turn, for that block, the transfer module 36 effects a packet transfer and increments/decrements a counter. This procedure is repeated for each packet of the block until the interface 40 determines, by reference to the counter, that the last packet of the block has been transferred. Typically, for each stored image, several blocks are transferred, in a packet-by-packet manner, as described immediately above.

Referring to Figure 7, a queue of jobs 200 ready for processing with the printer 20 (Figure 1) is shown. As with other conventional print queues, the job currently being printed is displayed in a window 202 and buttons 204 can be employed to scroll the list of jobs up or down. It should be appreciated that in a multifunctional machine, of the type discussed in the Background above, more than one queue would preferably be employed to accommodate for the various services offered. For example, jobs waiting to be scanned would reside in a scan queue while jobs waiting to be faxed would reside in a fax queue. Essentially the print or mark queue of Figure 7 may be just one of the plurality of queues employed in the printing system 10. Additionally, it should be appreciated that jobs may be inserted into the queues in a manner consistent with that disclosed by US-A-5,206,735. Finally, it will be appreciated that the queue could be maintained in, among other locations, the VCM Figure 3 or the Network Service Module (Figure 6).

In any multifunctional product (also referred to below as "MF Engine"), such as the printing system 10 described above, there is always the potential of multiple users requiring access to one or more subsystems at the same time. This access contention can occur in several areas of the MF Engine either as contention for a single resource e.g., EPC memory 24 (Figure 3), or as a contention for multiple kinds of resources e.g., EPC memory and IIT. When a contention situation arises, the printing system must respond in a predictable, and controlled manner that satisfies the various users.

In the preferred embodiment, at least two contention management methods are contemplated: <ul id="ul0002" list-style="none" compact="compact"><li>1. First In First Out (FIFO) Job Management.</li></ul>

In this method contention is handled on a first come first serve basis. Jobs submitted ahead of other jobs have first use of the required resource. Other jobs requesting that service are numerically ordered by their time of arrival and eventually have the opportunity to use the service. <ul id="ul0003" list-style="none" compact="compact"><li>2. In this method access to resources is managed with a "Key Operator/System Administrator ("KO/SA") defined algorithm. (See Table 1 below). With this algorithm, the KO/SA can arrange to have jobs defined according to job type, immediate walkup need, history of interruptions and other relevant factors. The algorithm can be configured to manage job contention in accordance with the desires of a typical printing system user. Since it is flexibly programmable, the algorithm can be made to accommodate for FIFO. In other words, FIFO is a subset of the capabilities of this algorithm.</li></ul>

It is contemplated that at least five job types will be handled by the KO/SA in printing system 10: <ul id="ul0004" list-style="none" compact="compact"><li>1. Copy Print or Walk-Up Jobs: Walk up user jobs requiring the use of the IIT and the corresponding marking resource;</li><li>2. Auto Report Print: Reports that are automatically printed, such as reports of machine or copier use, error logs, fax reports, etc. The reports, which are defined by the SA/KO, are printed from memory resources and require marking engine usage;</li><li>3. Net Print: Included in this job category are the following: <ul id="ul0005" list-style="none" compact="compact"><li>a) Jobs arriving from network sources, via the network service module 14 (Figure 1), which require marking resource,</li><li>b) Network service module (also referred to as "ESS") soft mailbox jobs activated by a walk-up or remote user, and</li><li>c) Any other jobs originating from the ESS or network;</li></ul></li><li>4. Fax Mailbox: Included in this job category are the following: <ul id="ul0006" list-style="none" compact="compact"><li>a) Fax receives (secure) which have been stored on the system for printout at a user's request,</li><li>b) Local reports such as system usage or fax logs, and</li><li>c) Any other jobs originating from the EPC memory 24 (Figure 3) or the printing system (also referred to as "MFSYS");</li></ul></li><li>5. Fax Print: Incoming Fax jobs that are meant to be printed immediately. Such jobs are captured in EPC memory 24 and then printed immediately.</li></ul>

The following terminology should be useful in obtaining a more complete understanding of the present description:

Authorized User: a user having a higher authority level than a casual user, but access rights less than that of a KO/SA. This is a reserved authority level intended for VIP Users.

Interrupt Level: A resource may be interrupted from the job it is currently working on. If this occurs, it is called a first level interrupt or interrupt level 1. If a job running in interrupt is interrupted itself, then this is a second level interrupt.

Job Type Priority: A priority assigned according to job or user type. An exemplary priority assignment, based on job type, is provided below.

Resource: Any mechanical, electronic or software component required to process a job.

Marking Resource: The resource used to print a job on a given media type.

Memory Resource: Types of Read/Write memory used by the printing system, e.g. memories 24, 34 (Figure 3), 74 and 76 (Figure 6).

Marked Job: A job which has been printed. This term is more generic than "printed job" and does not imply a particular method used for writing to the type of media.

Next to Print: This is the nomenclature for a job which is at the top of the queue of jobs and under stable/normal conditions, will be the " next to print" from the queue.

An important embodiment uses the following exemplary table, including contention priority algorithm presets, to optimize contention management: <tables id="tabl0001" num="0001"><img file="EP0873007A2_D0001.tif" /></tables><tables id="tabl0002" num="0002"><img file="EP0873007A2_D0002.tif" /></tables>

This table, to which the description below relates, permits the KO/SA to define how the system should operate when a situation arises. The table serves to define what types of jobs exist in the system and how given contention situations should be managed. As will be appreciated by those skilled in the art, table headings for the above table, as well as comparable tables below, may vary as a function of system architecture so that, for example, certain walk-up jobs, such as ESS MB (mailbox) could also be viewed as net print jobs.

Referring specifically to Table 1, the columns of the table list all the types of user jobs (where contention can occur) that can occur in the machine. The rows of the table list the type of contention that can occur. The intersection of rows and columns define the machine behavior for that job type in that particular contention situation.

The following contention management feature descriptions are best understood by reference to the above Table 1:

<u>Authorized User Override:</u> This feature setting allows an authorized user (AU) to interrupt other jobs on the IOT. The AU has interrupt capability override for all types of jobs, even ones that have had their interrupt limitation exceeded, e.g., a print job which has interrupt limitation set at 4 has been interrupted 4 times by other jobs and is currently using the marking resource.

AU tagged jobs are priority 1 (highest). If the table setting is 'Y' the job will always interrupt other lower priority jobs. If the setting is 'N' it will honor the row 4 entry (Table 1) for the job type of the currently printing job.

<u>Maximum ("Max" or "MAX") Number of Times a Job Type Can Be Interrupted</u>: This defines how many times a job can be interrupted. Once the set number of allowable times a job may be interrupted has been reached, the job can no longer be interrupted and will be allowed to finish its operation on the resource it is using. An exception to this rule would be the AU Over-ride. The calculation of the number times a job has been interrupted is a summation of all the times other jobs have interrupted the job, e.g., a Copy Job has been interrupted at different times by a Fax job, and four different Print jobs, the MAX # of interrupts was set to 4, hence the MAX # of interrupts setting has been exceeded.

<u>Interrupt Now (Y) or Do Job Next (N</u>): When an Interrupt hard button on the printing machine 12 (Figure 1) is enabled, any job which is tagged as an interrupt button job will receive a level 2 priority. If the Table 1, row 3 is set to 'Y' for a job type then that job type will override a 'N' in row 4 of the table and interrupt other jobs which are of lower priority.

Higher Priority Job Type Interrupt Enabled: If this is enabled with 'Y' then the Job Type may be interrupted by a Higher Priority Job type, or a Resource Exceeded condition (see table. 2).

<u>Specify Job Type Priority</u>: This defines the priority of the jobs based on job type. The basic types of jobs are listed in row 1 of Table 1. These generic job categories encompass a variety of specific job types so not all types of jobs need to be represented by the Table.

Operation: In one embodiment jobs are placed in a queue as they are submitted to the printing system. If one type of job has a higher priority than another type of job then it will be placed before that job in the queue. If two jobs have the same assigned priority then they are queued according to the time stamp they receive upon entering the queue (i.e., FIFO managed). Jobs queued and not able to mark because the marking engine has the wrong media or jobs in the queue held for similar reasons, will be bypassed by other jobs which are still able to use the marking engine. Once a job is at the top of the queue, if it has a higher priority than the currently printing job and if "Higher Priority Interrupt" is enabled, the higher priority job will interrupt the currently printing job.

<u>Timer for Jobs in the Queue</u>: This assures that a job will not become trapped in the queue of jobs by groups of higher priority jobs. A job type which has been in the queue for the maximum allocated time will be elevated to a job priority as described below. Nonetheless, the elevated job will obey all the rules defined by the table settings. In a situation where more than one job has reached its allocated time limit then they will be FIFO'd at the top of the queue.

Referring to the following Table 2, KO/SA settings may be provided for a "Resource Exceeded Condition": <tables id="tabl0003" num="0003"><table frame="all"><title>Table 2</title><tgroup cols="7" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="22.50mm" /><colspec colnum="2" colname="col2" colwidth="22.50mm" /><colspec colnum="3" colname="col3" colwidth="22.50mm" /><colspec colnum="4" colname="col4" colwidth="22.50mm" /><colspec colnum="5" colname="col5" colwidth="22.50mm" /><colspec colnum="6" colname="col6" colwidth="22.50mm" /><colspec colnum="7" colname="col7" colwidth="22.50mm" /><thead valign="top"><row><entry namest="col1" nameend="col7" align="center">Error conditions which demand resource (s)</entry></row><row><entry namest="col1" nameend="col1" align="center">Condition That Demand Resource</entry><entry namest="col2" nameend="col2" align="center">param.</entry><entry namest="col3" nameend="col3" align="center">Copy Job Print</entry><entry namest="col4" nameend="col4" align="center">Auto Report Print Print</entry><entry namest="col5" nameend="col5" align="center">Net Print &amp; ESS MB Print</entry><entry namest="col6" nameend="col6" align="center">Fax MB Print Local Report Print</entry><entry namest="col7" nameend="col7" align="center">Fax Print</entry></row></thead><tbody valign="top"><row rowsep="0"><entry namest="col1" nameend="col1" align="center">If Fax memory is full, Interrupt</entry><entry namest="col2" nameend="col2" align="center">Y/N</entry><entry namest="col3" nameend="col3" align="center">Y</entry><entry namest="col4" nameend="col4" align="center">Y</entry><entry namest="col5" nameend="col5" align="center">Y</entry><entry namest="col6" nameend="col6" align="center">Y</entry><entry namest="col7" nameend="col7" align="center">n/a</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center">and Print immediately</entry><entry namest="col2" nameend="col2" /><entry namest="col3" nameend="col3" /><entry namest="col4" nameend="col4" /><entry namest="col5" nameend="col5" /><entry namest="col6" nameend="col6" /><entry namest="col7" nameend="col7" /></row></tbody></tgroup></table></tables>

This condition or parameter arises when the memory for accommodating Fax Print is exceeded by a preselected threshold. In particular, if upon receipt of a Fax job, the Fax Memory resource becomes full and the IOT is printing another job, this will enable the current print job to be interrupted so that the Fax job can be printed. This parameter amounts to instantly promoting the FAX job through the queue to the IOT and interrupting the marking engine to attempt to free up FAX memory resources.

To save customers time in configuring their systems, configuration templates will be available for selection by the KO/SA. If selected by a KO/SA, the templates will auto configure the Contention Table (See e.g., Table 1 above) to settings which best support a customer's needs. The system will, in one example, provide for six templates from which the user can select. These templates will provide definition for a variety of system configurations ranging from FIFO configuration systems to Fax or Print centric systems. The manufacturing default settings will be included as one of the six templates. This template will be labeled as the default settings or "FIFO " template. A template for queue management control of jobs which does not include job priority interrupt will also be provided.

The six exemplary templates are as follows: <ul id="ul0007" list-style="none" compact="compact"><li>1) Basic FIFO without Priority Based Interrupt (Default Template): A basic FIFO queue managed template with all auto interrupt settings disabled is provided. The Interrupt button is enabled. (Row 3 of Table 1 set to 'Y'). All jobs set by this template will be treated as equal in priority and marking will occur on a first in first out basis with the exception of error handling marking.</li><li>2) Priority Based Favoring Copy without Priority Based Interrupt: A priority based template favoring Copy/Scan &amp; other walkup operations which also excludes the use of IOT interrupt job management is provided.</li><li>3) Priority Based Favoring Fax without Priority Based Interrupt: A priority based template favoring Fax incoming jobs followed by walkup jobs and then Print Jobs is provided. This template will not preferably include interrupt control of job management.</li><li>4) Priority Based Favoring Net Print without Priority Based Interrupt: A priority based template favoring Net Print jobs followed by walkup jobs and then by Fax direct print jobs is provided. The template will preferably not include interrupt control of job management.</li><li>5) Priority Based Favoring Copy/Scan with Job Type Interrupt Capability: A priority based template favoring Copy/Scan walk up jobs with interrupt settings enabled is provided.</li><li>6) Priority Based Favoring Print with Job Type Interrupt Capability: A priority based template favoring Copy/Scan walk up jobs with interrupt settings enabled is provided.</li></ul>

While the prior art has addressed the concept of interrupting an interrupt job with another interrupt job as well as the concept of printing one type of job (e.g. a copy job) before another type of job (e.g. print job), a problem arises when a system seeks to prioritize a large group of jobs including many job types. Referring to Figure 8, an embodiment in which a priority-based queue management scheme for determining the next job to obtain a system's resource is discussed. In the illustrated embodiment of Figure 8, a job's priority is based on the service that created the job. Preferably, the SA/KO sets the relative priority of each service from which a job is obtained in a queue.

As an overview, when a job requires a system resource, e.g. the scanner or printer, the job is placed in the job queue of the corresponding resource. When the resource is able to begin processing of a job, the resource obtains the highest priority job from its queue.

The priority-based queue management scheme is particularly useful in the area of job interrupt. The table of Figure 8 (also see Table 1 above) specifies when the job of one service can interrupt the job of another service. This view of interruption may be referred to as <i>interruptability.</i> The SA/KO preferably develops the interruptability matrix of Figure 8, which matrix sets forth the interruptability relationships between jobs of a plurality of service types. The interruptability scheme of the presently described embodiment incorporates the following concepts: <ul id="ul0008" list-style="none" compact="compact"><li>1) The SA/KO specifies the relative priority of each job (See Table 1 above) developed by a service (e.g. the priority of a "Remote File" (Figure 8) is relatively high since it can interrupt the processing of six other job types);</li><li>2) The SA/KO specifies the interruptability matrix for the jobs (e.g. copy job can interrupt a print job);</li><li>3) When a job is created within the printing system 10 (Figure 1), the job is assigned a priority based on service type;</li><li>4) Each system resource maintains a queue of jobs for the resource (in one example, the jobs in each queue are ordered according to job priority) ;</li><li>5) When a system resource is ready to process a job, the resource processes the job with the highest priority in its queue;</li><li>6) If a resource is processing a job and a new job requires the resource then if (the new job's priority is greater than the current job's priority) and (the current job is not an "interrupt" job) then if (the new job's service can interrupt the current job's service) then (the new job interrupts the current job) else (add the new job to the resource's job queue) else (add the new job to the resource's job queue); and</li></ul>

If the resource has an interrupted job and the resource completes processing all higher priority interrupting jobs, the resource resumes the proceeding of interrupted jobs.

Referring again to Figure 8, a few comments regarding the table thereof are in order. First, the matrix shows the interruptability of one service's job by another service's job. An interruptability decision exists when a job is using a system's resource and another higher priority job requires that resource. Second, a "yes" in a table entry indicates that the current job of a service (columns) can be interrupted by a higher priority job of the second service (rows). It should be appreciated that the matrix of Figure 8 is particularly useful in ordering jobs in a queue in that the relative priority of job type follows directly from the matrix. For example, a Remote File has the highest priority, in the example of Figure 8, and will preferably be given higher priority in processing than a Copy Job.

Referring now to Figures 9 and 10, another embodiment for prioritizing one or more jobs in a queue is discussed. Three concepts are considered by that embodiment:

The first concept relates to the above-discussed concept of enabling the KO/SA to specify a job's priority based on its input source or service (e.g., scanner application, ESS or network source or marking service). For each service/application/input source, the KO/SA preferably assigns a priority value (e.g., ranging from 0 to 50). In an example of the first concept, a system is configured with three inputs (scanner, net and fax). To provide scanner jobs with a greater priority than fax or net jobs, the KO/SA might value the inputs as follows:<maths id="math0001" num=""><math display="block"><mrow><mtext>fax: 10; net: 10; and scanner: 30</mtext></mrow></math><img file="EP0873007A2_D0003.tif" /></maths>

The second concept provides the KO/SA with the ability to increment a job's priority (beyond that of the first concept above) on the basis of the "reason for" or "method of" creating the job. In one aspect of the second concept, the printing system 10 would support priority valuation for two levels of interrupt, namely "interruptl" and "interrupt2". In one example, a scan or copy job, designated as "Print Now", would be treated as an interruptl job, while a net job with interrupt priority would be treated as an interrupt2 job. It will be understood that in an alternative approach which gives higher priority to jobs from the network, net jobs would be designated as interruptl jobs. In this one example, an interruptl job would be assigned a relatively high value (e.g., a value of 50), while and interrupt2 job would be assigned a relatively low value (e.g., a value of 20). In accordance with the first and second concepts, the respective values of an interrupt scan job, a scan job, an interrupt net job, and a net job would be 50, 30, 20, and 10.

The third concept provides for a preselected incremental increase to be added to the value of each queued job after a preselected time period. As will be appreciated, by reference to Table 1 above, the third concept contemplates adding an incremental value to each job value every time the job is interrupted by another job. In the third concept, the user preferably specifies two values, namely a time priority increment (ranging, for example, from 0-50) and a time interval (ranging from, for example, from 1-30 minutes). If no increment is desired, then the KO/SA specifies the time priority increment as equaling zero. In the embodiment of the third concept, a job value is not to exceed a preselected ceiling (e.g., a ceiling or maximum value of 100).

Referring specifically to Figures 9 and 10, an example, illustrating the three concepts discussed above, is provided. As will be noted, eventually, due to incrementing, Job C will achieve a level at which it cannot be interrupted by even a relatively high priority job.

Numerous features of the above-described embodiments will be appreciated by those skilled in the art:

First, queue management varying as a function of job or user priority is provided. In one example, a value is assigned to a job on the basis of either the service at which the job was originally developed or the user who developed the job. In this way a priority job can be placed into a queue in accordance with a preassigned priority or the authority level of the job originator. By considering the authority level of the job originator, a remote interrupt can be initiated. That is, a remote user or service with a sufficient level of authority may demand that his/her job be printed immediately at a remote printing machine.

Second, queue management can be facilitated through use of job priority table or matrix in which the priority of a given job type, relative to other job types, is preset as a function of the service at which the given job was developed. The matrix is particularly effective in addressing interruptability considerations. For example, the matrix can be used to determine whether a first job type should be allowed to interrupt the processing of a second job type.

Third, the queue management style of the preferred embodiment prevents a situation in which a job, due to its service origin, gets "stuck in the queue. In one preferred approach each queued job is assigned a value. As the job sets in the queue, its value increases to the extent that it must, within a selected time period, be processed, notwithstanding the original priority of the job. Alternatively, the value can be increased each time it is interrupted by another job.

Finally, the system can be programmed to automatically interrupt a job in process when an incoming job requires certain memory space and the current available memory space is unable to accommodate such requirement. This capability is particularly useful with respect to an incoming fax job since a shortage of memory, due to the current processing of one or more other jobs, can lead to a loss of a portion of the incoming fax job.