Last updated: July 14, 2026
Executive summary
Uniloc 2017 LLC v. Google LLC (No. 2:18-cv-00550, E.D. Texas) is part of Uniloc’s ongoing campaign targeting Google-related software products for alleged patent infringement. The case is linked to Uniloc’s broader “licensee demand” strategy and has repeatedly produced early-stage invalidity and pleading attacks in other Uniloc matters, centered on whether the asserted patent claims are directed to patent-ineligible subject matter and whether infringement allegations meet Rule 8 and plausibility standards.
This entry cannot be completed because the docket disposition, asserted patent numbers, claim constructions, dispositive motions outcomes, and final judgment or settlement terms are not provided here.
Litigation summary for Uniloc 2017 LLC v. Google LLC | 2:18-cv-00550
What courts decided (procedural posture)
No case-specific procedural outcomes are available in the provided input: there is no docket history, no order list, no schedule, and no final disposition referenced.
What patents were asserted?
No asserted patent numbers, publication numbers, or claim sets are included in the input.
What products and theories were alleged?
No accused Google products, infringement theories (system, method, or computer-readable medium), or software feature mappings are included in the input.
What were the key defenses?
No defense grounds are included in the input, such as:
- invalidity under 35 U.S.C. §§ 101, 102, 103, or 112
- unenforceability (inequitable conduct, prosecution history issues)
- noninfringement and lack of plausible pleading
- exhaustion, implied license, or other affirmative defenses
Why is Uniloc suing Google in this case? (strategy and patterns)
How Uniloc’s litigation posture typically works
Uniloc’s cases often focus on broadly framed infringement theories around software-related licensing or digital-device identification concepts. In these matters, defendants commonly challenge:
- claim eligibility (Section 101)
- sufficiency of infringement contentions and pleading specificity
- novelty of the “core concept” versus prior art
- whether the patents claim abstract ideas implemented on generic computers
No case-specific correspondence to this docket is provided in the input, so no mapping from general Uniloc patterns to this exact matter is supportable.
How strong are the patents in this Uniloc v. Google fight?
Patent strength drivers (what determines outcomes)
In software patent cases, outcomes typically hinge on:
- Section 101 eligibility of the asserted claims
- construction of claim terms related to system components or method steps
- whether novelty survives prior-art invalidity attacks
- whether accused functionality is actually present in the accused products
The input does not identify asserted claims or claim language, so no claim-by-claim strength analysis can be produced.
What is the litigation timeline for 2:18-cv-00550?
Timeline
No dates (complaint filing, amended pleadings, motion to dismiss, Markman, trial date, dispositive rulings, or settlement/voluntary dismissal) are present in the input, so a timeline cannot be reliably constructed.
Key docket milestones typically tracked
- Complaint filed
- Amended complaint(s)
- Initial disclosures and infringement contentions
- Motion to dismiss / Rule 12(c)
- Invalidity motions
- Claim construction (Markman)
- Summary judgment
- Trial and final judgment
- Stipulations or settlement terms
None of these milestones are provided for this case in the input.
What motions mattered most in Uniloc 2017 LLC v. Google LLC?
Featured snippets (likely motion themes)
No motion captions or orders are provided for this docket. As a result:
- the identity of decided issues
- the reasoning used by the court
- the exact claim scope affected by rulings
cannot be stated.
What does the case mean for generic or competitive risk?
Commercial exposure channels
Software patent litigations can affect product roadmaps through:
- injunction risk
- licensing costs or settlement leverage
- integration timelines
- feature redesign or implementation changes
No asserted patents, product mapping, or final outcome are included in the input, so this analysis cannot be tied to concrete exposure.
What settlement or injunction risks exist?
Injunction likelihood depends on outcomes
Infringement determinations, claim eligibility, and claim constructions drive injunction posture. The input lacks:
- final claim findings
- jury verdicts or bench findings
- any permanent injunction record
So no injunction risk assessment can be made for this specific docket.
Key takeaways
- The input identifies the case caption and docket number only.
- A litigation summary and analysis requires case-specific facts: asserted patents, accused products, motion outcomes, and final disposition.
- Those elements are not provided, so this entry cannot produce an accurate, complete litigation analysis for No. 2:18-cv-00550.
FAQs
What patents were asserted in Uniloc 2017 LLC v. Google LLC?
No asserted patent information is included in the provided input.
Did Uniloc 2017 LLC win any dispositive motions in 2:18-cv-00550?
No docket rulings are included in the provided input.
Was this case dismissed, settled, or tried?
No disposition facts are included in the provided input.
What Google products were accused in this matter?
No accused products are included in the provided input.
How can I find the latest status of case 2:18-cv-00550?
No source or docket link is included in the provided input.
References
- None.
