Patent Invalidation in San Francisco

patent invalidation San Francisco prior art and section 101 search by PerspireIP

Patent invalidation San Francisco strategy runs on a different weapon than it does anywhere else, because the patents asserted here are overwhelmingly software, fintech and artificial-intelligence patents, and the sharpest tool against them is 35 U.S.C. Β§ 101 subject-matter eligibility under the Supreme Court’s Alice framework. Cases land in the Northern District of California, a court with its own Patent Local Rules and a hard clock on invalidity contentions. PerspireIP builds the prior-art record that supports both the eligibility attack and the conventional Β§Β§ 102/103 grounds behind it.

Why patent invalidation San Francisco cases turn on Β§ 101 eligibility

In Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014), the Supreme Court set a two-step test for patent eligibility under 35 U.S.C. § 101. Step one asks whether the claim is directed to a judicial exception such as an abstract idea. If it is, step two asks whether the additional claim elements, individually and as an ordered combination, amount to significantly more than the exception itself.

That framework hits San Francisco defendants harder than anyone. The patent in Alice itself claimed a computer-implemented scheme for mitigating settlement risk — a financial method — and the same logic reaches payments, lending, marketplace, analytics and machine-learning claims drafted at a functional level of abstraction. Eligibility is a question of law, so unlike anticipation or obviousness it can be decided by a judge without a jury, and often long before trial.

For a venture-backed company facing an assertion campaign, that timing is the whole commercial argument. A successful eligibility ruling ends the case on the pleadings or on early summary judgment, before discovery costs and source-code production reshape the settlement maths.

Alice step two is a factual fight, and prior art is the evidence

The common misconception is that a § 101 motion needs no prior art. Since the Federal Circuit’s 2018 decisions in Berkheimer v. HP Inc. and Aatrix Software v. Green Shades Software, whether the additional claim elements were “well-understood, routine and conventional” in the relevant field is treated as a question of fact. A conclusory assertion that a step was conventional will not carry a motion; evidence will.

Aatrix also confirmed that eligibility can be resolved at the Rule 12(b)(6) stage only where no plausible factual allegation, taken as true, prevents deciding the question as a matter of law. Patentees have adapted: modern complaints plead in detail that the claimed architecture was a departure from what the art then offered.

The answer is documentary. Contemporaneous references showing the disputed elements — the caching layer, the tokenisation step, the model-training loop — already deployed as ordinary practice before the priority date convert an argument into a record. That is prior-art work, and it is why an eligibility motion and an invalidity search should be scoped together rather than sequentially.

The Northern District of California Patent Local Rules and the 45-day clock

The Northern District of California, which sits in San Francisco, Oakland and San Jose, was the first federal court to adopt Patent Local Rules, and they impose a discipline that surprises defendants used to open-ended discovery. Under Patent L.R. 3-1, a patentee must serve its Disclosure of Asserted Claims and Infringement Contentions not later than 14 days after the Initial Case Management Conference.

Patent L.R. 3-3 then requires each party opposing infringement to serve its Invalidity Contentions not later than 45 days after service of those infringement contentions. The contentions must identify each item of prior art, state whether it anticipates or renders the claim obvious, and include claim charts mapping every limitation. Patent L.R. 3-3 also captures grounds under §§ 101 and 112, and Patent L.R. 3-4 requires an accompanying production including copies of the prior art itself.

Claim construction follows immediately: exchange of claim terms within 14 days of the invalidity contentions, and proposed constructions 21 days after that. Contentions are treated as binding disclosures, and amending them later requires leave on a good-cause showing. Practically, the prior art you find in those first weeks is the prior art you litigate.

Non-patent literature: the real prior art for Bay Area software

Software prior art is usually not in a patent. It is in an ACM or IEEE conference paper, an RFC, a product manual, a release note, a mailing-list thread, a commit history, or a version of a documentation site that only survives in a web archive. Bay Area engineering culture published relentlessly and shipped open source, which means the invalidating disclosure often exists — it simply was never indexed as patent literature.

The evidentiary problem is proving it qualifies. A reference is a “printed publication” only if it was publicly accessible: disseminated or otherwise available such that persons interested and ordinarily skilled in the art, exercising reasonable diligence, could locate it. Courts and the PTAB weigh the nature of the meeting or distribution, any restrictions on disclosure, and expectations of confidentiality.

  • Conference proceedings, workshop papers, posters and technical talks, with dissemination evidence
  • Product manuals, datasheets, SDK guides, release notes and admin documentation
  • Open-source repositories, tagged releases, commit logs and package registry timestamps
  • Standards drafts, RFCs, whitepapers and archived documentation captures

We chase the date as hard as the disclosure — catalogue records, distribution lists, archive timestamps, registry metadata — because an undated reference is not a reference.

Inter partes review at the PTAB: the parallel track and its limits

Many San Francisco defendants run a PTAB inter partes review alongside the district-court case. IPR is powerful but deliberately narrow: under 35 U.S.C. § 311(b) a petitioner may seek cancellation only on grounds that could be raised under § 102 or § 103, and only on the basis of prior art consisting of patents or printed publications.

That statutory limit is the reason the two tracks are complementary rather than interchangeable. Section 101 eligibility cannot be raised in an IPR at all, so the Alice attack must go to the district court. Conversely, prior public use or on-sale evidence — a system shipped to customers, a product demonstrated at a trade show — also falls outside IPR and belongs in your N.D. Cal. contentions.

Two deadlines govern the choice. Under § 315(b) a petition is barred if filed more than one year after the petitioner was served with a complaint alleging infringement of that patent. And under § 315(e)(2), after a final written decision the petitioner is estopped from raising in the district court any ground it raised or reasonably could have raised. Sequencing and ground-selection therefore have to be decided early, on a complete search.

San Francisco’s exposure: software, fintech, AI and NPE campaigns

San Francisco concentrates exactly the technologies that assertion entities target. Enterprise software and SaaS, payments and fintech, marketplaces and logistics platforms, developer infrastructure, and now a dense cluster of artificial-intelligence and machine-learning companies all operate within a few square miles, backed by the venture capital that makes a fast settlement look cheaper than a defence.

Non-practising entities build campaigns around that asymmetry, asserting broad computer-implemented claims against many companies at once and pricing demands below the cost of litigating. The countermeasure is a strong, transferable invalidity record. Prior art that reads on the asserted claims does not just defend one defendant; it devalues the patent across the entire campaign and changes the economics of every parallel negotiation.

We also work the other side of the table for San Francisco companies enforcing their own rights, pressure-testing a portfolio before assertion so an eligibility or prior-art counterattack does not arrive as a surprise. Either way, the search is technology-first: we read the claims against how the field actually worked at the priority date.

How PerspireIP builds your invalidity record for N.D. Cal.

Every engagement starts with element-by-element claim mapping, then splits into two coordinated searches: classical patent and printed-publication art for §§ 102 and 103, and conventionality evidence aimed squarely at Alice step two. The deliverable is charted, dated and cited so your counsel can drop it into Invalidity Contentions, an eligibility brief or an IPR petition without rebuilding the analysis.

  • Claim charts aligned to Patent L.R. 3-3’s anticipation and obviousness requirements
  • Public-accessibility and date evidence packaged with every non-patent reference
  • A separate “well-understood, routine and conventional” exhibit set for step two
  • Ground-selection analysis across district court, IPR and post-grant options

Our patent invalidation San Francisco work sits alongside our Prior Art Litigation Search and Patent Infringement Analysis practices, and under the broader Patent Invalidation service. We work to your litigation calendar, keep every engagement confidential, and scale from a single asserted patent to a multi-defendant campaign. Send the patent number and your case-management dates, and we will scope the search within one business day.

IP Landscape & Resources in San Francisco

Key intellectual-property authorities and venues relevant to San Francisco:

Request a Patent Invalidation Search in San Francisco

Request a Patent Invalidation Search in San Francisco

Get an invalidity record built for N.D. Cal. Patent Local Rule 3-3 contentions, an Alice section 101 motion and a parallel IPR petition. Send us the patent number and your case-management dates, and we will scope the work within one business day.

Explore related PerspireIP services: Patent Invalidation · Prior Art Litigation Search · Patent Infringement Analysis.

Frequently Asked Questions

When are invalidity contentions due in the Northern District of California?

Under Patent L.R. 3-3, a party opposing infringement must serve Invalidity Contentions not later than 45 days after being served with the patentee’s Disclosure of Asserted Claims and Infringement Contentions, which itself is due 14 days after the Initial Case Management Conference. The contentions must identify each prior-art item, state anticipation or obviousness, and include claim charts. Patent L.R. 3-4 requires producing copies of the prior art alongside them.

Can I raise an Alice section 101 challenge at the PTAB instead of in San Francisco?

No. Under 35 U.S.C. Β§ 311(b), an inter partes review may only be based on grounds under Β§Β§ 102 or 103, and only on patents or printed publications. Subject-matter eligibility under Β§ 101 is outside that scope, so an Alice challenge has to be brought in the district court β€” typically as a Rule 12(b)(6) motion or an early summary judgment motion before the Northern District of California.

Why does a section 101 motion need prior art at all?

Because Alice step two asks whether the additional claim elements were well-understood, routine and conventional, and the Federal Circuit held in Berkheimer and Aatrix that this is a question of fact. Conclusory assertions lose. Contemporaneous references β€” conference papers, manuals, open-source code, archived documentation β€” showing those elements were ordinary practice before the priority date are what make the eligibility argument survive a plausibility challenge from the patentee’s pleadings.

How do you prove a GitHub repo or conference paper counts as prior art?

A reference qualifies as a printed publication only if it was publicly accessible: available such that persons interested and ordinarily skilled in the art, exercising reasonable diligence, could locate it. For Bay Area software art we gather dissemination and dating evidence β€” proceedings and catalogue records, distribution and attendance details, commit and tag timestamps, package-registry metadata and web-archive captures β€” and note any confidentiality restrictions that could defeat accessibility.