Patent 12118290
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Active provider: Google · gemini-2.5-pro
Obviousness
Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.
Analysis of Obviousness of U.S. Patent 12,118,290 under 35 U.S.C. § 103
This analysis examines the claims of U.S. Patent 12,118,290 ('290 patent) for obviousness in light of prior art available before the patent's priority date of July 6, 2020. A claim is considered obvious under 35 U.S.C. § 103 if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious to a person having ordinary skill in the art (PHOSITA).
This analysis concludes that the independent claims of the '290 patent would have been obvious over a combination of prior art references, primarily U.S. Patent Application Publication No. 2015/0378904 A1 (Leto) in view of U.S. Patent Application Publication No. 2018/0114251 A1 (Ramer).
Interpretation of Key Claim Terms
For this analysis, the claim terms are given their plain and ordinary meaning as understood by a PHOSITA in the field of content management and document generation systems.
- "Modular item" / "Content item": A discrete, reusable portion of content, such as a page, paragraph, image, or data chart, that can be managed independently and assembled into various documents.
- "First/Given Document": A source or master document that contains at least one modular item and its associated assembly rules, serving as a template for personalization.
- "Derivative Document": The new, personalized document created by the assembly process.
- "Style": The visual presentation and branding characteristics of a document, including fonts, color schemes, logos, and layout templates.
Summary of Prior Art
Leto (US 2015/0378904 A1): Leto teaches a "Dynamic Document Generation" system. This system assembles documents by selecting "content components" from a library. The selection is driven by a "document definition" which contains logic and rules. Based on data provided by a user (e.g., customer details), the system follows these rules to pull the appropriate components and assemble them into a finished document.
Ramer (US 2018/0114251 A1): Ramer describes a "Content Customization Platform" focused on personalizing marketing materials. The platform uses "content modules" that are associated with personalization rules based on user data. A key teaching of Ramer is the application of consistent branding and style templates to the dynamically assembled content to ensure a uniform look and feel.
Obviousness Argument
Grounds for Obviousness: Leto in view of Ramer
A combination of the teachings from Leto and Ramer would render the independent claims of the '290 patent obvious. Leto provides the foundational architecture for rule-based, modular document assembly, while Ramer provides the missing element of applying a consistent brand style to the assembled output.
Analysis of Independent Claim 1
Independent Claim 1 outlines a server-based system for automatic document assembly. Leto alone substantially teaches every element of this claim.
- Claim Limitations vs. Leto's Disclosures:
- (a-b) Server-based system: Leto describes a server architecture for its document generation system, which is a standard implementation for such technology.
- (c) Embed rules into a modular item of a first document: Leto's "document definition" contains the rules and logic associated with "content components" (modular items). A PHOSITA would find it an obvious design choice to either store these rules within the item itself or link them in a definition file.
- (d) Receive personalization parameters: Leto explicitly discloses receiving user-provided data to customize the document.
- (e) Pull a second modular item from a second document based on parameters and rules: Leto's system pulls "content components" from a content library (which constitutes one or more source documents) based on its rules and the user's data.
- (f) Assemble to generate a derivative document: This is the primary function of Leto's system—assembling the selected components into a final document.
Given that Leto teaches the core invention of Claim 1, this claim is at minimum obvious, if not anticipated, by Leto.
Analysis of Independent Claim 2
Independent Claim 2 describes a two-component system for creating and personalizing documents, with a specific requirement for rendering the final document in an associated style.
- Claim Limitations vs. Leto and Ramer:
- (a-g) A system to create, rule-associate, and assemble modular items from multiple documents based on personalization instructions: Leto fully discloses these steps. Its system allows for the definition of "content components" (modular items) with associated rules. An assembly engine then acts on user input (a "personalization instruction") to pull these components from a library (the "given document and at least another document") and assemble a new document.
- (h) Render the derivative document using a style associated with the given document: This limitation is not explicitly taught by Leto, which focuses on the logical assembly of content rather than its final presentation. However, this is precisely the problem solved by Ramer. Ramer teaches a system where dynamically assembled content modules are rendered using consistent branding and style templates.
Motivation to Combine
A person of ordinary skill in the art seeking to implement Leto's dynamic document generation system for a commercial or enterprise application would have been strongly motivated to incorporate the styling and rendering teachings of Ramer.
Solving a Known Problem: A system that assembles unformatted blocks of content is incomplete for most business needs. The generated documents (proposals, reports, marketing materials) must adhere to corporate branding guidelines. Ramer teaches a known solution to this exact problem: applying a style layer to modular content.
Predictable Result: Combining a content assembly engine (Leto) with a content styling engine (Ramer) would be a straightforward integration for a PHOSITA. The result—a system that can assemble the correct information and present it in a brand-compliant format—is not a surprising or unexpected outcome. It is the predictable result of uniting two established technologies to create a more complete and commercially viable product.
Therefore, it would have been obvious to a PHOSITA at the time of the invention to enhance Leto's document assembly system with Ramer's method of applying brand styles, thereby arriving at the complete invention described in Claim 2.
Generated 5/13/2026, 12:17:54 AM