Cobblestone Wireless, LLC Patent litigation record

Company 10 cases

10 cases on record naming Cobblestone Wireless, 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
H04J1/00 · H04B7/00 · H04W24/02 · H04L5/00
Case no.PartiesRoleCourtFiledDurationOutcome
1:24-cv-08726 Cobblestone Wireless, LLC v. Motorola Mobility, Inc. Plaintiff N.D. Ill. 20 Sep 2024 271 d Case Dismissed
2:23-cv-00454 Cobblestone Wireless, LLC v. Cisco Systems, Inc. Plaintiff E.D. Tex. 29 Sep 2023 612 d Case Dismissed
2:23-cv-00455 Cobblestone Wireless, LLC v. Commscope Holding Company, Inc. Plaintiff E.D. Tex. 29 Sep 2023 915 d Case Dismissed
2:23-cv-00457 Cobblestone Wireless, LLC v. Hewlett-Parkard, Co. Plaintiff E.D. Tex. 29 Sep 2023 612 d Case Dismissed
2:23-cv-00380 Cobblestone Wireless, LLC v. AT&T Services, Inc. Plaintiff E.D. Tex. 25 Aug 2023 420 d Dismissed with Prejudice
2:23-cv-00381 Cobblestone Wireless, LLC v. T-Mobile Plaintiff E.D. Tex. 25 Aug 2023 420 d Dismissed with Prejudice
2:23-cv-00382 Cobblestone Wireless, LLC v. Cellco Partnership, (dba Verizon Wireless) Plaintiff E.D. Tex. 25 Aug 2023 420 d Dismissed with Prejudice
2:23-cv-00285 Cobblestone Wireless, LLC v. Samsung Electronics Co., Ltd. Plaintiff E.D. Tex. 16 Jun 2023 482 d Case Dismissed
2:22-cv-00477 Cobblestone Wireless, LLC v. T-Mobile Plaintiff E.D. Tex. 16 Dec 2022 672 d Case Dismissed
2:22-cv-00478 Cobblestone Wireless, LLC v. Verizon Communications, Inc. Plaintiff E.D. Tex. 16 Dec 2022 672 d Case Dismissed
Source: Patsnap Litigation Data. Cases naming Cobblestone Wireless, LLC in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Cobblestone Wireless 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.