throbber
Case 1:19-cv-11586-IT Document 40 Filed 02/03/20 Page 1 of 5
`
`UNITED STATES DISTRICT COURT
`DISTRICT OF MASSACHUSETTS
`
`PHILIPS NORTH AMERICA LLC
`
`Plaintiff,
`
`
`
`v.
`
`FITBIT, INC.,
`
`Defendant.
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`C.A. No. 1:19-cv-11586-IT
`
`JURY TRIAL DEMANDED
`
`PLAINTIFF’S MOTION FOR LEAVE TO FILE A SUR-REPLY IN OPPOSITION
`TO DEFENDANT’S MOTION TO DISMISS
`
`Plaintiff Philips North America, LLC (“Philips”) respectfully requests leave to file the
`
`brief proposed Sur-Reply Brief attached as Exhibit 1 in response to the Reply brief filed by
`
`Defendant in support of its Motion to Dismiss (Dkt. 39). Philips’s proposed Sur-Reply is six
`
`pages in length, and is limited to addressing new arguments and issues raised in Defendant’s
`
`Reply that should have been raised in Plaintiff’s original Motion and that Philips has not had an
`
`opportunity to address. For example, and by Defendant’s own admission, much of its Reply
`
`brief is focused on addressing the allegations made in Philips’s Amended Complaint—which
`
`Defendant obviously had well before filing its motion. In particular the proposed Sur-Reply
`
`addresses two specific items:
`
`1. Fitbit’s (legally incorrect) Reply argument that the detailed pleadings in Philips’
`
`complaint should be ignored and only the patent considered for the purposes of
`
`evaluating the claims under 35 U.S.C. §101. (See Dkt. 39) This argument is directly
`
`contradicted by recent Federal Circuit case law. To make it, Fitbit relies on cases
`
`

`

`Case 1:19-cv-11586-IT Document 40 Filed 02/03/20 Page 2 of 5
`
`where implausible pleadings contradicted the language of a patent—not the issue
`
`here.
`
`2. The Supreme Court’s recent denial of certiorari in several cases addressing 35 U.S.C.
`
`§101. Without explanation, Fitbit’s Reply characterizes those decisions as “rejecting
`
`the same types of arguments that Philips raises” in its opposition. But in fact, the
`
`opposite is true—even though one of those denied petitions (Cellspin) was filed by
`
`Fitbit.
`
`Where a Reply brief arguably raises new arguments, a Sur-Reply is appropriate. See e.g.
`
`Klein v. MHM Correctional Services, Inc., No. 08-11814-MLW, 2010 WL 3245291, *2 (D.
`
`Mass Aug. 16, 2010). This is especially so where the Reply arguments could have (and should
`
`have) been raised in the original motion, as is the case with Fitbit’s criticism of the facts alleged
`
`in Philips’s Amended Complaint.
`
`The Court has not scheduled a hearing on Defendant’s Motion and no party will be
`
`prejudiced by the Court granting leave to file the proposed limited Sur-Reply.
`
`2
`
`

`

`Case 1:19-cv-11586-IT Document 40 Filed 02/03/20 Page 3 of 5
`
`LOCAL RULE 7.1(a)(2) CERTIFICATE
`
`The undersigned counsel certify that they have conferred with counsel for Defendant, and
`
`that Defendant does not consent to the relief requested in this motion
`
`3
`
`

`

`Case 1:19-cv-11586-IT Document 40 Filed 02/03/20 Page 4 of 5
`
`Dated: February 3, 2020
`
`Respectfully Submitted,
`
` /s/ Ruben J. Rodrigues
`Lucas I. Silva (BBO 673,935)
`FOLEY & LARDNER LLP
`111 Huntington Avenue
`Boston, MA 02199
`Phone: (617) 342-4000
`Fax: (617) 342-4001
`lsilva@foley.com
`
`Eley O. Thompson (pro hac vice)
`FOLEY & LARDNER LLP
`321 N. Clark Street
`Suite 2800
`Chicago, IL 60654-5313
`Phone: (312) 832-4359
`Fax: (312) 832-4700
`ethompson@foley.com
`
`
`
`
`
`
`
`
`Counsel for Philips North America LLC
`
`4
`
`

`

`Case 1:19-cv-11586-IT Document 40 Filed 02/03/20 Page 5 of 5
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that, on February 3, 2020, a copy of the foregoing
`
`document was filed with the Court through the ECF system and that a copy will be electronically
`
`served on registered participants as identified on the Notice of Electronic Filing.
`
`By:
`
` /s/ Ruben J. Rodrigues
`
`5
`
`

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