throbber

`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`___________________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`__________________________
`
`
`MEDTRONIC, INC. AND MEDTRONIC VASCULAR, INC.
`
`Petitioners,
`
`v.
`
`TELEFLEX INNOVATIONS S.À.R.L.,
`
`Patent Owner
`_____________________________
`
`Cases IPR2019-0135, IPR2019-0136
`U.S. Patent No. RE45,776
`______________________________
`
`PETITIONERS’ EXPLANATION OF MATERIAL DIFFERENCES
`BETWEEN PETITIONS AND PETITION RANKING FOR
`U.S. PATENT NO. RE45,776
`
`

`

`Medtronic, Inc. and Medtronic Vascular, Inc. (“Petitioners”) filed concurrent
`
`inter partes review (“IPR”) petitions against U.S. Pat. No. RE45,776 (“the ’776
`
`Patent;” Ex-1001), but the claims are split so only two petitions challenge a given
`
`claim. The Board should consider and institute both petitions.
`
`1. Two petitions are necessary because of a priority date dispute.
`
`The Board’s Trial Practice Guide states that “more than one petition may be
`
`necessary” where, as here, “there is a dispute about priority date requiring
`
`arguments under multiple prior art references.” TPG UPDATE (July 2019) at 26.
`
`Petitioner filed two petitions per claim for this exact reason, as outlined below.
`
`Itou-Based Petition
`Ground 1: Claims 25-27, 29-33, 35-37, 41-45, and 47-49 as
`Petition 1
`IPR2019-0135
`anticipated by U.S. Patent No. 7,736,355 (“Itou”)
`
`Ground 2: Claims 39 and 46 as obvious over Itou in view of
`the knowledge of a POSITA
`
`Ground 3: Claims 36-37 and 52-56 as obvious over Itou in
`view of U.S. Pat. App. 2005/0015073 (“Kataishi”) and/or the
`knowledge of a POSITA
`
`Ground 4: Claims 32, 36-38, 46, 52-56 as obvious over Itou
`in view of U.S. Patent No. 7,604,612 (“Ressemann”) and/or
`the knowledge of a POSITA
`
`Ground 5: Claims 52-56 as obvious over Itou in view of U.S.
`Patent No. 5,980,486 (“Enger”) and/or the knowledge of a
`POSITA
`
`
`1
`
`
`
`
`
`
`
`

`

`Kontos-Based Petition
`Ground 1: Claims 25-27, 29, 33, 35-37, 39, 41-49, and 52 as
`Petition 2
`IPR2019-0136
`obvious over U.S. Patent No. 5,439,445 (“Kontos”),
`Ressemann and/or the knowledge of a POSITA
`
`
`Ground 2: Claims 30-32 and 53-56 as obvious over Kontos,
`Ressemann, Takahasi et al., New Method to Increase a
`Backup Support of a 6 French Guiding Coronary Catheter
`(“Takahashi”) and/or the knowledge of a POSITA
`
`Ground 3: Claim 52 as obvious over Kontos, Ressemann,
`Kataishi, and/or the knowledge of a POSITA
`
`Ground 4: Claims 53-56 as obvious over Kontos in view of
`Ressemann, Takahashi, Kataishi, and/or the knowledge of a
`POSITA
`
`Petition 1 asserts Itou as a primary reference. Itou has an effective filing date
`
`
`
`
`of September 23, 2005. (Ex-1007.) But Patent Owner has alleged a conception and
`
`reduction to practice date in 2004—a date much earlier than the priority date on the
`
`face of the ’776 Patent.1 (Ex-1084; Ex-1001.) Petitioners therefore submitted a
`
`second Petition (Petition 2) that covers a similar set of claims as Petition 1 but
`
`asserts prior art references with priority dates before 2004. This second petition
`
`(Petition 2) relies on Kontos as a primary reference. Kontos issued on August 8,
`
`1995, and it is prior art under at least § 102(b). (Ex-1009.) Patent Owner is not able
`
`to swear behind Kontos, as it may attempt to do for Itou in Petition 1.
`
`
`1 The ʼ776 Patent claims priority to U.S. Pat. No. 8,292,850, which, on its face, is
`
`entitled to a priority date of May 3, 2006. (Ex-1001.)
`
`
`
`2
`
`

`

`
`
`The Board’s decision in Microsoft Corp. v. IPA Technologies, Inc. is
`
`instructive. IPR2019-00810, Paper 12 (PTAB Oct. 16, 2019). There, as here, the
`
`patent owner raised a priority date issue necessitating “arguments under multiple
`
`prior art references.” Id. at 15. In Microsoft Corp. the priority date dispute
`
`concerned a single prior art reference. Here, the priority dispute is more
`
`fundamental—Patent Owner has raised a priority date issue regarding the
`
`challenged patent itself. It would be manifestly unfair and prejudicial to Petitioner
`
`if the Board exercises its discretion under § 314(a) to deny Petition 2 and
`
`post-institution Patent Owner successfully swears behind Itou. Accordingly, the
`
`Board should consider and institute Petition 1 and Petition 2.
`
`2. Two petitions are necessary because of the length and number of
`claims asserted by Patent Owner in district court.
`
`
`The ’776 Patent has 32 lengthy claims. The challenged independent
`
`claims—claims 25, 52, and 53—consist of a combined 424 words. Mere recitation
`
`of the challenged claims in Petitions 1 and 2 takes up over 1200 words.
`
`Given Patent Owner’s allegations in district court, Petitioners must also
`
`challenge substantially all claims of the ’776 Patent. The Board’s Trial Practice
`
`Guide states that “more than one petition may be necessary” where, as here, “the
`
`patent owner has asserted a large number of claims in litigation.” TPG UPDATE
`
`(July 2019) at 26. In the district court litigation, Patent Owner has refused to
`
`identify the specific claims—or a specific number of claims—it will assert against
`
`
`
`3
`
`

`

`Petitioner. (Ex-1079 ¶ 71 (“Medtronic has infringed and continues to infringe one
`
`or more claims of the ’776 patent, including at least claims 25, 36, and 37…;” see
`
`also Ex-1083 at 2 (¶ 5d).)
`
`The Board’s decision in Microsoft Corp. is again instructive. There, as here,
`
`“word count limitations and a large number of challenged claims” supported the
`
`filing of multiple petitions. IPR2019-00810, Paper 9 at 14. In Microsoft Corp., the
`
`patent owner generally alleged infringement of “one or more claims” of the subject
`
`patent. Id. at 1 (“The complaint identified only claim 61, while generally alleging
`
`that Petitioner infringed ‘one or more claims.’”) The patent owner also opposed the
`
`streamlining of disputed issues, rejecting petitioner’s proposal to consider a set of
`
`twenty-four exemplary claims. Id. at 13.
`
`Here, too, Petitioner cannot reasonably fit its arguments into a single
`
`petition. Petitioner cannot reasonably fit both its Itou-based and Kontos-based
`
`arguments into a single petition—both of which are necessary, as outlined above—
`
`because of Patent Owner’s position regarding its alleged conception and reduction
`
`to practice date. And Patent Owner has rejected reasonable proposals to narrow the
`
`parties’ dispute (See Ex-1083 at 2 (¶ 5d).)
`
`
`
`
`
`4
`
`

`

`3. The Board should consider and institute both petitions, beginning
`with Petition 1 and then Petition 2.
`For the reasons set forth above, Petitioners respectfully request consideration
`
`and institution of both Petition 1 and Petition 2. Petitioners request that the Board
`
`consider its petitions in the following order: Petition 1 (IPR2019-0135), followed
`
`by Petition 2 (IPR2019-0136).
`
`
`
`RESPECTFULLY SUBMITTED,
`
`ROBINS KAPLAN LLP
`
`
`Date: November 14, 2019
`800 LaSalle Ave, Suite 2800
`Minneapolis, MN 55402
`612.349.8500
`
`
`
`
`/ Cyrus A. Morton /
`Cyrus A. Morton
`
`Attorney for Petitioner
`Medtronic, Inc.
`
`
`
`
`
`5
`
`

`

`CERTIFICATE OF SERVICE
`
`The undersigned certifies that PETITIONERS’ EXPLANATION OF
`
`
`
`
`MATERIAL DIFFERENCES BETWEEN PETITIONS AND PETITION
`
`RANKING FOR U.S. PATENT NO. RE45,776 was served on November 14, 2019,
`
`by Federal Express mail to the USPTO correspondence address of record listed
`
`below:
`
`
`
`Paul Onderick
`PATTERSON THUENTE PEDERSEN, P.A.
`80 South 8th Street
`4800 IDS Center
`Minneapolis, MN 55402-2100
`
`Courtesy copies were also sent to the following address of record for counsel
`
`in Vascular Solutions LLC, et al. v. Medtronic, Inc., et al., No. 19-cv-01760 (D.
`
`Minn., filed July 2, 2019):
`
`CARLSON, CASPERS, VANDENBURGH & LINDQUIST, P.A.
`225 South Sixth Street, Suite 4200
`Minneapolis, MN 55402
`
`/ Cyrus A. Morton /
`
`Cyrus A. Morton
`Registration No. 44,954
`Robins Kaplan LLP
`cmorton@robinskaplan.com
`
`Attorney for Petitioners
`
`6
`
`
`
`
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket