13 cases on record
- Cases on record
- 13
- Classification
- H04L12/413 · H04L29/06 · H04L12/407 · H04L12/56 · H04L49/90 · H03M13/09 · H03M13/00 · H04L12/66 · H04Q11/04 · H04L29/08
- Courts involved
- E.D. Tex.
| Case no. | Parties | Court | Filed | Duration | Outcome |
|---|---|---|---|---|---|
| 4:17-cv-00141 | Plectrum, LLC v. Oracle Corporation | E.D. Tex. | 24 Feb 2017 | 120 d | Likely Settlement |
| 4:17-cv-00120 | Plectrum, LLC v. AT&T, Inc. | E.D. Tex. | 20 Feb 2017 | 217 d | Likely Settlement |
| 4:17-cv-00121 | Plectrum, LLC v. Broadcom Corporation | E.D. Tex. | 20 Feb 2017 | 124 d | Likely Settlement |
| 4:17-cv-00123 | Plectrum, LLC v. Comcast Corporation | E.D. Tex. | 20 Feb 2017 | 221 d | Voluntary dismissal |
| 4:17-cv-00125 | Plectrum, LLC v. NEC Corporation of America | E.D. Tex. | 20 Feb 2017 | 124 d | Likely Settlement |
| 4:17-cv-00126 | Plectrum, LLC v. Verizon Communications, Inc. | E.D. Tex. | 20 Feb 2017 | 124 d | Likely Settlement |
| 4:17-cv-00081 | Plectrum, LLC v. Facebook, Inc. | E.D. Tex. | 3 Feb 2017 | 143 d | Likely Settlement |
| 4:17-cv-00082 | Plectrum, LLC v. Fortinet, Inc. | E.D. Tex. | 3 Feb 2017 | 224 d | Likely Settlement |
| 4:17-cv-00083 | Plectrum, LLC v. Huawei Technologies USA, Inc. | E.D. Tex. | 3 Feb 2017 | 143 d | Likely Settlement |
| 4:17-cv-00084 | Plectrum, LLC v. Juniper Networks, Inc. | E.D. Tex. | 3 Feb 2017 | 141 d | Likely Settlement |
| 4:17-cv-00077 | Plectrum, LLC v. Brocade Communications Systems, Inc. | E.D. Tex. | 2 Feb 2017 | 144 d | Likely Settlement |
| 4:17-cv-00078 | Plectrum, LLC v. Cisco Systems, Inc. | E.D. Tex. | 2 Feb 2017 | 26 d | Voluntary dismissal |
| 4:17-cv-00079 | Plectrum, LLC v. Extreme Networks, Inc. | E.D. Tex. | 2 Feb 2017 | 142 d | Likely Settlement |
Where the claim space is crowded
Which patents are asserted most in this field, and which branches are still open.
Map this field- 01Ranked prior artEvery hit source-linked
- 02Claim-level comparisonAgainst your own product
- 03Legal statusAcross 174 jurisdictions
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.
Report an incorrect record
Tell us what is wrong on this page. The page address is included automatically.
Privacy request
For requests about your personal information on this page. The page address is included automatically.