Cochlear Corporation Patent litigation record

Company 10 cases

10 cases on record naming Cochlear Corporation: 4 as claimant, 6 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
4
As respondent
6
Patents held
Not recorded
Core tech
A61B17/00 · A61C8/00 · A61B17/86 · H04R25/00 · A61N1/375 · A61N1/08 · A61N1/378 · A61N1/37 · H04H7/00 · A61B17/56
Case no.PartiesRoleCourtFiledDurationOutcome
2021-1448 Oticon Medical LLC v. Cochlear Limited Defendant Fed. Cir. 22 Dec 2020 49 d Closed
20-362 Cochlear Corporation v. Alfred E. Mann Foundation For Scientific Research Plaintiff U.S. Supreme Court 17 Sep 2020 88 d Appeal Denied
1:19-cv-10303 Cochlear, Ltd. v. MED-EL Corporation Plaintiff D. Mass. 18 Feb 2019 147 d Procedural Outcome
2019-1201 Alfred E. Mann Foundation For Scientific Research v. Cochlear Corporation Defendant Fed. Cir. 14 Nov 2018 488 d Closed
1:17-cv-00660 Cochlear, Ltd. v. Oticon Medical, AB Plaintiff D. Colo. 13 Mar 2017 282 d Likely Settlement
1:16-cv-01700 Cochlear, Ltd. v. Oticon Medical, AB Plaintiff D. Colo. 1 Jul 2016 451 d Stayed
2015-1606 Alfred E. Mann Foundation For Scientific Research v. Cochlear Corporation Defendant Fed. Cir. 30 Apr 2015 567 d Closed
2015-1607 Alfred E. Mann Foundation For Scientific Research v. Cochlear Corporation Defendant Fed. Cir. 30 Apr 2015 567 d Closed
2015-1580 Alfred E. Mann Foundation For Scientific Research v. Cochlear Corporation Defendant Fed. Cir. 22 Apr 2015 575 d Closed
2:07-cv-08108 Alfred E. Mann Foundation For Scientific Research v. Cochlear Corporation Defendant C.D. Cal. 13 Dec 2007 3984 d Judgment on the Merits
Source: Patsnap Litigation Data. Cases naming Cochlear Corporation in the current snapshot. Run this in Eureka
Patsnap Eureka

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