Book a demo

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

Try now
Flypsi v. Google: Federal Circuit Affirms Unpatentability of US11218585B2 | PatSnap
Patent Litigation

Flypsi v. Google (25-1010): Federal Circuit Affirms Patent Unpatentable

Flypsi, Inc. (dba Flyp) appealed a patentability ruling against Google LLC at the Federal Circuit over US11218585B2, a patent covering a telephone network system and method. The court issued a Rule 36 affirmance — the lower decision stands — closing the appeal after 588 days.

Resolution time
588days
588 days from filing to close — consistent with Federal Circuit appeal timelines for patent validity disputes
Patents asserted
1
US11218585B2 — telephone network system and method
Outcome
Unpatentable
Federal Circuit found no reversible error; lower unpatentability ruling stands
Cost ruling
Not recorded
No cost or fee award is recorded in the available public record
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Flypsi's telephone network patent falls at the Federal Circuit

Flypsi, Inc., operating as Flyp, brought appeal No. 25-1010 before the Court of Appeals for the Federal Circuit against Google LLC, docketed 2 October 2024. The case centred on US11218585B2 (application no. US17/243401), a patent covering a telephone network system and method. The verdict cause is recorded as patentability, specifically an invalidity/cancellation action, indicating the patent's validity had been challenged in a prior proceeding before the appeal was filed.

The Federal Circuit disposed of the appeal on 13 May 2026 with a per curiam Rule 36 judgement: 'AFFIRMED.' The recorded basis of termination is 'Unpatentable', confirming that the court found no reversible error in the underlying determination that US11218585B2 does not meet the requirements for patentability. The affirmance is binding and final at this appellate level. The specific terms and findings from the lower proceeding are not further elaborated in the available Rule 36 order.

A Rule 36 affirmance — issued without a written opinion — signals the Federal Circuit considered the lower tribunal's reasoning sufficient on its face and saw no need for further elaboration. For Flypsi, the path to further review narrows significantly: options would be limited to a petition for rehearing en banc or a petition for certiorari to the US Supreme Court. What drove the underlying unpatentability finding, and whether the claims faced prior art, obviousness, or eligibility grounds, is not disclosed in the available appellate record.

See Complete Case & Patent Analysis →
Case at a glance
Case no.25-1010
DefendantGoogle, LLC
CourtCourt of Appeals for the Federal Circuit
JudgeN/A
FiledOctober 2, 2024
ClosedMay 13, 2026
Duration588 days
OutcomeUnpatentable
Verdict causePatentability
BasisUnpatentable
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 Unpatentable in 588 days

588 days from filing to close — consistent with Federal Circuit appeal timelines for patent validity disputes

Case timeline: Appeal filed OCT 2 2024 — 588 days total Horizontal timeline showing the three key events in FLYPSI, INC., dba Flyp v Google, LLC from filing to resolution. Source: PACER, Court of Appeals for the Federal Circuit. OCT 2 2024 Appeal filed Pre-trial proceedings MAY 13 2026 Unpatentable 588 DAYS TOTAL
Patent at issue

US11218585B2 — Telephone network system and method

Publication No.US11218585B2
Application No.US17/243401
Patent details
ProductTelephone network system and method
Cited in actionOctober 2, 2024
Technical brief · sourced from PatSnap patent database
Patent figurePatent figure
Representative claim (1 of 3 independent)
1. A method of providing telephone service, comprising: automatically storing electronic information that indicates an association of a secondary telephone number and a primary telephone number with a mobile device in a computer memory associated with a server; automatically transmitting information that indicates an access telephone number to the mobile device via a data channel; automatically associating a primary telephone number and access telephone number pairing with a corresponding secondary telephone number and contact telephone number pairing in the computer memory; receiving, at a switch associated with…
Technical background
CROSS-REFERENCE TO RELATED APPLICATION(S) This application is a divisional application and claims the benefit of priority to co-pending U.S. patent application Ser. No. 17/039,566, filed Sep. 30, 2020 by Zhidov et al., which is a divisional of U.S. patent application Ser. No. 16/444,753, filed Jun. 18, 2019, by Zhidov, et al., which is a divisional application of U.S. patent application Ser. No. 16/031,806 (now U.S. Pat. No. 10,334,094), filed Jul. 10, 2018 by Zhidov, et al., which is a continuation application of…
Patent family
13 family members across 1 jurisdiction (US)
PatSnap Eureka · FTO Search Agent
Should you run an FTO analysis against US11218585B2?

Developers and product teams building telephone network systems, multi-number telephony applications, or VoIP call-routing infrastructure should be aware that US11218585B2 has been confirmed unpatentable by the Federal Circuit. While this specific patent no longer presents an enforcement risk, related Flypsi family patents or co-pending applications may cover similar claim scope and warrant independent review before product launch or market entry.

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. See Fed. Cir. R. 36.
Source: PACER Docket, Case 25-1010, Court of Appeals for the Federal Circuit

The Federal Circuit's order — 'AFFIRMED. See Fed. Cir. R. 36.' — disposes of the appeal summarily, indicating the panel found the lower tribunal's unpatentability determination free from reversible error. Rule 36 affirmances do not produce a written opinion and therefore generate no binding precedent, but they are legally equivalent to a full reasoned affirmance. The underlying basis of unpatentability governs the patent's status going forward.

PACER case 25-1010 · Public docket record Explore in Eureka ↗
Court ruling

Federal Circuit affirms: what the ruling means for both parties

Legal mechanism

Rule 36 affirmance: the lower decision stands without written opinion

A Federal Circuit Rule 36 judgement affirms the decision below without a written opinion when the court determines that no reversible error occurred and that a full written disposition is unnecessary. 'AFFIRMED' under Rule 36 carries the same legal weight as a reasoned opinion — the unpatentability determination is upheld in full. It does not, however, create binding precedent on the legal questions involved.

No reversible error found
Patent holder outcome

US11218585B2 confirmed unpatentable — enforcement rights extinguished

For Flypsi, the affirmance is a terminal ruling at the Federal Circuit level. With US11218585B2 confirmed unpatentable, Flypsi cannot enforce the patent against Google or any third party. Any licensing programme or infringement claims built around this patent are effectively foreclosed unless a higher court overturns the ruling. Further appeal would require en banc rehearing or Supreme Court certiorari — both statistically unlikely paths.

Patent rights extinguished
Challenger outcome

Google secures freedom to operate without the shadow of US11218585B2

Google's successful defence of the unpatentability challenge removes US11218585B2 as a potential enforcement risk. With the Federal Circuit's affirmance, Google and the broader market gain certainty that this telephone network patent cannot be asserted. The Rule 36 disposition means no new precedent is created, but the practical outcome — patent invalidated — is identical to a reasoned opinion.

FTO confirmed for Google
Commercial implications

Telephone network patent space: reduced assertion risk from this family

The invalidation of US11218585B2 removes one patent asset from the telephone network system and method domain. Competitors and technology developers operating in VoIP, multi-number telephony, and related spaces face reduced assertion risk from this specific patent. However, Flypsi's broader portfolio position is not disclosed in the available record — related family members or continuation patents may remain in force and should be independently monitored.

Monitor related family members
Legal analysis based on PACER docket records for case 25-1010 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffFLYPSI, INC., dba FlypCompany/Search in Eureka ↗
DefendantGoogle, LLCCompany/Search in Eureka ↗
Plaintiff counselBenjamin S. RichardsAttorneyCounsel for FLYPSI, INC., dba FlypSearch in Eureka ↗
Plaintiff counselEimeric ReigPlessisAttorneyCounsel for FLYPSI, INC., dba FlypSearch in Eureka ↗
Plaintiff law firmWinston & Strawn, LLPLaw FirmRepresenting FLYPSI, INC., dba FlypSearch in Eureka ↗
Defendant counselDaniel ZeilbergerAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselJoseph PalysAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselMichael WolfeAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant counselNaveen ModiAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant law firmPaul Hastings, LLPLaw FirmRepresenting Google, LLCSearch in Eureka ↗
Presiding judgeJudge N/AJudgeCourt of Appeals for the Federal CircuitSearch in Eureka ↗
R&D signals

R&D signals in the telephone network and multi-line app space

Forward-looking patent and innovation intelligence surfaced from the Flypsi v. Google Federal Circuit appeal — relevant to telephony, VoIP, and multi-number application developers.

Patent portfolio

Flypsi/Flyp patent family: what remains after US11218585B2?

With US11218585B2 invalidated, the live scope of Flypsi's IP position depends on continuation patents, divisional applications, or related filings under the same technology family. Mapping the full Flyp portfolio — including any pending applications — is essential for competitors and potential acquirers to understand residual assertion risk in the multi-number telephony space.

Monitor Flyp patent family
Technology landscape

Filing trends in multi-number telephony and VoIP call routing

The multi-number mobile telephony space — enabling separate lines on a single device — has attracted growing patent activity from both established carriers and app-layer startups. Analysing filing trends around call routing, number provisioning, and SIP-based telephony methods can identify emerging competitors and white-space claim areas before they become enforcement risks.

VoIP + multi-line filing trends
Competitor IP posture

Google's telephony and communication infrastructure patent position

Google's successful defence in this appeal is consistent with a broad IP portfolio in communications infrastructure, VoIP, and mobile telephony. Reviewing Google's granted patents and recent filings in telephone network systems can reveal the defensive and offensive scope of its IP position — informative for companies developing competing telephony products or seeking partnership and licensing opportunities.

Google telephony IP landscape
White space opportunity

Adjacent claim space in number management and telephony provisioning

The invalidation of US11218585B2 may create claim-space opportunities in telephone number provisioning, dynamic number assignment, and app-layer call management — areas adjacent to the invalidated claims. R&D teams exploring novel approaches in these sub-domains should assess whether differentiated claim strategies can establish protectable positions where prior art has eroded existing patents.

Telephony claim white space
Related litigation

Similar Federal Circuit telephony patent validity appeals

Explore Federal Circuit appeals involving telephone network and VoIP patent validity challenges — cases with comparable PTAB origins and Rule 36 dispositions in the communications technology sector.

🔍
Access 40+ similar cases in PatSnap Eureka
FLYPSI, INC., dba Flyp patent enforcement history, Court of Appeals for the Federal Circuit case history, FLYPSI, INC., dba Flyp's full IP portfolio, and comparable case analysis
VoIP patent PTAB appealsMulti-number app IP casesGoogle Federal Circuit winsRule 36 telephony affirmances
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the telephony patent IP landscape

A Rule 36 affirmance of unpatentability at the Federal Circuit sends a clear signal about assertion risk and patent quality in the telephone network space.

Rule 36 dispositions offer no written precedent but do close enforcement paths

A Federal Circuit Rule 36 affirmance is legally final but creates no citable precedent. For IP teams, this means the specific grounds of unpatentability remain opaque from the appellate order alone — practitioners should review the lower tribunal's record to understand what claim elements or prior art drove the invalidity finding before drawing broader conclusions.

Telephony and multi-number app patents face sustained validity scrutiny

The invalidation of a telephone network system and method patent in a Google-defended proceeding is consistent with broader pressure on software-implemented communication patents at the USPTO and PTAB. Companies holding or acquiring patents in this space should conduct rigorous claim-by-claim validity assessments before committing to enforcement or licensing strategies.

🔒
Full strategic analysis in PatSnap Eureka
Unlock full telephony patent portfolio analysis and Federal Circuit appeal strategy insights for this case.
Flypsi patent family mapPTAB prior art landscapeMulti-number VoIP patent risk
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

FLYPSI v Google — key questions answered

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

Monitor telephony patent risk after Flypsi v. Google

The invalidation of US11218585B2 reshapes the assertion landscape for telephone network and multi-number app patents. Use PatSnap Eureka to track surviving Flypsi family patents, run FTO searches, and receive alerts on new filings in the telephony domain.

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.