Share This Page
Litigation Details for WSOU Investments LLC v. Google LLC (W.D. Tex. 2020)
✉ Email this page to a colleague
WSOU Investments LLC v. Google LLC (W.D. Tex. 2020)
| Docket | ⤷ Start Trial | Date Filed | 2020-06-29 |
| Court | District Court, W.D. Texas | Date Terminated | 2022-01-25 |
| Cause | 35:271 Patent Infringement | Assigned To | Alan D. Albright |
| Jury Demand | Both | Referred To | |
| Parties | AQUA LICENSING, LLC | ||
| Patents | 9,427,421 | ||
| Attorneys | Bradley David Liddle | ||
| Firms | Warren Lex LLP | ||
| Link to Docket | External link to docket | ||
Small Molecule Drugs cited in WSOU Investments LLC v. Google LLC
Details for WSOU Investments LLC v. Google LLC (W.D. Tex. 2020)
| Date Filed | Document No. | Description | Snippet | Link To Document |
|---|---|---|---|---|
| 2020-06-29 | External link to document | |||
| >Date Filed | >Document No. | >Description | >Snippet | >Link To Document |
ecutive summary
The docket WSOU Investments LLC v. Google LLC, 6:20-cv-00571 reflects a set of patent-infringement allegations by WSOU targeting Google products and services on asserted network and device-related technologies. The key business point for risk and timing is that the case sits in the pattern of WSOU’s ongoing litigation against large tech platforms, where outcomes typically hinge on claim construction, infringement proof tied to specific accused features, and how courts treat standard-essential-technology style arguments even when patents are not expressly SEPs.
WSOU Investments LLC v. Google LLC 6:20-cv-00571 litigation summary and analysis
This case is identified by the U.S. District Court docket number 6:20-cv-00571 in the Eastern District of Texas. It is a patent infringement action by WSOU Investments LLC against Google LLC (the accused instrumentality set in WSOU cases is usually disclosed in the complaint and claim charts, then narrowed through amended pleadings and court orders).
What patents does WSOU assert in WSOU v. Google 6:20-cv-00571?
Answer: The asserted patents and claims are defined in the complaint and any subsequent amended infringement contentions served under the court’s patent-local rules.
How to identify the asserted patent family and claim themes
- Asserted patents are typically filed in WSOU’s common technology areas across its tech-platform litigation portfolios.
- Each case’s asserted set can include continuation members and related priority families that allow the same technical theme to appear across multiple patent numbers.
- Litigation focus usually shifts from broad “system” allegations at pleading to narrower elements tied to specific accused features after claim construction.
Business relevance
- For licensing and design-around analysis, the operative step is mapping each asserted claim limitation to one or more accused Google features, then aligning that mapping to the product roadmap and deployment cadence.
What products and features does Google face under WSOU v. Google 6:20-cv-00571?
Answer: The accused instrumentalities are listed in the complaint and infringement contentions, and they typically correspond to one or more Google services that integrate networking, search, caching, indexing, or client-server communication workflows.
Where infringement usually turns
- Claim construction of functional limitations
- Proof that the accused products practice the claimed steps or system elements
- Whether accused features are implemented as a single system “as claimed” versus distributed across components in a way that defendants argue defeats “single-instrumentality” requirements
Design-around implications
- If infringement proof rests on client behavior or specific network communication patterns, a feasible design-around often targets those workflow steps rather than the broad service concept.
What is the procedural posture in 6:20-cv-00571 (motions, claim construction, trial dates)?
Answer: The docket timeline is determinative for exposure because WSOU’s cases often move through standard patent-case milestones: scheduling orders, Markman proceedings, summary-judgment motions, and dispositive orders or trial readiness.
Milestone mapping (what to track on the docket)
- Initial pleadings and service: complaint, answer, and any early motions to dismiss
- Patent-local deadlines: infringement contentions, invalidity contentions, claim construction proposals
- Markman / claim construction: the orders that usually drive settlement leverage
- Dispositive motions: summary judgment on infringement, invalidity, or lack of damages theories
- Trial or settlement posture: pretrial order and mediation references if present
Business relevance
- If the case is in the claim-construction or summary-judgment stage, near-term settlement leverage typically increases, and downside valuation for accused products typically reflects worst-case claim-scope readings.
What are the main legal arguments WSOU uses and how does Google typically respond?
Answer: In WSOU platform litigation, WSOU generally argues literal infringement or infringement under equivalents based on claim charts linking each limitation to accused functionality. Google typically responds with noninfringement, invalidity, and procedural defenses tied to claim scope and proof.
WSOU’s recurring infringement theories (case-type pattern)
- System claims: accused products constitute the claimed system elements
- Method claims: accused workflows implement steps as claimed
- Functional limitations: WSOU argues ordinary implementations satisfy “configured to” or “for” language
Google’s recurring defenses (case-type pattern)
- Noninfringement: distributed architecture, missing elements, or implementation differences
- Invalidity: anticipation/obviousness over prior art; sometimes indefiniteness attacks
- Designation issues: accused feature definitions not matching the asserted limitations
- Remedies: damages theories limited by proof, apportionment, and comparable royalty considerations
How strong is the patent estate for WSOU in this case?
Answer: Strength in this matter is best measured by how the court’s claim construction reads the asserted limitations and by whether those constructions preserve novelty over cited prior art references.
Strength indicators to extract from orders
- Whether claim terms receive narrowing constructions that align with the accused features
- Whether invalidity grounds survive summary judgment
- Whether WSOU’s asserted claims are differentiated by specific technological constraints rather than generic functionality
Business relevance
- For licensing decisions, the practical “strength” metric is whether the court’s claim constructions preserve claim elements that are actually present in accused Google implementations.
What claim construction outcomes matter most for infringement exposure?
Answer: The most business-relevant outcomes are constructions of:
- “configured to” and other functional language
- step sequencing limitations in method claims
- system “component” definitions that can require a single orchestrated system or a particular arrangement
- “using,” “receiving,” “transmitting,” or “storing” limitations tied to distributed architectures
Why constructions drive settlement
- If constructions narrow key limitations away from accused product behavior, WSOU’s infringement case weakens quickly.
- If constructions broaden or map cleanly onto accused features, the case shifts toward damages or licensing posture.
What validity and prior art challenges are typically asserted in WSOU tech-platform cases?
Answer: Google’s typical validity challenges include:
- anticipation by a single reference
- obviousness combinations
- indefiniteness where claim language is accused of lacking clear boundaries
What to track on the docket
- invalidity contention charts
- expert reports
- summary judgment rulings on prior art
- any postured relationship between the asserted family’s priority dates and the prior art effective dates
Does the case involve Paragraph IV-type challenges or other exclusivity issues?
Answer: No. This is a patent infringement matter between WSOU and Google over software and systems-related IP, not an FDA Hatch-Waxman Paragraph IV framework.
Is there a settlement, consent judgment, or dismissal in WSOU v. Google 6:20-cv-00571?
Answer: Docket disposition is the authoritative source for whether claims were settled, dismissed with or without prejudice, or stayed pending other matters.
What to look for
- “Joint dismissal” entries
- “Settlement” references and sealed agreement notices
- “Stipulated dismissal” after Markman or after dispositive motions
Business relevance
- Settlement often includes license scope, ongoing royalty terms, and covenants that can cap or eliminate future injunction risk, but only the final dismissal or order confirms the operational impact.
What injunction risk exists, and how do courts treat injunction requests in these cases?
Answer: Injunction exposure depends on:
- whether infringement and validity survive dispositive phases
- whether the patentee seeks injunctive relief and whether the court applies current injunction standards
- whether irreparable harm evidence is credited
Business relevance
- For platform companies, even a nonfinal infringement finding typically drives the commercial resolution strategy around licensing and portfolio cross-licenses.
How does this case compare with other WSOU v. tech-platform litigation?
Answer: The case fits WSOU’s broader pattern of filing against large consumer tech and internet platforms, using a consistent infringement framework with claim charts tied to accused system behaviors.
Comparison dimensions that matter
- asserted patent family overlap across cases
- venue and judge assignment patterns that affect claim-construction tendencies
- the accused feature set and whether the case turns on the same limitation types
- settlement timing relative to Markman and summary judgment
Commercial and strategic impact: what does WSOU v. Google 6:20-cv-00571 mean for product teams and licensing?
Answer: The operational impact is concentrated on:
- mapping accused features to claim elements under the court’s constructions
- assessing whether engineering changes can mitigate exposure without harming core product functionality
- licensing strategy if key claim elements align strongly with current implementations
Risk triage model for internal use (docket-driven)
- Early phase (pleading and contentions): risk is high-level; prioritize claim chart validation and invalidity discovery.
- Markman phase: risk becomes measurable once constructions issue.
- Post-Markman / summary judgment: risk converts to settlement probability and damages posture.
Key litigation timeline to extract from the docket
Answer: The timeline must be pulled from docket entries in 6:20-cv-00571 including filing date, amended complaints, claim construction dates, and dispositive motion dates.
What should appear in the docket event list
- Complaint filed and served
- Defendant response and any motions to dismiss
- Scheduling order and patent-local deadlines
- Markman hearing and claim construction order
- Expert deadlines
- Summary judgment motions and rulings
- Trial setting and any status changes
- Settlement dismissal or final judgment
Data table: docket-based items that determine exposure
| Exposure driver | What it changes | Why it matters |
|---|---|---|
| Claim construction order | Scope of claim terms | Determines whether accused Google features meet limitations |
| Infringement contentions / amended charts | Which features are alleged | Narrows the factual theory and helps estimate engineering design-around options |
| Invalidity contentions and prior art rulings | Viability of asserted claims | Controls whether litigation proceeds to damages or collapses early |
| Disposition (settlement/dismissal) | Ends or caps injunction risk | Converts litigation uncertainty into license scope and royalty exposure |
| Remedies posture | Damages ceiling and injunction probability | Drives commercial negotiation leverage |
What to monitor next
Answer: Monitor the docket for (1) claim construction outcomes, (2) dispositive motion rulings, and (3) any settlement or dismissal order entries that define the end state of claims in 6:20-cv-00571.
Key Takeaways
- WSOU Investments LLC v. Google LLC (6:20-cv-00571) is a patent infringement case whose leverage points are claim construction and validity/infringement survival through dispositive phases.
- The case outcome and commercial impact depend on how the court construes key claim limitations and whether those constructions map onto accused Google product features identified in contention sets.
- Settlement or dismissal entries on the docket are the definitive signal for final license scope, injunction risk, and residual exposure.
FAQs
1) What is the fastest way to assess infringement risk in WSOU v. Google?
Track the claim construction order and compare the construed limitations to the accused features listed in WSOU’s infringement contentions.
2) Do WSOU cases typically focus on literal infringement or equivalents?
WSOU typically pleads literal infringement and also asserts infringement under equivalents for limitations it argues are met in substantially the same way, with the viability of equivalents shaped by claim construction.
3) What happens to a case if key claims are narrowed at Markman?
Narrowing often forces WSOU to amend theories, limits the mapped features, and can increase the odds of dismissal or settlement.
4) How does prior art selection affect WSOU’s chances of surviving invalidity challenges?
Prior art that aligns closely with the constructed claim scope tends to be decisive in summary judgment; the effective dates and priority chain of the asserted patents also matter.
5) Can a settlement in WSOU v. Google affect other WSOU cases against the same defendant?
Often yes, through portfolio licensing dynamics and covenants, but only the settlement terms and any dismissal language define the operational reach.
References (APA)
- U.S. District Court, Eastern District of Texas. WSOU Investments LLC v. Google LLC, No. 6:20-cv-00571 (case docket).
More… ↓
