Print Controller Purge via Flush Messages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for purging print data paths in production printing systems are inefficient, especially when dealing with large amounts of data, as they can cause significant delays and require continuous connection between the host system and print controller.
Innovation Solution
Implementing flush job and flush path messages within the print controller to initiate and manage data purging, allowing components to purge specific or all print jobs independently, without relying on the host system, thus enabling efficient data clearance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the print data path is purged by stopping new data input and letting the printing process empty out old data, then the print data path is cleared, but the print engine may run for several minutes causing significant delays
Solution Approach 1:
The system sends flush messages to components in advance of actual data purging, preparing them to clear their buffers and queues when the purge is initiated. This preliminary preparation allows for faster, more coordinated data removal rather than passive waiting for the printing process to naturally empty data.
Solution Approach 2:
The invention extracts the purging function from the passive printing process and makes it an active, controllable operation. By sending flush messages to specific components (interpreter, bitmap generator, buffer manager), the system selectively removes data from the print data path without requiring the entire printing process to run to completion.
2Productivity
If the print data path is kept full to maintain rated-speed printing, then productivity is maintained, but purging becomes more complex and time-consuming when data must be removed
Solution Approach 1:
The system divides the print data path into separate manageable components (host interface, interpreter, bitmap generator, buffer manager, print engine) and sends targeted flush messages to each. This segmentation allows the purge operation to be controlled independently at each stage, making the complex purging process more manageable while maintaining overall system productivity.
3Reliability
If the host system remains continuously connected to the print controller during purging, then coordination is maintained, but system resources are consumed and connection stability is reduced
Solution Approach 1:
The print controller autonomously manages the purging operation by sending flush messages to its own internal components without requiring continuous host system involvement. The controller can initiate and complete the purge process independently, reducing the need for persistent host-controller connections and associated resource consumption.
Data Source
AI summary
A print controller and associated methods of purging a print data path are disclosed. A print controller comprises a job storage system that receives and stores print jobs, and a print data path, which includes components operable to process print jobs, from the job storage system to print engines. The control system receives registrations from the components for flush job messages, flush path messages, or both. The control system receives a request to purge the print data path, and identifies print jobs being processed in the print data path. The control system transmits flush job messages to the components registering for the flush job messages for each print job instructing the components to purge data for the print jobs. The control system also transmits a flush path message to the components registering for the flush path messages instructing the components to purge data for the print jobs being handled.