Litigation workflow from asserted patent to Ursa-backed report
A shareable PatentBear page showing the actual product flow for a recent asserted-patent matter: patent reader, patent-specific Ursa, global Ursa, Research, and report packaging.
Matter Snapshot
This is a workflow demo built around a live public-record example, not a legal opinion. The objective is to show how PatentBear can organize the research path a litigator would follow.
- Case
- Advanced Integrated Circuit Process LLC v. Taiwan Semiconductor Manufacturing Company Limited
- Court
- Eastern District of Texas, No. 2:25-cv-00324-JRG
- Filed
- April 1, 2025
- Worked patent
- U.S. Patent No. 7,632,751, Semiconductor device having via connecting between interconnects
- Why this case
- Recent semiconductor litigation with asserted patents, accused process technology, PTAB pressure, and live district-court motion practice.
PatentBear Flow Screenshots
Each section below uses a real PatentBear page capture and links back into the product flow.
Patent Reader
Start with the asserted patent. The reader keeps the abstract, claims, figures, metadata, and later analysis workspace in one view.
Open this step
Patent-Specific Ursa
Open the patent chat panel to ask focused questions against the claims, abstract, and specification with citation-aware answers.
Open this stepGlobal Ursa Chat
Use Ursa for matter intake, litigation triage, prior-art planning, and prompts that span more than one patent record.
Open this step
Research page
Route deeper work into Research when the question becomes a structured analysis: prior art, disclosure, clearance, or claim construction.
Open this step
Shareable Report Surface
Package the workflow into a report page that a litigator or client can review without opening the underlying docket files.
Open this step
What a litigator does with this flow
The screenshots are the interface layer. The work product behind them is the familiar patent-litigation sequence: docket triage, asserted-claim selection, infringement mapping, invalidity search, discovery, claim construction, and damages planning.
- 1Open the asserted patent and identify independent claims, figures, assignment history, and priority context.
- 2Ask patent-specific Ursa questions against the record, then inspect citations back in the reader.
- 3Use global Ursa to frame the matter: accused technology, prior-art search strings, and litigation questions.
- 4Move deeper workflows into Research when the analysis becomes structured and repeatable.
- 5Package the flow into a shareable report for internal review, client updates, or product demonstration.