Advantech Corporation Patent litigation record

Company 11 cases

11 cases on record naming Advantech Corporation: 0 as claimant, 11 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
0
As respondent
11
Patents held
Not recorded
Core tech
Not recorded
Case no.PartiesRoleCourtFiledDurationOutcome
6:23-cv-00882 Acqis, LLC v. Advantech Co., Ltd. Defendant W.D. Tex. 22 Dec 2023 602 d Dismissed with Prejudice
6:23-cv-00723 Unwired Global Systems, LLC v. Advantech Co., Ltd. Defendant W.D. Tex. 19 Oct 2023 580 d Voluntary dismissal
6:22-cv-00059 Cedar Lane Technologies, Inc. v. Advantech Co., Ltd. Defendant W.D. Tex. 17 Jan 2022 175 d Voluntary dismissal
6:21-cv-01331 American Patents, LLC v. Advantech Co., Ltd. Defendant W.D. Tex. 21 Dec 2021 136 d Voluntary dismissal
1:21-cv-00209 Harmony Licensing, LLC v. Advantech Corporation Defendant S.D. Ohio 29 Mar 2021 254 d Voluntary dismissal
3:20-cv-03789 JSDQ Mesh Technologies, LLC v. Advantech Corporation Defendant N.D. Cal. 9 Jun 2020 135 d Voluntary dismissal
3:20-cv-02964 Aperture Net, LLC v. Advantech Corporation Defendant N.D. Cal. 30 Apr 2020 109 d Closed
3:19-cv-07190 Magnacross, LLC v. Advantech Corporation Defendant N.D. Cal. 31 Oct 2019 193 d Voluntary dismissal
4:19-cv-01596 Altair Logix, LLC v. Advantech Corporation Defendant N.D. Cal. 27 Mar 2019 238 d Voluntary dismissal
2:19-cv-00061 Longhorn HD, LLC v. Advantech Corporation Defendant E.D. Tex. 25 Feb 2019 315 d Likely Settlement
6:15-cv-00619 Chrimar Systems, Inc. v. Advantech Corporation Defendant E.D. Tex. 1 Jul 2015 356 d Likely Settlement
Source: Patsnap Litigation Data. Cases naming Advantech Corporation in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Advantech 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.