A Federal Circuit patent decision rarely arrives with the convenience of a side-by-side comparison. Usually, patent eligibility law gives attorneys a stack of opinions, a two-part test, several judicial exceptions, and enough uncertainty to keep a conference room occupied until the coffee runs out.
Constellation Designs, LLC v. LG Electronics Inc., decided on April 28, 2026, is different. In one precedential opinion, the U.S. Court of Appeals for the Federal Circuit examined two groups of patent claims based on closely related telecommunications technology. It concluded that one group was too abstract and result-oriented to remain patent eligible, while the other contained enough concrete structure to survive a challenge under 35 U.S.C. § 101.
The ruling does not eliminate the confusion surrounding patent-eligible subject matter. Patent law has not suddenly become a friendly instruction manual with cheerful diagrams. However, the decision gives patent applicants, litigators, technology companies, and inventors an unusually clear lesson: describing an impressive result is not the same as claiming the technological way in which that result is achieved.
Why This Federal Circuit Decision Matters
Section 101 of the Patent Act permits patents for new and useful processes, machines, manufactures, and compositions of matter. Courts have also recognized exceptions for laws of nature, natural phenomena, and abstract ideas. Those exceptions are meant to prevent a patent owner from monopolizing the basic tools of scientific and technological work.
Under the Supreme Court’s Alice and Mayo framework, a court first asks whether a patent claim is directed to one of those excluded concepts. If it is, the court then asks whether the remaining claim elements contain an inventive concept that transforms the claim into a patent-eligible application.
Simple enough on paper. In practice, identifying an “abstract idea” can feel like identifying modern art: everyone knows one when they see it, but the explanations become lively as soon as lawyers enter the room.
The importance of Constellation Designs is that the Federal Circuit reviewed claims involving the same general inventive insight and reached opposite eligibility conclusions. That contrast makes the case particularly useful for understanding where the court currently draws the line between an abstract goal and a specific technological implementation.
The Technology Behind Constellation Designs v. LG
How Signal Constellations Work
The patents involved digital communication systems used to convert digital bits into analog signals for transmission and then convert the received signals back into digital information. A “constellation” is a visual representation of possible transmitted symbols. Each point corresponds to a combination of signal characteristics and represents a particular pattern of digital bits.
As a broadcast signal travels, it becomes weaker and collects noise. That interference can make it harder for a receiver, such as a television, to identify the correct transmitted symbol. Traditional systems often relied on uniform constellations, with points arranged at regular distances from one another.
The inventors associated with Constellation Designs used non-uniform constellations optimized according to a measurement called parallel decode capacity. Their approach could improve transmission performance at certain signal-to-noise ratios. One counterintuitive feature was that some constellation points could occupy the same location while carrying different labels.
The Dispute With LG Electronics
Constellation Designs accused LG televisions compatible with the ATSC 3.0 broadcast standard of infringing several patents. The dispute eventually focused on nine claims from four patents.
The Eastern District of Texas found all of the asserted claims eligible under Section 101. A jury later found infringement, determined that the infringement was willful, and awarded approximately $1.68 million in past damages based on a royalty of $6.75 per television.
LG appealed several issues, including patent eligibility. The Federal Circuit divided the asserted claims into two categories:
- Optimization claims, which broadly covered constellations optimized for parallel decode capacity.
- Constellation claims, which recited particular non-uniform constellation structures and defined characteristics.
That division became the heart of the eligibility analysis.
Why the Optimization Claims Failed Section 101
The Claims Described the Destination, Not the Route
The representative optimization claim described a digital communication system using a geometrically spaced QAM symbol constellation “optimized” for parallel decode capacity. The problem, according to the Federal Circuit, was that the claim did not explain how the optimization was performed.
It stated the desired result: better capacity at a reduced signal-to-noise ratio. But it did not meaningfully limit the process for reaching that result. In the court’s view, the claim was drafted broadly enough to cover essentially every method of optimizing a constellation for parallel decode capacity.
The Federal Circuit compared this problem to the nineteenth-century Supreme Court decision in O’Reilly v. Morse. Samuel Morse was entitled to claim his specific telegraph implementation, but he could not claim every use of electromagnetism for transmitting intelligible information over a distance. Owning the machine was one thing; attempting to reserve every road leading to the same destination was another.
The optimization claims faced the same concern. They claimed the outcome without placing meaningful boundaries around the technological means used to produce it.
The Specification Could Not Repair the Claims
Constellation Designs pointed out that the patent specification described an iterative optimization process. That disclosure included selecting a constellation size, estimating a signal-to-noise ratio, optimizing the constellation, checking whether values had converged, and repeating the process when necessary.
Those details sounded technical because they were technical. Unfortunately for the patent owner, they were not adequately incorporated into the disputed optimization claims.
The Federal Circuit emphasized that a Section 101 inquiry must focus on the claim language. A detailed specification may help explain the invention, but it cannot quietly lend limitations to claims that do not contain them. In other words, the specification cannot arrive halfway through the lawsuit wearing a superhero cape and rescue a claim from the language the applicant actually chose.
Novelty Did Not Supply an Inventive Concept
At the second step of the Alice analysis, Constellation Designs argued that the inventors had produced counterintuitive performance improvements and had been the first to develop certain optimized non-uniform constellations.
The court rejected that argument because novelty, non-obviousness, and patent eligibility are separate inquiries. An idea can be new yet still be claimed at an impermissibly abstract level. Likewise, surviving challenges under Sections 102 or 103 does not automatically establish an inventive concept under Section 101.
The alleged inventive concept was essentially the same optimization idea that made the claims abstract at step one. Repeating the abstract idea with greater enthusiasm did not transform it into something significantly more.
Why the Specific Constellation Claims Survived
The second group of claims received a very different result. Instead of claiming all constellations optimized for a desired capacity, these claims described specific non-uniform configurations.
The representative eligible claim required, among other limitations, unequally spaced point locations, different labels for the constellation points, and at least two points occupying the same location. Those were identifiable structural characteristics rather than a generalized instruction to optimize performance.
The Federal Circuit concluded that the claims addressed a particular technological problemcapacity constraints in digital communication systemswith a particular technological solution. Because the claims included sufficient specificity and structure, the court held that they were not directed to an abstract idea at Alice step one. There was therefore no need to continue to step two.
This distinction is the decision’s central lesson. Both groups of claims arose from the same research and the same technical field. Both were supported by detailed specifications. Yet the broad claims covering a desired optimization result were vulnerable, while claims reciting concrete configurations remained eligible.
A Broader Pattern in Federal Circuit Patent Eligibility Cases
Constellation Designs fits a growing pattern in Federal Circuit decisions. Claims are more likely to survive when they identify how a technical improvement is implemented through particular structures, processing steps, relationships, or system behavior.
In PowerBlock Holdings v. iFit, for example, the Federal Circuit found claims covering an automatically adjustable dumbbell eligible because they recited a specific combination of nested weight plates, a handle, a movable selector, and a motor connected to that selector. The district court had oversimplified the invention as the abstract idea of automated weight stacking. The appellate court instead considered the claimed structure as a whole.
By contrast, in Recentive Analytics v. Fox, the Federal Circuit found machine-learning claims ineligible where they applied established machine-learning techniques to scheduling and network-map problems without claiming an improvement to the underlying models or their operation.
Together, these decisions suggest that merely adding “automatically,” “using artificial intelligence,” or “optimized” to a familiar objective is unlikely to carry the day. Those words can describe powerful technologies, but they can also function as decorative legal parsley unless the claim explains the operational mechanism that makes the technology different.
Practical Lessons for Patent Drafting
Claim the Mechanism, Not Merely the Benefit
A claim should do more than promise faster processing, better accuracy, reduced bandwidth, improved security, or optimized performance. It should identify the components, relationships, transformations, constraints, or ordered steps responsible for that improvement.
Applicants should ask whether a claim tells a technically trained reader how the result is achieved. A claim that says “optimize a network to reduce congestion” presents substantial eligibility risk. A claim describing a particular data structure, routing rule, measurement sequence, feedback operation, and threshold-based adjustment offers a more concrete story.
Build Multiple Levels of Claim Scope
A patent application should not rely exclusively on one sweeping independent claim. A layered claim strategy can include broader claims, intermediate claims containing implementation constraints, and narrower claims directed to specific architectures or configurations.
The Constellation patents illustrate why this matters. When the optimization claims encountered trouble, the claims covering concrete constellation structures remained standing. Claim diversity can prevent an eligibility dispute from becoming an all-or-nothing event.
Align the Claims With the Technical Narrative
The specification should clearly identify the technical problem, prior technical limitations, the claimed improvement, and the mechanisms producing that improvement. More importantly, the most important mechanisms should appear in the claims.
A patent cannot depend on readers performing an intellectual scavenger hunt through 80 pages of description to discover why a six-line claim is supposedly technological. The relationship between the invention’s contribution and the claim language should be visible without binoculars.
Implications for Patent Litigation
For accused infringers, the decision provides a framework for challenging claims that define an invention primarily by a desired result. A strong Section 101 argument may compare the claim language with the specification and demonstrate that the detailed implementation appears only in the description, not in the claims.
Patent owners, meanwhile, should resist characterizations that strip away meaningful claim limitations. Courts have repeatedly warned against describing claims at an excessively high level of abstraction. A patent covering a defined signal configuration should not automatically become “the idea of communicating information,” just as a motorized adjustable dumbbell should not be reduced to “changing weight.”
The case also shows that eligibility, infringement, and damages remain distinct issues. Although the Federal Circuit vacated the eligibility ruling for the optimization claims, it affirmed the eligibility of the constellation claims and left the infringement and damages rulings intact. The court also approved the use of industry-standard evidence for some claim limitations combined with product-specific evidence for others.
What the Decision Does Not Mean
The decision does not establish that every functional claim is invalid. Patent claims frequently use functional language, particularly in software, electronics, and communications. The concern arises when the claim covers a result without meaningful restrictions on how the result is produced.
Nor does the ruling mean that mathematical techniques, optimization methods, or software-based inventions are automatically ineligible. Such inventions may qualify when the claims integrate those concepts into a specific practical application or recite a concrete improvement in technology.
Finally, there is no magic phrase that guarantees eligibility. Adding “technical,” “specialized,” or “computer-implemented” does not solve a structural problem in the claim. Courts examine what the claim actually requires, not how many impressive adjectives attended its drafting ceremony.
Experience-Based Perspective: Applying the Decision in Real Patent Work
Recurring experience across patent prosecution, portfolio reviews, and infringement disputes shows that eligibility problems often begin long before anyone files a lawsuit. They begin when an invention disclosure describes the business objective brilliantly but treats the engineering mechanism as an inconvenient footnote.
Imagine a software team that develops a system capable of reducing cloud-computing costs by 30 percent. The initial invention disclosure may focus on the result: workloads are “dynamically optimized” across servers. That language sounds attractive in a presentation, but it leaves unanswered questions. What data does the system collect? How does it classify workloads? Which constraints determine placement? Does it use a particular feedback loop? What happens when latency and cost targets conflict?
The strongest drafting experience usually comes from interviewing the engineers until those details emerge. The first description may say, “The platform intelligently selects a server.” After several rounds of discussion, the actual invention may involve generating a resource vector, comparing it with node-specific capacity profiles, excluding nodes that violate a latency boundary, and assigning the workload according to a weighted score recalculated after each deployment.
That second explanation is less elegant for a marketing brochure, but far more useful for patent claims. It describes a mechanism rather than applauding an outcome.
Portfolio reviews reveal another common experience: older patent families often contain excellent implementation details in the specification but very broad claims built around functional results. When those patents enter licensing negotiations or litigation, the owner may discover that its best technical arguments are not reflected in the asserted claims. The Constellation decision makes that mismatch especially dangerous.
A practical review should therefore compare every important claimed benefit with the limitation that allegedly produces it. When the benefit appears in the claim but the mechanism exists only in the specification, continuation practice may offer an opportunity to pursue more concrete claims while the family remains pending.
Litigation experience also demonstrates the value of preparing competing claim characterizations early. The accused infringer will often describe the claim in broad terms: collecting data, optimizing a result, displaying information, or automating a human activity. The patent owner will describe a specialized architecture solving a technical problem.
The better argument is usually the one most closely tied to actual claim language. Diagrams, expert explanations, and specification passages can provide context, but they cannot manufacture limitations. Claim charts prepared for eligibilitynot just infringementcan help a team identify the precise language supporting its technological-improvement theory.
Another useful experience is to test a draft claim with a simple question: could radically different technologies satisfy the claim merely because they achieve the same outcome? When the answer is yes, the claim may be result-oriented. Adding implementation constraints, structural relationships, or ordered operations can reduce that risk without limiting the claim to a single commercial embodiment.
The goal is not to make every claim microscopic. Claims must still have commercially meaningful scope. The drafting challenge is to claim the inventive territory without attempting to own the entire continent. Constellation Designs demonstrates that a portfolio can contain both vulnerable broad claims and durable implementation claims based on the same underlying discovery. Thoughtful claim layering turns that observation into a strategy rather than a post-litigation regret.
Conclusion
The Federal Circuit’s decision in Constellation Designs v. LG offers one of the clearest recent comparisons between result-oriented patent claims and claims directed to a concrete technological implementation.
The optimization claims failed because they broadly claimed constellations optimized for a desired result without reciting how that optimization was achieved. The specific constellation claims survived because they defined particular structural characteristics that addressed a recognized technological problem.
For inventors and patent applicants, the message is straightforward: include the machinery of innovation, not merely the applause line. For litigators, the case provides useful language for both challenging overbroad claims and defending claims containing meaningful technological structure. Section 101 remains complicated, but this decision supplies a practical compass: specificity, structure, and claimed implementation matter.
Note: This article provides general information about U.S. patent law and does not constitute legal advice. Eligibility outcomes depend on the complete claim language, specification, procedural record, and applicable precedent.
