Patent Invalidation in Seattle

Patent invalidation Seattle work is unlike invalidity practice anywhere else in the country, because the patents asserted here read on cloud platforms, distributed systems, logistics software and e-commerce infrastructure rather than on machines you can put on a bench. Amazon and AWS sit in South Lake Union, Microsoft is across the lake in Redmond, Boeing builds commercial aircraft at Everett and Renton, and a dense layer of storage, networking and marketplace companies fills the gaps. For that technology, the decisive prior art is almost never another patent. It is non-patent literature: an RFC, a conference paper, a mailing-list thread, a commit log, a release note. PerspireIP finds that material and, just as importantly, proves when it became public.

Why patent invalidation Seattle cases are won in non-patent literature

Distributed computing grew up in the open. Long before the cloud patents now being asserted were filed, the same ideas — consistent hashing, leader election, eventual consistency, content distribution, container scheduling, overlay routing — were being described in standards drafts, academic papers, engineering blogs and source code. The result is that the closest art to a modern infrastructure claim usually sits outside any patent database, in material nobody ever indexed with an examiner in mind.

That reshapes what an invalidity search has to be. A classification-driven sweep of granted patents will miss the reference that actually anticipates the claim, and an examiner working under time pressure almost certainly missed it too — which is precisely why it carries weight. The hard work is not finding the document. It is establishing, on a record a tribunal will accept, that the document was publicly available before the challenged patent’s effective filing date.

Everything below is about that second problem, because in Seattle technology disputes it is where invalidity positions are made or lost.

What actually qualifies as a printed publication under 35 U.S.C. § 102

Under 35 U.S.C. § 102(a)(1), a claimed invention is not patentable if, before its effective filing date, it was “patented, described in a printed publication, or in public use, on sale, or otherwise available to the public.” The phrase “printed publication” is far broader than it sounds. Nothing has to be printed, bound, sold or catalogued. The touchstone the Federal Circuit applies is public accessibility.

A reference is publicly accessible if it was disseminated or otherwise made available to the extent that persons interested and ordinarily skilled in the subject matter or art, exercising reasonable diligence, could locate it. Two consequences follow. First, you do not have to prove that anyone actually read it — in Samsung Electronics v. Infobridge (Fed. Cir. 2019) the court confirmed a challenger need not show the reference was received by, or available to, a significant portion of those skilled in the art.

Second, formal indexing is not a strict prerequisite — but practical findability still matters enormously. In Acceleration Bay v. Activision Blizzard (Fed. Cir. 2018), a case about overlay networks for distributed broadcasting, a technical report posted on a university computer-science department’s website failed the test: it was indexed only by author name and year, and the evidence about the site’s search function did not establish that a diligent skilled searcher could have found it.

Two documents can be equally real and equally on point, and only one of them is prior art. The difference is the evidentiary record you build around it.

Where Seattle’s cloud prior art lives: RFCs, USENIX papers, repositories and release notes

A patent invalidation Seattle search runs across sources that a conventional patent search never touches. Each has its own accessibility story, and we chart that story alongside the technical mapping.

• IETF RFCs and Internet-Drafts — the Datatracker carries publication dates and full version histories, and superseded drafts are archived rather than deleted
• IETF and working-group mailing-list archives — every public message has a permanent, dated URL, the same kind of listserv circulation at issue in Infobridge
• USENIX, SIGCOMM, OSDI, NSDI and SOSP proceedings — the operating-systems and networking literature that underpins most cloud claims, much of it openly published
• Open-source repositories and commit histories — signed, timestamped commits, tagged releases, issue threads and design documents
• Product documentation, changelogs and release notes — how a service actually worked on a given date
• Archived web pages — captures recovered through the Internet Archive and supported by its declaration

Seattle’s technology base makes these sources unusually productive. The engineers who built early distributed storage, marketplace and content-delivery systems in this region published as they went, contributed to standards bodies, and shipped documentation. That paper trail is the raw material of a serious invalidity case.

Proving the date: the evidentiary problem that decides cloud IPRs

Finding the reference is the easy half. The half that wins or loses the proceeding is corroborating that it was publicly available before the critical date. A file’s metadata is not evidence of publication. A page that is reachable today says nothing about 2011. A commit timestamp can be rewritten. Tribunals know all of this, and patent owners argue it hard.

The PTAB’s Precedential Opinion Panel addressed the standard in Hulu v. Sound View Innovations (IPR2018-01039, December 2019), holding that a petition must identify evidence sufficient to establish a reasonable likelihood that the reference was publicly accessible before the critical date. The panel was explicit that there is no presumption in favour of finding a reference to be a printed publication. Conventional indicia — copyright and printing dates, an ISBN, publication in an established series — can carry that burden.

For born-digital material the indicia are different, so we assemble them deliberately: Datatracker version records, dated archive URLs, conference proceedings front matter, mirrored copies held by independent parties, repository history, and Internet Archive captures supported by the Archive’s standard affidavit. Note the caution running through PTAB decisions on archived pages — showing that a page existed online is not the same as showing it was publicly accessible in the legal sense.

Authentication is a separate hurdle again, and a solvable one. In Valve Corp. v. Ironburg Inventions (Fed. Cir. 2021) — litigation involving a Washington-based games company — the court held that authentication by comparison is routine, and that a printout of an online article could be authenticated against a substantively identical copy. Where corroboration is thin, a declaration from a librarian, archivist, conference organiser or contemporaneous participant often supplies what documents alone cannot.

System prior art, public use, and what an IPR cannot reach

Deployed services are a distinct category of prior art. If a distributed system was in public use or otherwise available to the public before the effective filing date, it can invalidate under § 102 — and for infrastructure patents the running system is frequently closer to the claims than anything written about it. Proving it means reconstructing configuration, architecture, availability and dates from documentation, contracts, internal design records and witness testimony.

Forum choice then becomes strategic, because 35 U.S.C. § 311(b) limits an inter partes review to grounds under § 102 or § 103 and only on the basis of prior art consisting of patents or printed publications. System and public-use art simply cannot be run at the PTAB. That is the structural reason the NPL angle dominates cloud IPR practice: whatever you know about how a service worked has to be converted into documents that qualify as printed publications, or the ground stays in district court.

The two records also serve different audiences. A district-court jury in Seattle can be shown what a service did, when it did it, and who used it, with engineers testifying to the architecture they built. A PTAB panel of technically trained judges will instead read the document you filed and ask a narrower question: was this available to the interested skilled artisan before the critical date, and what proves it? The same underlying facts, marshalled two different ways.

Getting that allocation right early also protects against estoppel surprises. Under 35 U.S.C. § 315(e)(2), a petitioner who reaches a final written decision is estopped in district court from raising grounds it raised or reasonably could have raised in the review — an issue litigated at length in this district in the Ironburg and Valve dispute. Deciding deliberately which references go into the petition, and why, is part of the search strategy rather than an afterthought.

We scope searches around that split from the outset — documentary grounds built to survive a printed-publication challenge for the petition, and the fuller system-art record preserved for the parallel district-court invalidity case.

Timing invalidity work for the Western District of Washington and the PTAB

Patent cases against Seattle-area technology companies are heard in the U.S. District Court for the Western District of Washington, whose Seattle courthouse stands at 700 Stewart Street. The district’s Local Patent Rules compress the invalidity timetable sharply. Under LPR 120, a party claiming infringement serves its asserted claims and infringement contentions within 15 days of the scheduling conference. Under LPR 121, the accused infringer must serve non-infringement and invalidity contentions no later than 30 days after that.

Those contentions are demanding. LPR 121 requires each prior-art publication to be identified by title and date of publication, with author and publisher where feasible, and requires public uses or sales to be identified by the item, the date, and the identity of the person or entity involved — date evidence, in other words, is a pleading obligation, not something deferred to expert reports. LPR 122 then requires production of a copy of every identified item not already in the file history, and LPR 124 permits amendment only by court order on a timely showing of good cause.

Running in parallel, 35 U.S.C. § 315(b) bars an inter partes review filed more than one year after the petitioner is served with an infringement complaint. Between a 45-day contention clock and a 12-month statutory bar, the searching has to start immediately — and the same evidence base should be built once and used in both forums.

How PerspireIP builds a Seattle invalidity record

We begin with element-by-element claim construction mapping, then search patent and non-patent literature in parallel — standards archives, conference proceedings, repositories, mailing lists, product documentation and archived web material — targeting the systems vocabulary the claims are really written in rather than the terms the drafter chose.

• Claim charts mapping every limitation to the reference text, figure or code passage
• A public-accessibility memo for each key NPL reference, with the date evidence attached
• Corroboration strategy: independent copies, archive declarations, and witnesses worth approaching
• Grounds split between PTAB-eligible printed publications and district-court system art
• Deliverables timed to LPR 121 contentions and the § 315(b) filing bar

Every patent invalidation Seattle engagement is run alongside your litigation counsel and under strict confidentiality. We do the exhaustive searching and the date-proving groundwork; your team does the advocacy. The deliverable is a record built to withstand the printed-publication fight, not a list of promising hits that collapses the first time a patent owner asks when the reference actually became public.

Whether you are an accused infringer in the Western District of Washington, a petitioner preparing an IPR against a cloud or e-commerce patent, or counsel assessing exposure before a complaint arrives, we scale from a single-patent search to a portfolio-wide campaign.

IP Landscape & Resources in Seattle

Key intellectual-property authorities and venues relevant to Seattle:

• United States Patent and Trademark Office (USPTO) — grants the patents at issue and publishes the MPEP guidance on printed publications as prior art
• Patent Trial and Appeal Board (PTAB) — decides inter partes review, limited by 35 U.S.C. § 311(b) to patents and printed publications
• U.S. District Court, Western District of Washington — the Seattle patent venue; its Local Patent Rules set the invalidity-contention timetable
• U.S. Court of Appeals for the Federal Circuit — sets the public-accessibility standard governing non-patent-literature prior art

Request a Patent Invalidation Search in Seattle

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

Frequently Asked Questions