Lightside Technologies, LLC Patent litigation record

Company 10 cases

10 cases on record naming Lightside Technologies, LLC: 10 as claimant, 0 as respondent. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

10 cases on record

Cases on record
10
As claimant
10
As respondent
0
Patents held
Not recorded
Core tech
H04B1/66 · H04N7/01 · G11B27/031 · G11B27/034 · H04N5/85 · H04N5/222 · H04N5/44
Case no.PartiesRoleCourtFiledDurationOutcome
1:21-cv-20026 Lightside Technologies, LLC v. Curtis International, Ltd. Plaintiff S.D. Fla. 5 Jan 2021 42 d Stayed
2:20-cv-11055 Lightside Technologies, LLC v. Supersonic, Inc. Plaintiff C.D. Cal. 4 Dec 2020 38 d Voluntary dismissal
2:20-cv-08549 Lightside Technologies, LLC v. Sceptre, Inc. Plaintiff C.D. Cal. 17 Sep 2020 53 d Voluntary dismissal
3:20-cv-00725 Lightside Technologies LLC v. HTC Corporation Plaintiff N.D. Tex. 26 Mar 2020 309 d Voluntary dismissal
5:20-cv-00378 Lightside Technologies LLC v. Tinnovate, LLC Plaintiff C.D. Cal. 25 Feb 2020 142 d Case Settled
3:19-cv-02128 Lightside Technologies LLC v. ZTE Corporation Plaintiff N.D. Tex. 9 Sep 2019 165 d Voluntary dismissal
5:19-cv-01458 Lightside Technologies LLC v. TTE Technology, Inc. Plaintiff C.D. Cal. 6 Aug 2019 160 d Voluntary dismissal
1:18-cv-01268 Lightside Technologies, LLC v. Haier American Trading, LLC Plaintiff D. Del. 20 Aug 2018 112 d Voluntary dismissal
8:17-cv-01152 Lightside Technologies, LLC v. Vizio, Inc. Plaintiff C.D. Cal. 6 Jul 2017 53 d Stayed
2:16-cv-01250 Lightside Technologies, LLC v. Vizio, Inc. Plaintiff E.D. Tex. 9 Nov 2016 238 d Case Transferred
Source: Patsnap Litigation Data. Cases naming Lightside Technologies, LLC in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Lightside Technologies 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.