Composite Reusable Document Component Caching for Print Throughput
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face inefficiencies in rendering and caching composite reusable document components (RDCs) and reusable underlays (RULs, leading to time-consuming merging of multiple components, which lowers page per minute throughput in personalized print jobs.
Innovation Solution
A method that creates composite RDCs and RULs by caching and rendering individual RDCs within bounding boxes, combining them to form composite RULs, and using cached underlays and overlays for faster page rendering, with components outside the page boundary clipped.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple RDCs are retrieved from cache and merged to construct page output, then reusable components can be utilized, but the merging process is time consuming and lowers page per minute throughput
Solution Approach 1:
The patent combines multiple RDCs into a single composite RDC that is rendered once and cached. This composite RDC replaces the need to retrieve and merge multiple individual RDCs from the cache during page construction, thereby maintaining reusable component utilization while significantly reducing the time required for merging operations and increasing page per minute throughput.
Solution Approach 2:
The patent performs preliminary rendering and caching of composite RDCs before they are needed for page output. By pre-composing and caching the composite RDC in advance, the system eliminates the time-consuming merging step during actual page construction, thus resolving the contradiction between reusable component utilization and page per minute throughput.
2Adaptability or versatility
If individual RDCs are rendered and cached separately, then reusability is maintained, but multiple retrieval and merging operations are required for pages with multiple RDCs
Solution Approach 1:
The patent merges multiple individual RDCs into a single composite RDC structure. This composite RDC is rendered once and cached, eliminating the need for multiple separate retrieval and merging operations when constructing pages with multiple RDCs. This approach maintains RDC reusability while significantly reducing the time lost to multiple merging operations.
Solution Approach 2:
The composite RDC serves multiple functions simultaneously: it acts as a reusable component that can be applied to multiple pages, and it pre-composes multiple individual RDCs into a single unit that eliminates the need for repeated merging operations. This multi-functionality resolves the contradiction between maintaining reusability and reducing time loss.
Data Source
AI summary
A method for creating reusable composite components from interpreted pages of rendered document during dynamic document construction involves first obtaining a list of document components from the page and identifying any non-cached components. The individual reusable document components (RDCs) are cached having been rendered to their respective bounding box dimensions. These RDCs are then permuted into combinations of RDCs and each composite RDC is cached rendered relative to each other in a bounding box of sufficient size to adequately contain the combination. Then, combining RDCs to form composite reusable underlays RULs and caching the composite RULs rendered to full-page size. Any portion of each RDC of each composite RUL falling outside the boundary of RULs full-page size is clipped. If a method renders pages having a combination of reusable components and non-cached components, the first step assesses the page for the possibility of having an underlay-overlay pair. Then a cache of RULs is searched for underlays having the needed RDCs. If the correct RUL is not found in cache then generating a RUL from the page's RDCs and caching the new RUL rendered to full-page size. A full-page size overlay is rendered having the non-cached components. Lastly, given the overlay and given the correct underlay is found in cache then retrieving the underlay and rendering the page therefrom.