Dataquill Limited Patent litigation record

Company 11 cases

11 cases on record naming Dataquill Limited: 11 as claimant, 0 as respondent. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

11 cases on record

Cases on record
11
As claimant
11
As respondent
0
Patents held
Not recorded
Core tech
G06K7/10 · G06K17/00 · G06F3/06 · G06K7/00 · H04M1/00
Case no.PartiesRoleCourtFiledDurationOutcome
1:22-cv-00610 Dataquill, Ltd. v. Amazon.com, Inc. Plaintiff D. Del. 6 May 2022 377 d Consent Judgment
1:21-cv-01438 Dataquill, Ltd. v. Google, LLC Plaintiff D. Del. 8 Oct 2021 396 d Consent Judgment
1:21-cv-00883 Dataquill Limited v. T-Mobile US, Inc. Plaintiff D. Del. 21 Jun 2021 133 d Voluntary dismissal
1:21-cv-22275 DataQuill Limited v. Simply, Inc. Plaintiff S.D. Fla. 21 Jun 2021 113 d Voluntary dismissal
1:20-cv-20760 Dataquill Limited v. Blu Products, Inc. Plaintiff S.D. Fla. 21 Feb 2020 270 d Stayed
6:20-cv-00017 Dataquill Limited v. Acer America Corporation Plaintiff W.D. Tex. 10 Jan 2020 97 d Voluntary dismissal
2:19-cv-00280 Dataquill Limited v. Asustek Computer, Inc. Plaintiff E.D. Tex. 14 Aug 2019 317 d Voluntary dismissal
2:19-cv-00281 Dataquill Limited v. Coolpad Technologies, Inc. Plaintiff E.D. Tex. 14 Aug 2019 216 d Voluntary dismissal
2:19-cv-03394 Dataquill Limited v. TCL Communication Technology Holdings Limited Plaintiff C.D. Cal. 26 Apr 2019 753 d Voluntary dismissal
2:13-cv-00633 Dataquill Limited v. Huawei Technologies Co., Ltd. Plaintiff E.D. Tex. 16 Aug 2013 887 d Likely Settlement
2:13-cv-00634 Dataquill Limited v. ZTE Corporation Plaintiff E.D. Tex. 16 Aug 2013 887 d Likely Settlement
Source: Patsnap Litigation Data. Cases naming Dataquill Limited in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Dataquill is protecting

Portfolio, claim scope and where its coverage is thin. Every answer cites the records behind it.

Analyse this portfolio
10,000 free credits to start

About this summary. This page summarises the litigation records within the coverage and snapshot dates stated here. Counts describe records in that dataset and do not, by themselves, establish the conduct, litigation success or legal position of any person or organisation.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.