Skip to content

Constellation Designs v. LG: Result-Oriented Claims

Read from the decision; quotations on this page verified against its text.
CourtFederal Circuit
Decided28 April 2026
CitationNo. 2024-1822 (Fed. Cir. Apr. 28, 2026), modified and reissued Aug. 31, 2026, precedential
In one lineA claim that names the result you want, without saying how to get it, is an abstract idea however much the specification explains.
Holding

Claims reciting a constellation optimized for a named capacity measure were held abstract and result-oriented, because the claim said what was achieved and not how. Claims in the same family reciting specific constellations were upheld.

Four patents, one family, two kinds of claim, two different answers. That is what makes this the clearest teaching case in this cluster: you can see what moved a claim from one side of the line to the other without comparing two unrelated patents.

Of claim 17, the court said "we conclude that claim 17 is ineligible because it is an abstract, result-oriented claim directed to all ways of achieving a recited result." It reached that by comparison with O'Reilly v. Morse, the 1853 Supreme Court decision that upheld Morse's claims to the details of the telegraph and struck down the broad one.

What Separated the Two Sets

The split disposition in one family, from the opinion's own conclusion. As of 29 September 2026.
ClaimsWhat they reciteOutcome
Claims 17, 21, 24, 28 of the '761 patent and claim 5 of the '700 A constellation optimized for parallel decode capacity, defined by the performance achieved Eligibility vacated; abstract and result-oriented
Claims 21, 23 of the '509 patent and claims 24, 44 of the '922 Specific non-uniform constellations Eligibility affirmed

The court's description of the defect is worth reading slowly. "The claim itself does not recite how to achieve a constellation" optimized for that measure; instead "this important and distinguishing element of the claim is described in a result-oriented way." The breadth that follows is what the court identified as the abstract idea itself.

The patentee's best argument was that the claims did recite a concrete technique, namely using parallel decode capacity to optimize. The court's answer was that claim 17 "lacks sufficient details about the alleged" technique.

The Specification Does Not Rescue the Claim

This is the point engineers most often get wrong. The specification described an iterative process for arriving at these constellations. It did not save the claims that left that process out. Quoting ChargePoint, the court said "reliance on the specification must always yield to the claim language."

The same idea appears twice in the opinion. "the specification may help illuminate the true focus" of a claim, but the eligibility inquiry is about the claim. A thorough description is necessary for other reasons, including enablement and written description. It is not a substitute for putting the mechanism in the claim.

That is the same lesson GoTV v. Netflix and Columbia v. Gen Digital reach from different directions, and this decision states it with an eligible counterexample sitting next to the ineligible claims.

The Opinion You Should Cite Is the August One

The panel modified and reissued this opinion on 31 August 2026 after a petition for rehearing. The reissued document carries both dates in its header and a footnote saying "This opinion has been modified and reissued following a petition for rehearing." Everything above is unchanged by the modification: we compared the two documents sentence by sentence, and the eligibility analysis and the disposition paragraph are word for word identical.

One passage was removed. In the April version, the footnote disposing of LG's damages argument gave a backup reason on the merits. The August version stops at the procedural one. What survives is the procedural holding, and it is the part worth carrying away:

LG argued that ineligible claims should void the damages award, and lost that argument on timing. The court recorded that LG raised it "for the first time" at oral argument, that "[t]his argument was foreseeable and should have been raised in LG's opening brief", and cited a case "collecting cases for proposition that arguments raised for the first time during oral argument are forfeited." The damages award stood on a patent family that had just lost five claims.

The same precision explains the word vacated in the table above rather than reversed. A footnote records that "LG never crossmoved for summary judgment of patent ineligibility" and instead argued that "genuine issues of material fact preclude[d] summary judgment." The court held claim 17 ineligible and sent the claims back; it did not enter judgment against them.

What This Does Not Decide

  • It states no threshold. The opinion does not say how much mechanism a claim needs, and the surviving claims were upheld because they recited specific constellations, not because they cleared a stated bar.
  • It does not say whether any other claim is eligible.
  • The case also addressed infringement, damages and expert testimony. Those parts are covered only in the section above.

Educational, not legal advice. Reporting what a court held is not advice on how to draft a claim, which is work for a registered practitioner.

Sources

  • Constellation Designs, LLC v. LG Electronics Inc., No. 2024-1822, opinion issued 28 April 2026 and modified and reissued 31 August 2026, precedential, on appeal from E.D. Tex. No. 2:21-cv-00448-JRG. Both versions were read; the August one is the controlling document
  • O'Reilly v. Morse, 56 U.S. (15 How.) 62 (1853), as the opinion applies it
  • Back to the cluster: software patents after Alice