US7086747B2 Patent litigation record

Patent 11 cases

US7086747B2 has been asserted in 11 cases on record. 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
Asserted by
Blackbird Tech
Asserted against
Espen Technology · Hyperikon · EiKO Global · RemPhos Technologies · Halco Lighting Technologies · Innoled Lighting · Axlen · ETi Solid State Lighting · LEDwholesalers.com · 3NLED Lighting USA
Courts
C.D. Cal. · D. Del.
Technology
lighting device components
Case no.PartiesCourtFiledDurationOutcome
2:19-cv-07622 Blackbird Tech, LLC v. Espen Technology, Inc. C.D. Cal. 3 Sep 2019 72 d Voluntary dismissal
1:16-cv-00966 Blackbird Tech, LLC v. Hyperikon, Inc. D. Del. 19 Oct 2016 128 d Voluntary dismissal
1:16-cv-00967 Blackbird Tech, LLC v. EiKO Global, LLC D. Del. 19 Oct 2016 145 d Likely Settlement
1:16-cv-00968 Blackbird Tech, LLC v. RemPhos Technologies, LLC D. Del. 19 Oct 2016 99 d Voluntary dismissal
1:16-cv-00971 Blackbird Tech, LLC v. Halco Lighting Technologies, LLC D. Del. 19 Oct 2016 145 d Likely Settlement
1:16-cv-00972 Blackbird Tech, LLC v. Innoled Lighting, Inc. D. Del. 19 Oct 2016 107 d Likely Settlement
1:16-cv-00973 Blackbird Tech, LLC v. Espen Technology, Inc. D. Del. 19 Oct 2016 1049 d Case Transferred
1:15-cv-00055 Blackbird Tech, LLC v. Axlen, Inc. D. Del. 20 Jan 2015 336 d Other
1:15-cv-00057 Blackbird Tech, LLC v. ETi Solid State Lighting, Inc. D. Del. 20 Jan 2015 1494 d Likely Settlement
1:15-cv-00060 Blackbird Tech, LLC v. LEDwholesalers.com, Inc. D. Del. 20 Jan 2015 694 d Likely Settlement
1:15-cv-00063 Blackbird Tech, LLC v. 3NLED Lighting USA, Inc. D. Del. 20 Jan 2015 566 d Other
Source: Patsnap Litigation Data. Cases asserting US7086747B2 in the current snapshot. Run this in Eureka
Patsnap Eureka

How strong is US7086747B2?

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.