Walker Digital, LLC Patent litigation record

Company 12 cases

12 cases on record naming Walker Digital, LLC: 12 as claimant, 0 as respondent. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

12 cases on record

Cases on record
12
As claimant
12
As respondent
0
Patents held
Not recorded
Core tech
Not recorded
Case no.PartiesRoleCourtFiledDurationOutcome
1:11-cv-00989 Walker Digital, LLC v. Google, Inc. Plaintiff D. Del. 18 Oct 2011 1177 d Likely Settlement
1:11-cv-00990 Walker Digital, LLC v. Amazon.com, Inc. Plaintiff D. Del. 18 Oct 2011 1178 d Likely Settlement
1:11-cv-00993 Walker Digital, LLC v. Vibrant Media, Inc. Plaintiff D. Del. 18 Oct 2011 1177 d Likely Settlement
1:11-cv-00696 Walker Digital, LLC v. Microsoft, Corp. Plaintiff D. Del. 8 Aug 2011 1257 d Likely Settlement
1:11-cv-00369 Walker Digital, LLC v. Google, Inc. Plaintiff D. Del. 26 Apr 2011 1592 d Likely Settlement
1:11-cv-00368 Walker Digital, LLC v. 2K Games, Inc. Plaintiff D. Del. 25 Apr 2011 1473 d Likely Settlement
1:11-cv-00362 Walker Digital, LLC v. Amazon.com, Inc. Plaintiff D. Del. 22 Apr 2011 1434 d Likely Settlement
1:11-cv-00326 Walker Digital, LLC v. Casio America, Inc. Plaintiff D. Del. 12 Apr 2011 2732 d Likely Settlement
1:11-cv-00309 Walker Digital, LLC v. Apple, Inc. Plaintiff D. Del. 11 Apr 2011 1417 d Procedural Outcome
1:11-cv-00318 Walker Digital, LLC v. MySpace, Inc. Plaintiff D. Del. 11 Apr 2011 1823 d Likely Settlement
1:11-cv-00320 Walker Digital, LLC v. American Airlines, Inc. Plaintiff D. Del. 11 Apr 2011 1418 d Likely Settlement
1:11-cv-00321 Walker Digital, LLC v. Ayre Acoustics, Inc. Plaintiff D. Del. 11 Apr 2011 1414 d Likely Settlement
Source: Patsnap Litigation Data. Cases naming Walker Digital, LLC in the current snapshot. Run this in Eureka
Patsnap Eureka

See what Walker Digital 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.