Printed Circuits & Assemblies and Semiconductor Devices Patent litigation record

Technology 8 cases

8 cases on record in Printed Circuits & Assemblies and Semiconductor Devices. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

8 cases on record

Cases on record
8
Classification
H05K1/18 · H05K3/46 · H01L25/10 · H01L25/00 · H01L23/00 · H01L23/552 · H01L23/538 · H01L21/48 · H01L23/13 · H01L23/29 · H01L23/544 · H05K1/02 · H05K3/28 · H01L21/56 · H10W74/01 · H01L21/52 · H01L23/08 · H01L21/60 · H01L23/055 · H05K1/00 · H10W76/153 · H10W76/18 · H05K1/16 · H01L23/498 · H01L23/48 · H05K5/00 · H05K7/00 · H04N5/225 · H01L21/4763
Courts involved
N.D. Cal. · E.D. Tex. · W.D. Tex. · S.D. Tex. · D. Del. · S.D.N.Y.
Case no.PartiesCourtFiledDurationOutcome
3:25-cv-02206 Imberatek, LLC v. Apple Computer, Inc. N.D. Cal. 4 Mar 2025 63 d Dismissed with Prejudice
4:24-cv-00937 Bell Semiconductor, LLC v. Cisco Systems, Inc. E.D. Tex. 18 Oct 2024 27 d Dismissed with Prejudice
1:24-cv-00129 Imberatek, LLC v. Apple, Inc. W.D. Tex. 5 Feb 2024 392 d Case Transferred
4:23-cv-00974 Bell Semiconductor, LLC v. Juniper Networks, Inc. E.D. Tex. 31 Oct 2023 84 d Voluntary dismissal
4:22-cv-03440 KT Imaging USA, LLC v. Zhejiang Dahua Technology Co., Ltd. S.D. Tex. 6 Oct 2022 428 d Dismissed with Prejudice
6:22-cv-01026 KT Imaging USA, LLC v. Hangzhou Hikvision Digitial Technology Co., Ltd. W.D. Tex. 3 Oct 2022 450 d Dismissed with Prejudice
1:22-cv-01292 Bell Semiconductor, LLC v. Micron Technology, Inc. D. Del. 30 Sep 2022 123 d Voluntary dismissal
1:22-cv-08248 KT Imaging USA, LLC v. Fujifilm Holdings, Corp. S.D.N.Y. 27 Sep 2022 141 d Case Settled
Source: Patsnap Litigation Data. Cases classified under Printed Circuits & Assemblies and Semiconductor Devices. Run this in Eureka
Patsnap Eureka

Where the claim space is crowded

Which patents are asserted most in this field, and which branches are still open.

Map this field
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.