Inspection production control mechanism

Abstract

To disclose an art related to image processing in a printing system.SOLUTION: A system includes: at least one physical memory device to store a logic; and one or more processors connected with the at least one physical memory device. The one or more processors execute the inspection logic to capture a page image of a print job page printed on a print medium, determine a page identifier on the page image, determine whether the page identifier is within a first production range associated with a first inspection production, and perform inspection processing using a first inspection production on the page image when it is determined that the page identifier is within the first production range.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to the field of printing systems, and more particularly to image processing in printing systems. [Background technology]

[0002] High speed print production systems often implement a Print Verification System (PVS) to detect defects in the print data applied to the media (e.g., paper). Print defects are most often caused by impurities in the media or partial drying and clumping of ink at the orifices of the print nozzles. While in some cases the defects are tolerable, in other cases the defects cause the print to be rejected and destroyed. Summary of the Invention

[0003] In one embodiment, a system includes at least one physical memory device that stores inspection logic and one or more processors connected to the at least one physical memory device, where the one or more processors execute the inspection logic to capture a page image of a print job page printed on a print medium, determine a page identifier on the page image, determine whether the page identifier is within a first production range associated with a first inspection production, and if it is determined that the page identifier is within the first production range, perform an inspection process on the page image using the first inspection production. [Brief description of the drawings]

[0004] A better understanding of the invention may be had from the following detailed description taken in conjunction with the following drawings, in which:

[0005] [Figure 1] FIG. 1 is a block diagram of an embodiment of a printing system.

[0006] [Figure 2A] FIG. 2 is a block diagram illustrating an embodiment of a print controller. [Figure 2B] FIG. 2 is a block diagram illustrating an embodiment of a print controller.

[0007] [Diagram 3] 1 illustrates one embodiment of a test production module.

[0008] [Figure 4A] 1 illustrates an embodiment of a graphical user interface. [Figure 4B] 1 illustrates an embodiment of a graphical user interface.

[0009] [Figure 5A] FIG. 2 is a flow diagram illustrating an embodiment of a process performed by an inspection production module. [Figure 5B] FIG. 2 is a flow diagram illustrating an embodiment of a process performed by an inspection production module.

[0010] [Figure 6] 1 illustrates one embodiment of a print verification system.

[0011] [Figure 7] FIG. 1 is a flow diagram of one embodiment of a process for performing print verification.

[0012] [Figure 8] FIG. 11 is a flow diagram illustrating another embodiment of a process for performing print verification.

[0013] [Figure 9] FIG. 1 is a flow diagram illustrating one embodiment of an inspection process.

[0014] [Figure 10] 1 illustrates an embodiment of a computer system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] A mechanism for automatically controlling inspection production is described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the underlying principles of the present invention.

[0016] In the specification, a reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase "in one embodiment" in various places in the specification do not necessarily all refer to the same embodiment.

[0017] Throughout this document, terms such as "logic," "component," "module," "engine," "model," "computer," etc. may be referred to interchangeably and may include, by way of example, any combination of software and hardware, such as software, hardware, and / or firmware. Additionally, any use of a particular brand, word, term, phrase, name, and / or acronym should not be read as limiting embodiments to a product or software or device that carries that label in literature outside of this document.

[0018] 1 is a block diagram illustrating one embodiment of a printing system 130. A host system 110 is in communication with the printing system 130 to print a sheet image 120 onto a print medium 180 (e.g., paper) via a printer 160. The resulting print medium 180 may be printed in color and / or in any of a number of grayscales, including black and white (e.g., cyan, magenta, yellow, and black, (CMYK)). The host system 110 may include any computing device, such as a personal computer, a server, a cloud infrastructure, or even a digital imaging device, such as, for example, a digital camera or scanner.

[0019] Sheet image 120 may be any file or data that describes how an image should be printed on a sheet of print media 180. For example, sheet image 120 may include PostScript data, Printer Command Language (PCL) data, and / or any other printer language data. Print controller 140 processes the sheet image to generate bitmap 150 for printing on print media 180 via printer 160.

[0020] The printing system 130 may be a high-speed printer operable to print relatively high volumes (e.g., greater than 100 pages per minute). The print medium 180 may be continuous paper, cut paper, and / or any other tangible medium suitable for printing. In one generalized form, the printing system 130 includes a printer 160 having one or more print engines 165 that presents a bitmap 150 on the print medium 180 via a marking material (e.g., toner, ink, coating, etc.) based on the sheet image 120.

[0021] The print controller 140 and the printer 160 may both be implemented within the same printing system 130 or may be implemented separately and connected to one another. In another embodiment, the print controller 140 may be implemented within the host system 110 and connected to the printer 160. The print controller 140 may be any system, device, software, circuitry, and / or other suitable component operable to transform the sheet images 120 to generate bitmaps 150 for printing onto the print media 180. In this regard, the print controller 140 may include processing and data storage capabilities.

[0022] In one embodiment, a print verification system (PVS) 190 is implemented to capture images of the printing surface of the print medium 180 and determine print quality defects on the print medium 180 (e.g., substrate or print substrate). The print quality defects may be defects due to defective print markings on the substrate (e.g., clogged ink nozzles, ink drops not in the correct position on the substrate, missing ink drops due to incorrect color, incorrect character, incorrect image, barcode quality, and / or incorrect image element size, etc.) and / or physical defects in the substrate (e.g., impurities, specks, smudges, flutter, temporary wrinkles, wrinkles, and / or z-direction defects). In one embodiment, the PVS 190 may report the results of any detected defects to the print controller 140 for further processing. The PVS 190 may be a standalone component or may be integrated into the print system 130.

[0023] 2A and 2B show an embodiment of the print controller 140. As shown in FIG. 2A, the print controller 140 (e.g., DFE or digital front end) in its generalized form includes an interpreter module 212, a halftone processing module 214, and an inspection production module 220. FIG. 2B shows an alternative embodiment having print controllers 140A and 140B. In this embodiment, the print controller 140A includes the interpreter module 212 and the halftone processing module 214, and the print controller 140B includes the inspection production module 220. The print controllers 140A and 140B may be implemented in the same printing system 130 (as shown) or may be implemented separately and connected to each other. Alternatively, the inspection production module 220 may be implemented in the PVS 190 and connected to the printing system 130.

[0024] The interpreter module 212 is operable to interpret, render, rasterize, or otherwise convert an image of a print job (e.g., a raw sheetside image such as sheet image 120) into a sheetside bitmap. The sheetside bitmaps generated by the interpreter module 212 are each a two-dimensional array of pixels (i.e., a Continuous Tone Image (CTI)) that represents an image of the print job, also referred to as a full sheetside bitmap. The two-dimensional pixel array is considered a "full" sheetside bitmap because the bitmap contains a set of pixels of the image. In one embodiment, the interpreter module 212 is operable to interpret or render multiple raw sheetsides simultaneously such that the rendering speed substantially matches the speed of the image processing of the production print engine.

[0025] The halftone processing module 214 is operable to represent the sheetside bitmap as a halftone pattern of inks. For example, the halftone processing module 214 may convert pixels to a halftone pattern of CMYK inks for application to paper. The halftone design may include a predefined mapping of input pixel gray levels to output drop sizes based on pixel location.

[0026] Print production in the printing system 130 is increasingly moving towards hands-off production, including including additional dynamic data within a print job, including variability in form and page size, and including additional capabilities for finishing equipment and workflow solutions to manage such features without stopping the printing process. However, conventional PVS systems have limitations in terms of how they can manage changes to content or form size. Further, for a particular customer's print job output, with conventional PVS systems, it is necessary to manually select inspection production. For example, a system operator needs to manually select a particular production on a conventional PVS that correlates with the print data processed by the print controller 140. These processes are independent, and the operator needs to confirm that the correlation is correct.

[0027] According to one embodiment, an inspection production module 220 is provided to facilitate the selection of one or more inspection productions to be implemented in the PVS 190 during printing. In such an embodiment, the inspection production module 220 receives from the PVS 190 a page identifier (page ID value) identified from the captured print image of the printed page of the print job. The printed page identifier is located on the printed page of the print job and is used to specify the page within the print job on which the selected inspection production is to be implemented for verification of the print job. In a further embodiment, the PVS 190 is configured to determine (e.g., identify and decode) the page identifier included in the print image of the printed page to determine which of a plurality of inspection productions should perform a print verification on the page image. As used herein, an inspection production (or production) includes a set of inspection instructions (e.g., a set of instructions for performing an inspection of a print image) used by the inspection logic of the PVS 190 to determine one or more types of defects within a print job to be inspected and the location within the print image to be inspected.

[0028] 3 illustrates one embodiment of the inspection production module 220. According to one embodiment, the inspection production module 220 receives the detected page identifier, determines whether the page is a production page associated with a first inspection production, where the inspection production is used to perform print verification of the print image of the printed print job data, and upon determining that the page is a production page, sends a production message to the print verification system. The production message includes the name of the inspection production and a page identifier indicating the first page in the range that uses the inspection production.

[0029] 3, the test production module 220 includes a production database 310, a production interface 320, and a graphical user interface (GUI) 350. The production database 310 includes a list of all test productions currently implemented in the PVS 190. In one embodiment, the production database 310 is accessed for selection of one or more test productions. The graphical user interface (GUI) 350 may be implemented within the test production module 220 or may be implemented separately (e.g., implemented within the printing system 130 or the printing controller 140) and connected to each other.

[0030] The production interface 320 includes an application programming interface (API) that facilitates communication with the inspection logic in the PVS 190. According to one embodiment, the production interface 320 is configured to receive update messages from the PVS 190. In such an embodiment, the update message includes an updated list of all inspection productions (e.g., identified by production name) currently implemented in the PVS 190, and may include the scanning resolution at which each production applies. The updated inspection productions are presented as choices that may be selected by an operator, as described further below. Technical advantages resulting from providing a list of inspection productions currently implemented in the PVS 190 include avoiding processing errors due to selecting an unavailable inspection production.

[0031] In a further embodiment, the production database 310 includes a default production for the instance where a specific production is not selected in the production interface 320 .

[0032] In one embodiment, a system operator may use GUI 350 and production interface 320 to search production database 310 to select one or more productions to be associated with the print job to be printed. The productions may be identified by the associated name of the production (e.g., production name). In this embodiment, the operator selection is made by specifying each production as a job property in the print job. For example, other available properties may include edge enhancement options, thin line rendering black, cyan, magenta, yellow, black (CMYK) overprint options, etc. Technical advantages resulting from selecting one or more inspection productions as properties of the print job data include data processing efficiencies by combining inspection production selection with other print job properties.

[0033] In further embodiments, the production interface 320 may automatically select one or more productions to associate with a print job. For example, the production interface 320 may automatically select a production based on characteristics of a printing system that always uses the same production. Such print job characteristics include a hot folder directory used to submit the print job or a selected virtual printer queue. Technical advantages resulting from the automated association of inspection productions with print jobs include increasing system efficiency by eliminating manual intervention.

[0034] In one embodiment, the production interface 320 may be further configured to select a default production upon a determination that no production has been selected. In this embodiment, the default production may include a standard default production or an operator-selected default production to be used. Technical advantages resulting from providing a default test production include ensuring that a default test production is selected even if the operator has not selected a test production.

[0035] Figures 4A and 4B show an embodiment of a GUI 350. As shown in Figure 4A, a production may be selected based on the name of the production (e.g., Example Production (600x600) or default) as a job property of the printer hot folder ICCProfilePrints.

[0036] In a further embodiment, production interface 320 provides a choice (e.g., via user interface 350) for error handling in the event that PVS 190 determines that the print job does not conform to the results of the checks performed according to the production. In this embodiment, the operator may select whether a message (e.g., a warning) is displayed in PVS 190 or whether the print production should proceed when an error is detected. Figure 4B discloses a choice for error handling in GUI 350 (e.g., "User Production Error" set to "Warning").

[0037] According to one embodiment, the production interface 320 associates a production transition (e.g., from a first production to a second production) based on a page identifier (page ID value) associated with each page of the print job data. As described below, the print controller 140 applies page ID data to each page of the print job data during job interpretation (e.g., in the interpreter module 212) and identifies (e.g., using an associated property) the page ID value at which the production transition (production page ID) occurs. In this embodiment, the production interface 320 is configured to send a production message to the PVS 190 that identifies the production page ID as the page ID value associated with the first page in the page range to which the production is to be applied. For example, the production interface 320 may send a first production message indicating a production page ID (e.g., page #1) as the first page to which the first production (or production N) is to be applied for testing in the PVS 190. Subsequent pages (e.g., pages #2 through #100) also apply the first production until a second production message is sent indicating that the subsequent production page ID (e.g., page #101) is the first page to which the second production (or production N+1) is to be applied. The printed page ID value may be printed as human readable characters or may be encoded, such as with a bar code. Technical advantages of encoding the page ID value using a printed bar code include the ease and reliability of a standardized symbology of printing, scanning, and decoding.

[0038] In a further embodiment, the production message also includes a production name (e.g., a default or specific production name) and a page ID value. In a further embodiment, the production message includes a Job Messaging Format (JMF). JMF messages are part of the Job Definition Format (JDF) specification. Like JDF, JMF is an Extensible Markup Language (XML)-based file formatting language used for communication between JDF agents and controllers in a JDF-enabled workflow.

[0039] According to one embodiment, the page ID data included in the expanded configuration of the side 2 verification code (e.g., a code used to verify that the front and back of the pages of a sheet being inspected in PVS 190 match correctly) may be expanded to include a page ID barcode. In one embodiment, each page is inspected for a unique ID number that indicates whether a particular action should occur. Thus, the production interface 320 inspects the side 2 verification code for each received page to determine whether the included page ID value is associated with a production change.

[0040] FIG. 5A is a flow diagram illustrating one embodiment of a process 500 for processing inspection production, which may be performed by inspection production module 220. Process 500 may be performed by processing logic, which may include hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (e.g., instructions running on a processing device), or a combination thereof. While process 500 is shown in a linear sequence for brevity and clarity of presentation, it is contemplated that any number of may be performed in parallel, asynchronously, or in a different order. For brevity, clarity, and ease of understanding, many of the details discussed with reference to FIGS. 1-4 will not be discussed or repeated here. Process 500 begins at processing block 510, where an updated production list is received (e.g., from PVS 190 or inspection production module 220). At processing block 520, print job data is received at some point after receipt of the production list. At process block 530, data is received (e.g., from PVS 190 or inspection production module 220) indicating one or more selected productions (e.g., one or more selected production names) to be associated with the print job. As discussed above, an operator may inspect the print job via GUI 350 and select a production for the print job as one of various available print job properties. At process block 540, the print job page (e.g., production page ID) and associated production at which a production transition occurs are identified. Process 500 is then complete. Technical advantages resulting from associating inspection productions with page ID values ​​include the ability to change inspection productions at the page level without manual intervention to improve system efficiency.

[0041] 5B is a flow diagram illustrating one embodiment of a process 550 for inserting a page ID value into print job data, which may be performed by the inspection production module 220. The process 550 may be performed by processing logic, which may include hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (e.g., instructions running on a processing device), or a combination thereof. Although the process 550 is shown in a linear sequence for brevity and clarity of presentation, it is contemplated that any number of them may be performed in parallel, asynchronously, or in a different order. For brevity, clarity, and ease of understanding, many of the details discussed with reference to FIGS. 1-4 will not be discussed or repeated here.

[0042] At process block 560, a page in the print job data is received or determined. At process block 565, the page ID value is applied to the corresponding page (e.g., the page ID value is inserted into the print job for printing on the corresponding print job page). At decision block 570, a determination is made as to whether the page ID value is associated with a production transition. If not, control is returned to process block 565 where another page is received or determined. Otherwise, a production message is sent to PVS 190 (processing block 575) that includes the page ID value as the production page ID and the name of the production to be used. At decision block 580, a determination is made as to whether there are additional pages to process. If so, control is returned to process block 565 where another page is received. Otherwise, process 550 is complete.

[0043] As discussed above, print media having printed data is received at PVS 190, which performs print image capture and defect detection. Figure 6 illustrates one embodiment of PVS 190, including image capture device 610, registration engine 620, controller interface 630, inspection logic 640, and production database 650. In one embodiment, image capture device 610 includes one or more cameras. However, in other embodiments, image capture device 610 may include different types of image capture devices. Image capture device 610 includes one or more available optical resolution settings (e.g., scanning resolution) selectable and identifiable to PVS 190.

[0044] The image capture device 610 may provide measurements of the image (e.g., reflectance, intensity, etc.) for each of one or more color bands. In such an embodiment, the image capture device 610 captures (or scans) an image of the print media after the bitmap print data (or bitmap data) is applied to the print media using a marking material. The image capture device 610 may transmit the resulting print media image data corresponding to one or more color bands (e.g., red, green, blue, grayscale, etc.).

[0045] The registration engine 620 receives the obtained print media image data (e.g., print image, print image data) and performs registration between the print media image data and the bitmap print image data (e.g., bitmap image). According to one embodiment, the registration process may be implemented by performing color transformation, rotation, skew transformation, translation, and / or scaling operations on the print media image and / or the bitmap image to obtain a matching data scheme between the print media image, the bitmap image, and / or the inspection logic 640.

[0046] Controller interface 630 includes an API configured to interface with production interface 320. In one embodiment, controller interface 630 detects modifications to production database 650 (e.g., the creation or deletion of a production) and sends an updated production list to production interface 320. In a further embodiment, production interface 320 ensures that the updated production list excludes productions currently available in production database 650 that do not match the available scanning resolution of PVS 190.

[0047] During print job processing, controller interface 630 receives a production message from production interface 320. In response, controller interface 630 begins acquisition by loading the correct default production, then converts the default production to the production indicated in the production message (e.g., the current production is changed from the default production to the production indicated in the production message), generates a page ID command, and sends the page ID command to validation logic 640. In an embodiment, the page ID command includes the name of the production being implemented and the associated page ID value, and is formatted to meet the processing requirements of PVS 190, and more specifically, validation logic 640.

[0048] 7 is a flow diagram illustrating one embodiment of a process 700 performed by PVS 190 (e.g., controller interface 630). Process 700 may be performed by processing logic, which may include hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (e.g., instructions running on a processing device), or a combination thereof. Process 700 is shown in a linear sequence for brevity and clarity of presentation, but it is contemplated that any number of may be performed in parallel, asynchronously, or in a different order. For brevity, clarity, and ease of understanding, many of the details discussed with reference to FIGS. 1-6 will not be discussed or repeated here.

[0049] At processing block 710, a production message is received. At processing block 720, the correct default production is loaded. At processing block 730, the default production is converted to the production indicated in the production message. At processing block 740, a page ID command is sent (e.g., to validation logic 640) that includes the production page ID and associated production name.

[0050] 6, the check logic 640 receives a page ID command and loads the command into the queue 242 of upcoming productions and page ID values ​​to switch to, as well as acquiring memory resources associated with the page ID command (e.g., the productions associated with the page ID value) to execute the upcoming quantity (N) of productions. The check logic 640 may perform checks on the N productions once the resources are acquired. In one embodiment, the check logic 640 performs the check process by receiving scanned images of printed pages (or page images, printed images) and determining the page ID value contained in each page image.

[0051] The check logic 640 then determines whether the page image's page ID value is within the production page ID range for the production currently being used. In one embodiment, the check logic 640 determines that the page ID value is within the current production range if it determines that the page ID value is less than the production page ID for the next production (e.g., N+1).

[0052] If the inspection logic 640 determines that the page ID value is within the current production page ID, it continues to process the page image using the current production N. However, production N+1 is loaded and used to process the page image. Thus, the inspection logic 640 processes the page using the same production until it detects, based on the page ID value, that a different production should be used for processing. For example, when the inspection logic 640 receives page #1 as the production page ID, it processes pages #1 through #100 using a first production. When the inspection logic 640 then receives page #101 as the subsequent production page ID, it processes page #101 using a second production. In one embodiment, the inspection logic 640 processes the page image by detecting defects and comparing the page image using a production to a reference page image to detect defects and determine whether the detected defects are within an acceptable print quality margin.

[0053] 8 is a flow diagram illustrating one embodiment of a process 800 for performing print verification, which may be performed by PVS 190 (e.g., inspection logic 640). Process 800 may be performed by processing logic, which may include hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (e.g., instructions running on a processing device), or a combination thereof. While process 800 is shown in a linear sequence for brevity and clarity of presentation, it is contemplated that any number of may be performed in parallel, asynchronously, or in a different order. For brevity, clarity, and ease of understanding, many of the details discussed with reference to FIGS. 1-7 will not be discussed or repeated here.

[0054] At processing block 810, a Page ID command is received. At processing block 820, the Page ID command is loaded into a queue of upcoming productions and Page ID value switches. At processing block 830, production resources are obtained (e.g., retrieved from memory) to execute the upcoming N productions. At processing block 840, a test is performed using the N productions.

[0055] FIG. 9 is a flow diagram illustrating one embodiment of a process 900 for performing an inspection on a page image, which may be performed by PVS 190 (e.g., inspection logic 640). Process 900 may be performed by processing logic, which may include hardware (e.g., circuitry, dedicated logic, programmable logic, etc.), software (e.g., instructions running on a processing device), or a combination thereof. While process 900 is shown in a linear sequence for brevity and clarity of presentation, it is contemplated that any number of may be performed in parallel, asynchronously, or in a different order. For brevity, clarity, and ease of understanding, many of the details discussed with reference to FIGS. 1-9 will not be discussed or repeated.

[0056] At processing block 910, a page image is received. At processing block 920, a page ID value in the page image is determined. At decision block 930, a determination is made whether the page ID value is within the production page ID range of the currently being used production N (e.g., page ID value<production page ID(N+1)). If production N is determined to be within the production page ID range, production N is used to perform the inspection process on the page image (processing block 940). Otherwise, if the page ID value is determined to not be within the production page ID range, production N+1 is used to perform the inspection process on the page image.

[0057] Technical advantages resulting from determining the page ID value from the page image include effectively providing a page ID image within the printed image without having to consider a time delay between determining the page ID value and when the printed page arrives at the PVS 190 for processing. The time delay may vary due to changes in print job queuing, paper path configuration of the printing system 130, and / or print speed of the print engine 165. FIG. 10 illustrates a computer system 1300 on which the host system 110, the printing system 130, the print controller 140, and / or the PVS 190 may be implemented. The computer system 1300 includes a system bus 1320 for communicating information and a processor 1310 coupled to the bus 1320 for processing information.

[0058] Computer system 1300 further includes a random access memory (RAM) or other dynamic storage device 1327 (herein referred to as main memory), coupled to bus 1320 for storing information and instructions executed by processor 1310. Main memory 1325 may also be used for storing temporary variables or other intermediate information during execution of instructions by processor 1310. Computer system 1300 may also include a read only memory (ROM) and / or other static storage device 1326, coupled to bus 1320, for storing static information and instructions used by processor 1310.

[0059] A data storage device 1327, such as a magnetic or optical disk and its corresponding drive, may also be connected to the computer system 1300 for storing information and instructions. The computer system 1300 may also be connected to a second I / O bus 1350 via an I / O interface 1330. A number of I / O devices, including a display device 1324, input devices (e.g., a keyboard 1323 (e.g., an alphanumeric input device) and / or a cursor control device 1322) may also be connected to the I / O bus 1350. The communication device 1321 is for accessing other computers (servers or clients). The communication device 1321 may include a modem, a network interface card, or other well-known interface devices such as those used to connect to an Ethernet, Token Ring, or other type of network.

[0060] An embodiment of the present invention may include various steps as described above. The steps may be embodied in machine-executable instructions. The instructions may be used to cause a general-purpose or special-purpose processor to perform certain steps. Alternatively, the steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.

[0061] The elements of the present invention may also be provided as a machine-readable medium for storing machine-executable instructions. Machine-readable media include, but are not limited to, floppy disks, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, propagation media, or other types of media / machine-readable media suitable for storing electronic instructions. For example, the present invention may be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) as a computer program that may be transferred by a data signal embodied in a carrier wave or other propagation medium via a communications link (e.g., a modem or network connection).

[0062] The following sections and / or examples relate to further embodiments or examples. Details in the examples may be used anywhere in one or more embodiments. Various features of the various embodiments or examples may be combined in various ways with some features included and other features excluded to suit a variety of different applications. Examples may include subject matter such as a method, a means for performing the actions of the method, at least one machine-readable medium including instructions that, when executed by a machine, cause the machine to perform the actions of the method, a device, or a system, according to the embodiments and examples described herein.

[0063] In some embodiments related to Example 1, Example 1 includes at least one physical memory device that stores inspection logic; and one or more processors coupled to the at least one physical memory device, where the one or more processors execute the inspection logic to capture a page image of a print job page printed on a print medium, determine a page identifier for the page image, determine whether the page identifier is within a first production range associated with a first inspection production, and if it is determined that the page identifier is within the first production range, perform an inspection process using the first inspection production on the page image.

[0064] Example 2 includes the subject matter of example 1, where the inspection logic further performs an inspection process using a second inspection production on the page image if the page identifier is not within the first production range.

[0065] Example 3 includes the subject matter of examples 1 and 2, and wherein the at least one physical memory device further stores interface logic, and the one or more processors execute the interface logic to receive a production message including a name of the test production and a page identifier indicating a first page in a range using the test production.

[0066] Example 4 includes the subject matter of examples 1-3, and further includes the interface logic sending a page ID command to the inspection logic, the page ID command including the page identifier and the name of the inspection production.

[0067] Example 5 includes the subject matter of examples 1-4, wherein the inspection logic is further configured to receive a page ID command and add the page ID command to a queue of inspection productions.

[0068] Example 6 includes the subject matter of examples 1-5, and wherein the test logic further obtains memory resources associated with the page ID command for executing the test production, the memory resources including the test production.

[0069] Example 7 includes the subject matter of Examples 1-6, wherein the at least one physical memory device further stores insertion logic, and the one or more processors execute the insertion logic to receive a page of print job data, insert a page identifier into the print job data that applies to the page, and send a production message to the inspection logic.

[0070] Example 8 includes the subject matter of examples 1-7, wherein the insertion logic is further configured to receive an update message from the inspection logic that includes a list of inspection productions currently implemented in the print verification system.

[0071] Example 9 includes the subject matter of examples 1-8, wherein the insertion logic is further configured to receive data indicating a selection of one or more test productions to be associated with the print job data.

[0072] Example 10 includes the subject matter of examples 1-9, wherein the one or more inspection productions are selected as properties of the print job data.

[0073] Example 11 includes the subject matter of Examples 1-10, wherein the at least one physical memory device further stores a graphical user interface (GUI), and the one or more processors execute the GUI to receive a selection of the one or more test productions.

[0074] Example 12 includes the subject matter of Examples 1-11, and further includes a printer for printing the print job on a print medium.

[0075] Some embodiments are related to Example 13, which includes a method including capturing a page image of a print job page printed on a print medium, determining a page identifier on the page image, determining whether the page identifier is within a first production range associated with a first inspection production, and performing an inspection process using the first inspection production on the page image upon determining that the page identifier is within the first production range.

[0076] Example 14 includes the subject matter of example 13, and further includes performing an inspection process using a second inspection production on the page image upon determining that the page identifier is not within the first production range.

[0077] Example 15 includes the subject matter of examples 13 and 14, and further includes receiving a production message including a name of the test production and a page identifier indicating a first page in a range that uses the test production.

[0078] Example 16 includes the subject matter of Examples 13-15, and further includes sending a page ID command, where the page ID command includes a page identifier and a name of the test production.

[0079] Some embodiments are related to Example 17, which includes at least one computer-readable medium having instructions stored thereon that, when executed by one or more processors, cause the processors to capture a page image of a print job page printed on a print medium, determine a page identifier on the page image, determine whether the page identifier is within a first production range associated with a first inspection production, and, upon determining that the page identifier is within the first production range, perform an inspection process using the first inspection production on the page image.

[0080] Example 18 includes the subject matter of Example 17, and further includes instructions that, when executed by one or more processors, cause the processors to perform an inspection process using a second inspection production on the page image when it is determined that the page identifier is not within the first production range.

[0081] Example 19 includes the subject matter of Examples 17 and 18, and includes instructions that, when executed by one or more processors, cause the processors to receive a production message including a name of the test production and a page identifier indicating the first page of a range in which the test production is used.

[0082] Example 20 includes the subject matter of Examples 17-19, and further includes storing instructions that, when executed by one or more processors, cause the processors to send a page ID command to the inspection logic, the page ID command including a page identifier and a name of the inspection production.

[0083] Although many variations and modifications of the present invention will no doubt become apparent to those skilled in the art after reading the foregoing description, it should be understood that any particular embodiments shown and described by way of illustration are not intended to be regarded as limiting in any way. Accordingly, reference to details of various embodiments is not intended to limit the scope of the claims, which in themselves define only those features regarded as essential.

Claims

1. 1. A system comprising: at least one physical memory device for storing test logic; and one or more processors coupled to the at least one physical memory device, the one or more processors executing the checking logic to: capturing page images of the print job pages printed on a print medium; determining a page identifier on the page image; determining whether the page identifier is within a first production range associated with a first test production; and upon determining that the page identifier is within the first production range, performing an inspection process on the page image using a first inspection production.

2. 2. The system of claim 1, wherein the inspection logic is further configured to perform an inspection process on the page image using a second inspection production if the page identifier is determined to be not within the first production range.

3. 3. The system of claim 2, wherein the at least one physical memory device further stores interface logic, and the one or more processors execute the interface logic to receive a production message including a name of a test production and a page identifier indicating a first page in a range that uses the test production.

4. The system of claim 3 , wherein the interface logic is further configured to send a page ID command to the inspection logic, the page ID command including the page identifier and a name of the inspection production.

5. The checking logic further comprises: receiving the page ID command; and adding the page ID command to a queue of inspection production.

6. 6. The system of claim 5, wherein the test logic is further operable to obtain memory resources associated with the page ID command for executing the test production, the memory resources including the test production.

7. The at least one physical memory device further stores injection logic, and the one or more processors execute the injection logic to: receiving a page of print job data; inserting the page identifier into print job data that applies to the page; and sending a production message to the inspection logic.

8. 8. The system of claim 7, wherein the insertion logic is further operable to receive an update message from the inspection logic that includes a list of inspection productions currently implemented in the print verification system.

9. 10. The system of claim 8, wherein the insertion logic is further adapted to receive data indicating a selection of one or more test productions to be associated with the print job data.

10. The system of claim 9 , wherein the one or more inspection productions are selected as properties of the print job data.

11. 10. The system of claim 9, wherein the at least one physical memory device further stores a graphical user interface (GUI), and the one or more processors execute the GUI to receive a selection of the one or more test productions.

12. The system of claim 1 , further comprising a printer for printing the print job pages on the print medium.

13. 1. A method comprising: capturing page images of the print job pages printed on a print medium; determining a page identifier on the page image; determining whether the page identifier is within a first production range associated with a first test production; and upon determining that the page identifier is within the first production range, performing an inspection process on the page image using a first inspection production.

14. The method of claim 13 , further comprising, upon determining that the page identifier is not within the first production range, performing an inspection process on the page image using a second inspection production.

15. 15. The method of claim 14, further comprising receiving a production message including a name of the test production and a page identifier indicating the first page of a range in which the test production is used.

16. 16. The method of claim 15, further comprising sending a page ID command, the page ID command including the page identifier and a name of the test production.

17. At least one computer-readable medium having instructions stored thereon, the instructions, when executed by one or more processors, causing the processors to: capturing page images of the print job pages printed on a print medium; determining a page identifier on the page image; determining whether the page identifier is within a first production range associated with a first test production; and upon determining that the page identifier is within the first production range, performing an inspection process on the page image using a first inspection production.

18. 20. The computer-readable medium of claim 17, having instructions stored thereon that, when executed by one or more processors, cause the processors to perform an inspection process on the page image using a second inspection production upon determining that the page identifier is not within the first production range.

19. 20. The computer-readable medium of claim 18 having stored thereon instructions that, when executed by one or more processors, cause the processors to receive a production message including a name of a test production and a page identifier indicating a first page of a range that uses the test production.

20. 20. The computer-readable medium of claim 19, wherein instructions are stored that, when executed by one or more processors, cause the processors to send a page ID command to inspection logic, the page ID command including the page identifier and a name of the inspection production.

Images