throbber

`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`__________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`__________
`
`
`RUIZ FOOD PRODUCTS, INC.,
`
`Petitioner,
`
`v.
`
`MACROPOINT LLC,
`
`Patent Owner.
`
`__________
`
`Case IPR2017-02018
`U.S. Patent No. 9,429,659
`__________
`
`
`PATENT OWNER’S REPLY BRIEF
`IN SUPPORT OF MOTION TO DISMISS
`
`
`
`

`

`
`
`UPDATED LIST OF EXHIBITS
`
`
`
`2004
`
`2005
`
`Exhibit No. Description
`2001
`Expert Declaration of David Hilliard Williams
`2002
`David Hilliard Williams CV
`2003
`“What are the differences in the technical specifications in the
`1988 automatic onboard recording device (AOBRD) Rule (49
`CFR 395.15) and the Electronic Logging Device (ELD) rule?”,
`https://www.fmcsa.dot.gov/faq/what-are-differences-specs-1988-
`aobrd-rule-and-eld-rule
`“ELD MANDATE: UPDATES, VIOLATION INFORMATION
`AND DEVICE INTRODUCTION PRICING & REVIEWS
`DRIVERS
`NEED
`TO
`KNOW,”
`https://unitedworldtransportation.com/eld-mandate-updates-
`violation-information-device-introduction-pricing-reviews-
`drivers-need-know/
`“Automatic On-Board Recording Devices (AOBRDs) Hand-
`Held, Commercial Vehicle Safety Alliance, June 6, 2012,
`http://www.ct.gov/dmv/lib/dmv/cv_bulletins/2012-05-automatic-
`on-board-recording-devices-aobrds-hand-held-created-06-06-
`12.pdf
`“Small Hardware Device Provides GPS Fleet Tracking
`Capabilities,”
`Fleet
`Financials, October
`14,
`2010,
`https://www.fleetfinancials.com/72619/small-hardware-device-
`provides-gps-fleet-tracking-capabilities
`“A Look at the Geotab GO Device: Past, Present, and Future,”
`Malene
`Johansen & Vincent Zhu,
`June 22, 2015,
`https://www.geotab.com/blog/geotab-go-device-past-present-
`future/
`“Announcing Geotab GO5 Premium Vehicle Tracking Device,”
`April 5, 2011, https://www.geotab.com/press-release/u-blox/
`“FMCSA Implementation of MAP-21,” Federal Motor Carrier
`Safety
`Administration,
`September
`28,
`2012,
`https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/FMCS
`A%20Implementation%20of%20MAP-21-%20Overview-
`
`2006
`
`2007
`
`2008
`
`2009
`
` i
`
`

`

`
`
`
`
`
`
`2010
`
`Exhibit No. Description
`Agenda-Qs%209-28-12.pdf
`“The Future of Electronic On-board Recording Devices in the
`U.S.,” Michael Goldberg, July 3, 2011, https://www.frg-
`law.com/blog/the-future-of-electronic-on-board-recording-
`devices-in-the-u-s/
`Declaration of Kyle B Fleming, Esq.
`
`2011
`
`2012
`
`2013
`
`Kyle B. Fleming CV
`
`Complaint filed in FourKites, Inc. v MacroPoint, LLC,
`Case No. 1:16-cv-02703-CAB (N.D. Ohio)
`
` ii
`
`

`

`
`
`
`
`Petitioner’s Opposition (“Opp.”) advances irrelevant differences and
`
`unpersuasive arguments to ignore the holding and principles of Click-to-Call. The
`
`Federal Circuit found the plain language of § 315(b) to clearly and unambiguously
`
`express Congress’ intent that no dismissal exception exists. The plain language of
`
`§ 315(a) is equally clear and unambiguous, and the petition should be dismissed.
`
`I.
`
`The Federal Circuit’s Statements, Framework, And Conclusions From
`Click-To-Call Are Equally Applicable To § 315(a) And Petitioner Fails
`To Manufacture Any Material Distinction
`
`Petitioner first suggests that Click-to-Call’s silence on § 315(a) is a tacit
`
`affirmance that there is a dismissal exception to § 315(a). Opp. at 5. But the
`
`Federal Circuit did not address § 315(a) because it was not at issue, and the “case
`
`or controversy” requirement forbids advisory opinions on legal questions not
`
`actually in dispute. U.S. Const. art. III, § 2, cl. 1; Muskrat v. United States, 219
`
`U.S. 346, 356 (1911). Suggesting that the Federal Circuit “could have” ruled on
`
`§315(a) is constitutionally improper; therefore the lack of an advisory opinion
`
`cannot be twisted into an implicit approval of Petitioner’s § 315(a) position.
`
`Second is Petitioner’s unremarkable observation that the Federal Circuit’s
`
`decision on § 315(b) relied on the language of § 315(b) not (a). Opp. at 5-7. But
`
`“serving” versus “filing” is a difference without distinction. These are different
`
`events, but this difference has no substantive impact on the Federal Circuit’s
`
`holding, which has equal force and veracity if the language of § 315(a) is inserted:
`
` 1
`
`

`

`
`
`
`
`The statute does not contain any exceptions or exemptions for
`complaints served [filed] in civil actions that are subsequently
`dismissed, with or without prejudice.… Simply put, § 315(b)’s
`[§315(a)’s] time bar is implicated once a party receives notice through
`official delivery of a complaint in a civil action [files a civil action
`challenging the validity of a claim], irrespective of subsequent events.
`
`899 F.3d at 1330 (modification added). There is no dismissal exception anywhere
`
`in § 315, and no subsequent event undoes any act—service or filing—once it has
`
`occurred. Section 315(a) is no different from (b) on this decisive factor.
`
`Third, Petitioner argues the “dismissal” exception nevertheless should be
`
`applied because § 315(a) is a “preclusion” provision whereas § 315(b) is a statute
`
`of limitation. Opp. at 7-9. This is a false dichotomy because the result of the two
`
`provisions is the same—petitioner cannot seek an IPR. If § 315(a) is “preclusive,”
`
`then so is § 315(b)—and that was irrelevant in Click-to-Call. In any event, neither
`
`provision is “preclusive” because neither triggers any claim or issue preclusion.
`
`New Hampshire v. Maine, 532 U.S. 742, 748 (2001) (claim preclusion forecloses
`
`“successive litigation of the very same claim” regardless of the issues); Taylor v.
`
`Sturgell, 553 U.S. 880, 892 (2008) (issue preclusion forecloses successive
`
`litigation of the very same issues regardless of the claim).
`
`After dismissing its declaratory judgment action, FourKites retained its
`
`ability to sue MacroPoint again on the same claims and on the same issues—
`
`declaratory judgment of patent invalidity. That FourKites and Ruiz cannot file a
`
` 2
`
`

`

`
`
`
`different claim before a different tribunal is not legal preclusion because they are
`
`free assert the same claims and raise the same issues in another district court
`
`action. The lack of § 315 standing bars an IPR filing, but this is not the preclusion
`
`discussed by Judge Taranto or by Jet. Opp. at 7-8. Applying Click-to-Call to §
`
`315(a) is consistent with Judge Taranto’s assertion that “[t]he point of a dismissal
`
`‘without prejudice’ is to preserve, rather than eliminate, the ability of the plaintiff
`
`to sue the defendant again on the same claim.” 899 F.3d at 1348 (emphasis added).
`
`Petitioner is simply repackaging the Bonneville/Graves argument expressly
`
`rejected by Click-to-Call (and Judge Taranto). This is confirmed by Petitioner’s
`
`reliance on Clio USA, Opp. at 8, which itself was predicated on an application of
`
`Bonneville/Graves that was rejected by the Federal Circuit in Click-to-Call.
`
`II. Chevron Applies Because The Board Must Also Give Effect To The
`Unambiguously Expressed Intent Of Congress
`
`Contrary to Petitioner’s argument, Opp. at 9-10, the Chevron framework is
`
`appropriate because the step one analysis applies to courts and agencies:
`
`If the intent of Congress is clear, that is the end of the matter; for the
`court, as well as the agency, must give effect to the unambiguously
`expressed intent of Congress. Chevron, U.S.A., Inc. v. Nat. Res. Def.
`Council, Inc., 467 U.S. 837, 842–43 (1984) (emphasis added).
`
`Petitioner fastidiously ignores the plain language of the statute and never provides
`
`any analysis of the express intent of Congress based on the language of § 315(a).
`
`Petitioner simply posits that Click-to-Call does not apply and then advances
`
` 3
`
`

`

`
`
`
`various policy arguments unsupported by the statute. But policy considerations
`
`(step two) are irrelevant when, as here, the statutory language is unambiguous.
`
`Click-to-Call, 899 F.3d at 1332 (inquiry ends if step one answers the question).
`
`III. Petitioner’s Argument, Opp. At 10-12, That Congress Enacted § 315(a)
`With An Expectation That The Dismissal Exception Would Apply Is
`Unsupported By Any Evidence Or Legal Basis
`
`First, the cited Board decisions came after Congress enacted § 315(a)—
`
`therefore Congress could not have had any expectation vis-à-vis these decisions.
`
`Second, if Congress enacted § 315 based on some understanding of “background
`
`legal principles” concerning dismissals, it would have applied to § 315(b) too—but
`
`this is rejected by Click-to-Call. Third, all of the Board decisions cited by
`
`Petitioner—Gordon, Cyanotech, Tristar and Emerson—are predicated on the now
`
`discredited reading of the Graves and/or Bonneville decisions.
`
`IV. The Board Should Decline Petitioner’s Invitation, Opp. At 12-13, To
`Graft A New “Might Have Lacked Jurisdiction” Exception To § 315(a)
`Because It Is Not Supported By The Statute
`
`The plain language of § 315 does not disclose or suggest such an exception.
`
`Congress expressly and unambiguously chose “filing”—not some other event—as
`
`the trigger under § 315(a), and there is no valid basis to graft this exception to the
`
`unambiguous expression of Congressional intent. InVue’s underlying case was
`
`dismissed for lack subject matter jurisdiction. FourKites was not, so whether there
`
`might be an exception for lack of subject matter jurisdiction is not at issue here.
`
` 4
`
`

`

`
`
`
`V. A Declaratory Judgement Action Is Not A Counterclaim
`
`A counterclaim is a claim brought in an existing action by a claim-defendant
`
`against a claim-plaintiff, and a separate lawsuit is not a counterclaim to another
`
`action. See Fed. R. Civ. P. 13; Canfield Scientific, Inc. v. Melanoscan, LLC,
`
`IPR2017-02125, Paper No. 15 at 3-7 (PTAB Mar. 30, 2018). Subsection (a)(3)
`
`expressly addresses counterclaims, so Congress knew the difference and, had it
`
`wanted to treat some declaratory judgment actions as counterclaims, it could have
`
`done so. It did not, and that is the end of the inquiry.
`
`VI. Waiver Does Not Apply Because Standing/Jurisdiction Can Be Raised
`At Any Time During The Proceedings
`
`“After institution, standing issues may still be raised during the trial. A
`
`patent owner may seek authority from the Board to take pertinent discovery or to
`
`file a motion to challenge the petitioner’s standing.” See 77 Fed. Reg. 48680,
`
`48695, comment 8. This is consistent with the rule that subject matter jurisdiction
`
`cannot be assumed or waived. Arbaugh v. Y&H Corp., 546 U.S. 500, 514 (2006).
`
`Because § 315 is considered jurisdictional, it is not waivable. 899 F.3d at 1325.
`
`The failure to raise a futile defense is not a waiver if there is a subsequent
`
`change in the law. See In re Micron Tech., Inc., 875 F.3d 1091, 1096 (Fed. Cir.
`
`2017) (no waiver in view of TC Heartland decision changing venue law). Prior to
`
`Click-to-Call, Board precedent found a dismissal exception to § 315(a).
`
` 5
`
`

`

`Date: October 17, 2018
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
` /Mark C. Johnson/
`Mark C. Johnson, Reg. No. 51,854
`Kyle B. Fleming (admitted pro hac vice)
`Luis A. Carrion, Reg. No. 61,255
`Renner Otto
`1621 Euclid Avenue, Floor 19
`Cleveland, Ohio 44115
`t: +1.216.621.1113
`f: +1.216.621.6165
`
`Attorneys for Patent Owner
`MacroPoint, LLC
`
`

`

`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that the above-captioned PATENT OWNER’S
`REPLY BRIEF IN SUPPORT OF MOTION TO DISMISS is being served in its
`entirety on this date by filing this document through the Patent Review Processing
`System as well as delivering a copy via electronic mail upon the following at:
`
`
`James P. Murphy jpmurphy@polsinelli.com
`
`Matt Frontz mfrontz@polsinelli.com
`
`Ryan Murphy rmurphy@polsinelli.com
`
`Date: October 17, 2018
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
` /Mark C. Johnson/
`Mark C. Johnson, Reg. No. 51,854
`Renner Otto
`1621 Euclid Avenue, Floor 19
`Cleveland, Ohio 44115
`t: +1.216.621.1113
`f: +1.216.621.6165
`
`Attorneys for Patent Owner
`MacroPoint, LLC
`
`
`
`

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