US8199747B2 Patent litigation record

Patent 12 cases

US8199747B2 has been asserted in 12 cases on record. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

12 cases on record

Cases on record
12
Asserted by
Uniloc 2017 · Uniloc USA · Uniloc
Asserted against
Samsung Electronics America · Hike · Huawei Device USA · Vonage · AOL · Green Tomato · Tencent America · Snap · Kakao · Viber Media, SARL · Voxernet
Courts
Fed. Cir. · E.D. Tex.
Technology
digital information transmission
Case no.PartiesCourtFiledDurationOutcome
2019-2168 Uniloc 2017, LLC v. Samsung Electronics America, Inc. Fed. Cir. 23 Jul 2019 219 d Closed
2:17-cv-00476 Uniloc USA, Inc. v. Hike, Ltd. E.D. Tex. 6 Jun 2017 681 d Voluntary dismissal
2:17-cv-00349 Uniloc USA, Inc. v. Hike, Ltd. E.D. Tex. 21 Apr 2017 721 d Likely Settlement
2:16-cv-00994 Uniloc USA, Inc. v. Huawei Device USA, Inc. E.D. Tex. 6 Sep 2016 1030 d Voluntary dismissal
2:16-cv-00893 Uniloc USA, Inc. v. Vonage Holdings, Corp. E.D. Tex. 11 Aug 2016 98 d Voluntary dismissal
2:16-cv-00722 Uniloc USA, Inc. v. AOL, Inc. E.D. Tex. 5 Jul 2016 398 d Likely Settlement
2:16-cv-00731 Uniloc USA, Inc. v. Green Tomato Limited E.D. Tex. 5 Jul 2016 1017 d Voluntary dismissal
2:16-cv-00694 Uniloc USA, Inc. v. Tencent America, LLC E.D. Tex. 30 Jun 2016 354 d Out-of-court Settlement
2:16-cv-00696 Uniloc, Corp. v. Snap, Inc. E.D. Tex. 30 Jun 2016 2568 d Dismissed with Prejudice
2:16-cv-00640 Uniloc USA, Inc. v. Kakao Corporation E.D. Tex. 14 Jun 2016 276 d Likely Settlement
2:16-cv-00643 Uniloc USA, Inc. v. Viber Media, SARL E.D. Tex. 14 Jun 2016 219 d Likely Settlement
2:16-cv-00644 Uniloc USA, Inc. v. Voxernet, LLC E.D. Tex. 14 Jun 2016 197 d Likely Settlement
Source: Patsnap Litigation Data. Cases asserting US8199747B2 in the current snapshot. Run this in Eureka
Patsnap Eureka

How strong is US8199747B2?

Closest prior art, compared claim by claim, with every reference rated for how hard it hits.

Run a novelty search
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.