Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
Ameranth v. Ticketfly | Federal Circuit Appeal | PatSnap
Patent Litigation

Ameranth v. Ticketfly — Federal Circuit Appeal, Case 22-1690

Ameranth, Inc. appealed against Ticketfly, Inc. asserting three patents covering information management and synchronous communications systems with menu generation. The Federal Circuit docket records an AFFIRMED verdict, yet the recorded Basis of Termination is Appeal Dismissed. The appeal ran 512 days before closing.

Resolution time
512days
512 days — duration of the Federal Circuit appeal from filing to close
Patents asserted
3
US8146077B2, US6871325B1 and US6384850B1 — information management & synchronous communications systems with menu generation
Outcome
Appeal Dismissed
Recorded Basis of Termination: Appeal Dismissed; docket order states AFFIRMED
Cost ruling
Not recorded
No costs ruling is disclosed in the available case record
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Ameranth's three-patent Federal Circuit appeal against Ticketfly

Ameranth, Inc. filed this Federal Circuit appeal on 18 April 2022, challenging a lower-court outcome in an infringement action against Ticketfly, Inc. The three patents at issue — US8146077B2, US6871325B1, and US6384850B1 — all relate to information management and synchronous communications systems with menu generation, a technology domain Ameranth has pursued assertively across multiple proceedings. Ticketfly was represented by DLA Piper US LLP; Ameranth by Stamoulis & Weinblatt LLC.

The appeal closed on 12 September 2023 after 512 days. The recorded Basis of Termination is 'Appeal Dismissed'; the docket order states 'THIS CAUSE having been heard and considered, it is ORDERED and ADJUDGED: AFFIRMED.' These two characterisations are reported as-is from the available record — the specific terms are not disclosed in the available record and the reader should reconcile them independently.

A 512-day Federal Circuit appeal timeline is consistent with a fully-briefed merits appeal. What drove the precise procedural posture at close — including whether any collateral proceedings, jurisdictional questions, or party stipulations contributed — is not disclosed in the available public record.

See Complete Case & Patent Analysis →
Case at a glance
Case no.22-1690
CourtCourt of Appeals for the Federal Circuit
JudgeN/A
FiledApril 18, 2022
ClosedSeptember 12, 2023
Duration512 days
OutcomeAppeal Dismissed
Verdict causeInfringement Action
BasisAppeal Dismissed
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Court of Appeals for the Federal Circuit via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Appeal Dismissed in 512 days

512 days — duration of the Federal Circuit appeal from filing to close

Case timeline: Appeal filed APR 18 2022 — 512 days total Horizontal timeline showing the three key events in Ameranth, Inc. v Ticketfly, Inc. from filing to resolution. Source: PACER, Court of Appeals for the Federal Circuit. APR 18 2022 Appeal filed Pre-trial proceedings SEP 12 2023 Appeal Dismissed 512 DAYS TOTAL
Patent at issue

US8146077B2, US6871325B1 & US6384850B1 — menu-generation & synchronous communications

Publication No.US8146077B2
Application No.US11/112990
Patent details
ProductInformation management and synchronous communications system with menu generation
Cited in actionApril 18, 2022

Publication No.US6871325B1
Application No.US10/015729
Patent details
ProductInformation management and synchronous communications system with menu generation
Cited in actionApril 18, 2022

Publication No.US6384850B1
Application No.US09/400413
Patent details
ProductInformation management and synchronous communications system with menu generation and handwriting and voice modification of orders
Cited in actionApril 18, 2022
Technical brief · sourced from PatSnap patent database
Patent figurePatent figure
Representative claim (1 of 8 independent)
1. An information management and real time synchronous communications system for configuring and transmitting hospitality menus comprising: a. a central processing unit, b. a data storage device connected to said central processing unit, c. an operating system including a first graphical user interface, d. a master menu including at least menu categories, menu items and modifiers, wherein said master menu is capable of being stored on said data storage device pursuant to a master menu file structure and said master menu is capable of being configured for display to facilitate user operations in at least one windo…
Technical background
The present application is a continuation of application Ser. No. 10/016,517, filed Nov. 1, 2001 now U.S. Pat. No. 6,982,733, which is a continuation-in-part of application Ser. No. 09/400,413, filed Sep. 21, 1999 (now U.S. Pat. No. 6,384,850). The contents of application Ser. No. 10/016,517 and application Ser. No. 09/400,413 are incorporated herein by reference. FIELD OF THE INVENTION This invention relates to an information management and synchronous communications system and method for generation of computerize…
Patent family
3 family members across 1 jurisdiction (US)
PatSnap Eureka · FTO Search Agent
Should you run an FTO against US8146077B2, US6871325B1 and US6384850B1?

Any company developing or deploying information management platforms, menu-generation systems, synchronous communications tools, or event and hospitality software should assess freedom-to-operate against Ameranth's patent family. The claims span both the core system architecture and specific input modalities (handwriting, voice), meaning even incremental product updates in these categories can intersect with asserted claim language.

Run FTO in Eureka
Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Official verdict

Official order — verbatim text

THIS CAUSE having been heard and considered, it is ORDERED and ADJUDGED:AFFIRMED.
Source: PACER Docket, Case 22-1690, Court of Appeals for the Federal Circuit

The docket order states 'AFFIRMED', indicating the Federal Circuit panel found no reversible error in the proceedings below — the standard applied is whether the lower court committed a legal error warranting correction. The recorded Basis of Termination, however, is 'Appeal Dismissed'. Both characterisations are drawn directly from the available record; the specific terms are not disclosed, and the two descriptions should be read as reported rather than reconciled.

PACER case 22-1690 · Public docket record Explore in Eureka ↗
Court ruling

Federal Circuit ruling: what the appeal outcome means for both parties

Legal mechanism

AFFIRMED at the Federal Circuit: lower decision stands

The docket order states AFFIRMED, meaning the Federal Circuit found no reversible error in the decision below — the lower court's ruling on Ameranth's infringement claims is upheld. Note: the recorded Basis of Termination is 'Appeal Dismissed', which presents a distinct characterisation. Both are reported from the available record; the specific terms are not disclosed and readers should reconcile them independently.

No reversible error found
Patent holder outcome

Ameranth's appeal does not advance its infringement claims

An affirmance at the Federal Circuit level means Ameranth, as appellant, did not succeed in overturning the lower-court outcome. Further appellate options at this level are exhausted. Any path forward — such as en banc rehearing or certiorari — would require additional procedural steps not evidenced in the available record.

Appellant's challenge unsuccessful
Defendant outcome

Ticketfly's position from the court below is maintained

As appellee, Ticketfly benefits from the affirmance: the lower-court outcome in its favour is confirmed by the Federal Circuit. The three Ameranth patents asserted against Ticketfly do not, on the basis of this appeal record, support a finding of infringement liability at this stage. The specific terms of any underlying district court judgment are not disclosed in the available record.

Appellee's position upheld
Commercial implications

Federal Circuit affirmance raises the bar for future Ameranth enforcement

A Federal Circuit affirmance of an adverse ruling strengthens the precedent against the asserted claims in this context and signals heightened risk for patent holders pursuing similar enforcement strategies in the information management and menu-generation technology space. Companies operating in adjacent ticketing and hospitality technology sectors should monitor Ameranth's remaining portfolio activity.

Enforcement signal for the sector
Legal analysis based on PACER docket records for case 22-1690 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffAmeranth, Inc.Company/Search in Eureka ↗
DefendantTicketfly, Inc.Company/Search in Eureka ↗
Plaintiff counselRichard C. WeinblattAttorneyCounsel for Ameranth, Inc.Search in Eureka ↗
Plaintiff law firmStamoulis & Weinblatt LLCLaw FirmRepresenting Ameranth, Inc.Search in Eureka ↗
Defendant counselErin GibsonAttorneyCounsel for Ticketfly, Inc.Search in Eureka ↗
Defendant law firmDLA Piper US LLPLaw FirmRepresenting Ticketfly, Inc.Search in Eureka ↗
Presiding judgeJudge N/AJudgeCourt of Appeals for the Federal CircuitSearch in Eureka ↗
R&D signals

R&D signals in the hospitality-tech & menu-generation IP space

Forward-looking patent and innovation intelligence derived from Ameranth's portfolio and the technology landscape around synchronous communications and menu-generation systems.

Patent portfolio

Ameranth's ongoing assertion activity across its menu-tech family

Ameranth has pursued enforcement across multiple defendants using patents anchored to early 1999–2001 priority dates. Tracking citations, continuations, and inter partes review activity across the US8146077, US6871325, and US6384850 families reveals the current enforceability perimeter and which claims have survived challenge — critical intelligence for any FTO or design-around effort.

Portfolio enforcement mapping
Technology landscape

Filing trends in synchronous communications and menu-generation systems

The menu-generation and synchronous-order-management space has seen increasing filing activity from hospitality SaaS players, POS vendors, and event-technology platforms. Understanding who is filing in adjacent claim spaces — and where white space exists relative to Ameranth's priority dates — can guide both design-around strategies and new product development.

Filing trend analysis
Competitive IP posture

Ticketfly and Eventbrite: patent positioning in event-tech platforms

Ticketfly's IP posture in the event and venue management software space — including any patents it holds or has licensed in information management and communications — is relevant context for competitors and acquirers. Mapping Ticketfly's own filing activity reveals how defensively or offensively it is positioned relative to platform incumbents.

Defendant IP positioning
White space

Innovation gaps adjacent to Ameranth's claimed architectures

Ameranth's claims focus on synchronous menu generation and multi-modal order modification. Adjacent areas — such as AI-driven dynamic menu personalisation, real-time inventory-linked menu updates, or voice-native order management integrated with cloud POS — may represent white space beyond the scope of the asserted claims, offering filing opportunities for R&D teams in the hospitality and event-tech sectors.

Adjacent white space
Related litigation

Similar Federal Circuit infringement appeals in hospitality and menu-tech

Explore related Federal Circuit appeals involving software patent infringement claims in the information management, menu-generation, and hospitality-technology sector.

🔍
Access 40+ similar cases in PatSnap Eureka
Ameranth, Inc. patent enforcement history, Court of Appeals for the Federal Circuit case history, Ameranth, Inc.'s full IP portfolio, and comparable case analysis
Ameranth v. Pizza HutMenu-tech § 101 appealsSynchronous comms patentsHospitality software IP cases
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the hospitality-tech IP landscape

Three Ameranth patents reach the Federal Circuit — the outcome carries enforcement and portfolio intelligence implications for the broader sector.

Ameranth's multi-patent strategy signals broad assertion risk in menu-tech

Asserting three related patents covering information management and menu generation in a single action is consistent with a portfolio-enforcement strategy. Companies developing synchronous communications or menu-generation systems should map their products against Ameranth's remaining active claims.

Federal Circuit involvement raises validity and claim scope stakes

Appeals to the Federal Circuit on infringement actions involving software-implemented systems frequently turn on claim construction and patent eligibility. The outcome here — however characterised — confirms this family reached the highest patent-specialised appellate level, making it a useful benchmark for FTO analysis.

🔒
Full strategic analysis in PatSnap Eureka
Unlock patent portfolio and enforcement strategy intelligence for the hospitality-tech and menu-generation sector, derived from this Federal Circuit appeal.
Remaining Ameranth claimsDefence strategy signalsFTO risk by claim family
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Ameranth v Ticketfly — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Run FTO and portfolio analysis on Ameranth's patent family

This Federal Circuit appeal confirms Ameranth actively enforces its menu-generation and synchronous communications patents at the highest appellate level. Use PatSnap Eureka to map claim scope, identify continuations, and assess FTO risk before your next product launch.

Disclaimer

This page is compiled from public court dockets and third-party patent and litigation data via PatSnap Eureka, and is provided for general informational purposes only. The information shown — including party names, patent and application numbers, dates, case status, outcomes, and any analysis — may be incomplete, may not reflect the most recent filings or legal status, and may contain errors or omissions. Verify all details against official court records (for example, PACER) and the relevant patent office before relying on them.

Nothing on this page constitutes legal advice or a legal opinion on the validity, infringement, enforceability, or scope of any patent or case, and no attorney‑client relationship is created by its use. Any description of an outcome (such as a dismissal, settlement, or consent judgment) is a general summary, not a legal determination. All patents, trademarks, and company or law‑firm names are the property of their respective owners. PatSnap makes no warranty as to the accuracy or completeness of this content and disclaims, to the fullest extent permitted by law, all liability for reliance on it. For advice on a specific matter, consult qualified legal counsel.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.