PatentNext Takeaway: Ceiva Opco, LLC v. Amazon.com, Inc. illustrates how a concrete technological improvement can support patent eligibility. The Federal Circuit found that a digital picture frame system with a physically separable user interface provided such an improvement by enabling remote access that overcame the limitations of earlier frames. The practical lesson is to explain the technological advance in the specification and claim the features that produce it, rather than merely the desired result.
****
The Federal Circuit’s July 23, 2026 decision in Ceiva Opco, LLC v. Amazon.com, Inc., No. 2024-1721, provides a useful example of how concrete claim language can establish eligibility under 35 U.S.C. § 101. Reviewing summary judgment from the Central District of California, the court reversed the ineligibility ruling for claim 19 of the ’573 patent, affirmed the ruling for representative claims of three related patents, and remanded. Although nonprecedential, the opinion offers practical guidance for drafting and defending software and connected-device claims. Slip op. at 2, 17.
Link to Background and the Digital Picture Frame Problem Background and the Digital Picture Frame Problem
The disclosed system moved user interaction to a remotely accessible interface connected to a data repository. The frame could obtain images and software over a network, reducing the need for direct user intervention. The specification described self-configuration and self-maintenance, including obtaining new images and updating onboard software without user input. These passages explained how the disclosed arrangement changed the frame’s operation, beyond merely making picture sharing more convenient. Slip op. at 4.
Link to Claim 19 Captured the Arrangement That Produced the Improvement Claim 19 Captured the Arrangement That Produced the Improvement
Claim 19 did not stop at requiring remote image sharing. It recited a system with the following cooperating features, among other limitations:
- A digital picture frame containing memory and operating-system software that operates according to user-defined preferences, with a border resembling a printed-photograph frame.
- A user interface connected to a server over a network and “physically separable” from the frame, which obtains images and preferences from the user and provides them to the server.
- A server connected to the frame over the network that periodically relays the images and preferences when the frame automatically requests image data.
- A frame configured to obtain an operating-system update from the server.
These limitations matter in combination. They identify the device, the location and role of the user interface, and the interactions through which the system supplies content and settings to the frame. See slip op. at 5, 11.
Link to Alice Step One and the Concrete Technological Improvement Alice Step One and the Concrete Technological Improvement
Under Alice, the court first asks whether a claim is directed to an ineligible concept, such as an abstract idea. If so, it considers whether the claim contains an inventive concept sufficient to transform that concept into eligible subject matter. Claim 19 passed at the first step: the Federal Circuit found it was not directed to an abstract idea and expressly declined to reach step two. Slip op. at 9, 13.
Reading the claim as a whole in light of the specification, the court found a technical solution to a technological problem. The physically separable interface, together with the other limitations, governed when and how the frame received and displayed images and received settings updates. The claim therefore captured remote access through a sufficiently concrete implementation. The specification reinforced that reading by explaining how the arrangement overcame the earlier frames’ proximity limitations. Slip op. at 10–12.
The district court had characterized the interface as generic and configured only to achieve a result. But its quotation of the claim omitted the requirement that the interface be physically separable from the frame. The Federal Circuit identified that omission as critical: the resulting characterization disregarded the claimed advance and described the claim at an impermissibly high level of generality. Slip op. at 12–13.
This is not a rule that adding a remote interface automatically establishes eligibility. The court relied on the claimed combination and its relationship to the identified technical problem. Nor did it decide novelty, nonobviousness, or compliance with § 112; eligibility was the issue before it. Slip op. at 10–13 & n.3.
Link to How Ceiva Aligns With the Federal Circuit’s Three-Step Improvement Formula How Ceiva Aligns With the Federal Circuit’s Three-Step Improvement Formula
The Federal Circuit’s three-step improvement formula, drawn from its decisions and summarized in How to Patent Software Inventions: Show an “Improvement”, provides a useful framework for drafting software-related patent applications. Ceiva illustrates each step in practice. The formula synthesizes the court’s improvement analysis; it is not a separate legal test that replaces Alice.
Link to 1. Explain the technical improvement in the specification 1. Explain the technical improvement in the specification
The common specification explained a networked arrangement in which the frame obtained images and software from a repository while users interacted remotely. Its discussion of self-configuration and maintenance supplied technical context for the claimed system. The lesson is to describe the operations and component relationships that produce the advance, so that an improvement is apparent from the disclosure. See slip op. at 4, 11–12.
Link to 2. Show how the solution addresses shortcomings of existing technology 2. Show how the solution addresses shortcomings of existing technology
The specification identified concrete limitations of earlier frames: physical insertion of media, local manipulation of controls, and inability to update remotely. It then explained how the disclosed arrangement overcame those limitations. That comparison helped the court identify an improvement in digital picture frame technology. It was not a substitute for a separate novelty or obviousness analysis. See slip op. at 3–4, 10–12.
Link to 3. Put the features producing the improvement into the claims 3. Put the features producing the improvement into the claims
Claim 19 supplied the decisive connection between disclosure and scope. It required the physically separable interface and specified the roles of the server and frame in exchanging images and preferences. Those limitations captured the implementation underlying the asserted improvement. An aspirational statement that a system improves remote access would not perform the same work. See slip op. at 5, 11–13.
Link to Why the Related Claims Failed Why the Related Claims Failed
The court also rejected the step-two argument that industry praise for the commercial Ceiva Frame established an inventive concept or a factual dispute. It explained that secondary considerations of nonobviousness do not establish eligibility and, even assuming the evidence could matter, Ceiva had not sufficiently tied the praise to particular claim elements or their ordered combination. Slip op. at 16–17.
The opinion nevertheless cautioned against treating “configured to” as a forbidden phrase. Such language does not automatically make a claim abstract; eligibility requires consideration of the whole claim in light of the specification. The deficiency was insufficiently claimed implementation, not a drafting phrase considered in isolation. Slip op. at 15 n.5.
Link to Practitioner Tips Practitioner Tips
Preserve the technical relationships in the claim. Identify which arrangement, interaction, or process makes the invention work differently, and claim it at an appropriate level of specificity. In Ceiva, the separable interface mattered as part of the system, not as an isolated label.
Make the specification explain cause and effect. Connect the technical problem to the disclosed solution and explain why the solution changes device or system operation. Describe supported alternatives that can provide useful claim positions without relying solely on desired outcomes.
Develop claims with distinct eligibility positions. Consider claims that expressly capture the technical implementation alongside broader claims. Ceiva shows why a common disclosure cannot replace limitations missing from a particular claim.
Challenge abstractions that omit material limitations. When responding to a rejection or defending eligibility, map the asserted improvement to the actual claim language and supporting disclosure. Identify any characterization that overlooks the relationships responsible for the advance.
Keep eligibility and other patentability requirements separate. The § 101 inquiry into how a result is claimed is distinct from enablement. A favorable eligibility ruling also leaves §§ 102, 103, and 112 questions open. Product praise alone does not repair the absence of a claimed technical implementation. See slip op. at 13 n.3, 14, 16–17.
For software, AI, and connected medical-device applications, the drafting lesson is to connect the disclosed technical problem, the mechanism that solves it, and the limitations defining the claimed invention. Ceiva concerned digital picture frames rather than AI, but it supplies a concrete illustration of why that connection can determine the § 101 outcome.
****
Subscribe to get updates to this post or to receive future posts from PatentNext. Start a discussion or reach out to the author, Ryan Phelan, at rphelan@marshallip.com or 312-474-6607. Connect with or follow Ryan on LinkedIn.