throbber
Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 1 of 14
`
`
`
`UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF MASSACHUSETTS
`
`
`PHILIPS NORTH AMERICA LLC,
`
`v.
`
`FITBIT, INC.,
`
`Plaintiff,
`
`Defendant.
`
`Civil Action No. 1:19-cv-11586-FDS
`
`
`PLAINTIFF’S OPPOSITION TO DEFENDANT’S MOTION
`CONCERNING THE CONSTRUCTION OF “SERVER” CLAIM
`TERMS (DKT. 275.)
`
`
`
`
`
`

`

`
`
`I. 
`
`II. 
`
`III. 
`
`IV. 
`
`
`
`
`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 2 of 14
`
`TABLE OF CONTENTS
`
`INTRODUCTION ................................................................................................................... 1 
`
`FITBIT’S MANUFACTURED CLAIM CONSTRUCTION ARGUMENTS VIOLATE
`MULTIPLE TENETS OF CLAIM CONSTRUCTION ......................................................... 2 
`
`FITBIT HAS BEEN INTIMATELY AWARE OF PHILIPS’S INFRINGEMENT
`ARGUMENTS CONCERNING THE “SERVER” TERMS FOR NEARLY TWO YEARS 6 
`
`SUMMARY JUDGMENT BRIEFING WOULD BE THE MOST LOGICAL AND
`EFFICIENT WAY TO RESOLVE THE DISPUTE ............................................................... 8 
`
`
`
`i
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 3 of 14
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`
`
`Cases
`
`01 Communique Laboratory, Inc. v. LogMeIn, Inc.,
`687 F.3d 1292 (Fed. Cir. 2012)..............................................................................................4, 5
`
`Alfred E. Mann Found. For Sci. Research v. Cochlear Corp.,
`841 F.3d 1334 (Fed. Cir. 2016)..................................................................................................5
`
`Athenahealth, Inc. v. AdvancedMD Software, Inc.,
`11-11260-GAO, 2013 WL 6187145 (D. Mass. Nov. 26, 2013) ............................................5, 7
`
`Baldwin Graphic Sys., Inc. v. Siebert, Inc.,
`512 F.3d 1338 (Fed. Cir. 2008)..........................................................................................1, 3, 4
`
`Bd. of Regents of the U. of Texas System v. BENQ Am. Corp.,
`533 F.3d 1362 (Fed. Cir. 2008)..............................................................................................1, 3
`
`In re Body Sci. LLC Patent Litig.,
`167 F. Supp. 3d 152 (D. Mass. 2016) ........................................................................................9
`
`Ethicon Endo-Surgery, Inc. v. U.S. Surgical Corp.,
`93 F.3d 1572 (Fed. Cir. 1996)....................................................................................................3
`
`Fractus, S.A. v. ZTE Corp.,
`No. 3:18-CV-2838-K, 2019 WL 5267426 (N.D. Tex. Oct. 16, 2019) ..................................8, 9
`
`Long Hua Tech. Co., Ltd v. A123 Sys., LLC,
`CV 20-11887-RGS, 2021 WL 4122740 (D. Mass. Sept. 9, 2021) ............................................5
`
`MedIdea, L.L.C. v. DePuy Orthopaedics, Inc.,
`422 F. Supp. 3d 459 (D. Mass. 2019), aff'd, 833 Fed. Appx. 338 (Fed. Cir.
`2021)(unpublished) ................................................................................................................8, 9
`
`MicroStrategy Inc. v. Business Objects, S.A.,
`429 F.3d 1344 (Fed. Cir. 2005)..................................................................................................8
`
`Salazar v. Procter & Gamble Co.,
`414 F.3d 1342 (Fed. Cir. 2005)..................................................................................................5
`
`SiOnyx, LLC v. Hamamatsu Photonics K.K.,
`270 F. Supp. 3d 390 (D. Mass. 2017) (Saylor, J.) .....................................................................3
`
`Sorensen v. Int’l Trade Comm’n,
`427 F.3d 1375 (Fed. Cir. 2005)..................................................................................................5
`
`ii
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 4 of 14
`
`
`
`Wi-LAN USA, Inc. v. Apple Inc.,
`830 F.3d 1374 (Fed. Cir. 2016)..................................................................................................8
`
`
`
`
`
`iii
`
`

`

`
`
`I.
`
`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 5 of 14
`
`INTRODUCTION
`
`Plaintiff Philips North America LLC (“Philips”) respectfully submits this Opposition to
`
`Defendant Fitbit LLC’s (“Fitbit”) Motion for the Construction of Three Related Claim Terms (Dkt.
`
`275.) Philips opposes Fitbit’s efforts to insert additional claim construction briefing for the terms
`
`“a remote server,” “an internet server,” and “the server” (collectively, “the server terms”) in claim
`
`1 of U.S. Patent No. 8,277,377 (“the ’377 patent”) in view of the swiftly approaching deadline for
`
`dispositive motions.
`
`Philips agrees that when parties have a genuine dispute as to the meaning of a claim term,
`
`the Court must resolve it. However, Philips disagrees that there is any merit to Fitbit’s desperate
`
`and belated effort to avoid infringement with newly concocted claim construction theories.
`
`That the present dispute was manufactured and not genuine is demonstrated by the fact that
`
`Fitbit’s arguments violate multiple fundamental tenets of claim construction. Fitbit’s argument
`
`ignores that when a claim uses different words to describe different things, they should not be
`
`interpreted as necessarily referring to the same thing. (e.g. “a remote server” and “an internet
`
`server”). Bd. of Regents of the U. of Texas System v. BENQ Am. Corp., 533 F.3d 1362, 1371
`
`(Fed. Cir. 2008) (“Different claim terms are presumed to have different meanings.”). Fitbit’s
`
`argument also ignores that using “an indefinite article ‘a’ or ‘an’ in patent parlance carries the
`
`meaning of ‘one or more’ in open-ended claims containing the transitional phrase ‘comprising.’”
`
`Baldwin Graphic Sys., Inc. v. Siebert, Inc., 512 F.3d 1338, 1342 (Fed. Cir. 2008) (quoting KCJ
`
`Corp. v. Kinetic Concepts, Inc., 223 F.3d 1351, 1356 (Fed. Cir. 2000)).
`
`Fitbit’s purported justification for raising this issue so late in the case also suggest that this
`
`dispute was manufactured and not genuine. While Fitbit argues that Philips did not accuse multiple
`
`servers of infringing until the service of opening expert reports, the record unequivocally
`
`demonstrates the falsity of that assertion. The reality is that Fitbit has been on notice of Philips’s
`
`1
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 6 of 14
`
`
`
`infringement theories since the service of infringement contentions about two years ago—in which
`
`Philips alleged infringement by users downloading the Fitbit App from Google or Apple’s servers.
`
`What is more, Fitbit’s own opening expert report—served at the same time as Dr. Martin’s opening
`
`report—confirms that Fitbit was aware of Philips’s contention since it addressed the issue before
`
`receiving Philips’s expert report on infringement. (Dkt. 261-3 at ¶ 1030.) Indeed, Fitbit’s
`
`attempt to argue indefiniteness based on Philips’s infringement contention that reads “a remote
`
`server” and “an internet server” on different things is one of the items at issue in Philips’s Motion
`
`to Strike portions of Dr. Paradiso’s expert report. (Dkt. 260 at 14-17 of 19.)1
`
`Regardless of the lack of merit in Fitbit’s manufactured claim construction argument, to
`
`the extent Fitbit contends that the dispute is salient to non-infringement and invalidity, the proper
`
`time to raise it at this stage would be in upcoming dispositive motions, which are due in less than
`
`six weeks on March 2, 2022. There is no reasoned basis to derail the schedule or complicate the
`
`proceedings with an additional round of claim construction. Accordingly, Fitbit’s motion
`
`requesting a supplemental round of claim construction should be denied because the parties have
`
`the opportunity to address disputed terms in their dispositive motions under the schedule entered
`
`by the Court.
`
`II.
`
`FITBIT’S MANUFACTURED CLAIM CONSTRUCTION ARGUMENTS
`VIOLATE MULTIPLE TENETS OF CLAIM CONSTRUCTION
`
`Claim 1’s language clearly can cover multiple servers and Fitbit’s argument to the contrary
`
`violates multiple tenets of claim construction. Specifically, the server referred to in limitation 1(a)
`
`(“downloading an application . . . from a remote server”) does not have to be the same server
`
`referred to in limitation 1(g) (“sending the exercise-related information to an internet server”) as
`
`they are referred to with open ended articles (“a remote server” and “an internet server”). The
`
`
`1 For clarity, the pincites to pages in filed documents refer to the page numbers in the ECF header.
`
`2
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 7 of 14
`
`
`
`server referred to twice in limitation 1(h)2 (with the definite article “the”) refers to the same server
`
`that immediately preceding limitation 1(g) referred to as it involves that server performing a
`
`calculation based on the exercise-related information that was sent to the server in limitation 1(g).
`
`Thus, the claim language itself refers to at least two servers by different names – a “remote server”
`
`and an “internet server.”
`
`Fitbit’s position is contrary to the well-established principle that different words in a claim
`
`have different meanings and as such “remote server” and “internet server” do not have the same
`
`meaning. BENQ Am. Corp., 533 F.3d 1362 at 1371. (“The fact that the claim distinguishes
`
`between ‘each pre-programmed code’ and ‘the matched one or more pre-programmed codes’ is
`
`significant. Different claim terms are presumed to have different meanings.”); Ethicon Endo-
`
`Surgery, Inc. v. U.S. Surgical Corp., 93 F.3d 1572, 1579 (Fed. Cir. 1996) (reversing lower court’s
`
`ruling that a “pusher assembly” and a “pusher bar” have the same meaning); SiOnyx, LLC v.
`
`Hamamatsu Photonics K.K., 270 F. Supp. 3d 390, 405 (D. Mass. 2017) (Saylor, J.) (“There is a
`
`presumption in claim construction that different terms have different meanings. From that
`
`presumption, it follows that the patentee intended a different meaning by the term ‘height,’ [], than
`
`the term ‘protrude above the semiconductor surface,’ . . .”) (citing CAE Screenplates Inc. v.
`
`Heinrich Fiedler GmbH & Co., 224 F.3d 1308, 1317 (Fed. Cir. 2000)).
`
`Fitbit’s rationale for requesting that the Court construe the server terms also violates a well
`
`settled rule that “a” remote server or “an” internet server means there is only one remote server or
`
`one internet server. The Federal Circuit “has repeatedly emphasized that an indefinite article ‘a’
`
`or ‘an’ in patent parlance carries the meaning of ‘one or more’ in open-ended claims containing
`
`the transitional phrase ‘comprising.’” Baldwin Graphic, 512 F.3d at 1342. “That ‘a’ or ‘an’ can
`
`
`2 “receiving a calculated response from the server, the response associated with a calculation performed by the server
`based on the exercise-related information” ’377 patent, claim 1, limitation (h).
`
`3
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 8 of 14
`
`
`
`mean ‘one or more’ is best described as a rule, rather than merely as a presumption or even a
`
`convention.” Id. (emphasis added); 01 Communique Laboratory, Inc. v. LogMeIn, Inc., 687 F.3d
`
`1292, 1297 (Fed. Cir. 2012) (“As a general rule, the words ‘a’ or ‘an’ in a patent claim carry the
`
`meaning of ‘one or more.’”) (internal quotations and citations omitted). Further, Fitbit’s
`
`proposition that the use of the word “the” is indicative that the server in limitation 1(h) must be
`
`the same physical server in limitation 1(g) also goes against the Federal Circuit’s rule as the
`
`“subsequent use of definite articles ‘the’ or ‘said’ in a claim to refer back to the same claim term
`
`does not change the general plural rule, but simply reinvokes that non-singular meaning.” Baldwin
`
`Graphic, 512 F.3d at 1342.
`
`While there are exceptions to this rule, none of those are present here. There is no evidence
`
`that the patentee clearly intended to limit “a remote server” or “an internet server” to only one
`
`server of either category. Baldwin Graphic, 512 F.3d at 1342-1343 (“The exceptions to this rule
`
`are extremely limited: a patentee must ‘evince[ ] a clear intent” to limit ‘a’ or ‘an’ to “one.’ …. An
`
`exception to the general rule that “a” or “an” means more than one only arises where the language
`
`of the claims themselves, the specification, or the prosecution history necessitate a departure from
`
`the rule.”). Fitbit attempts to invoke this exception by pointing to Figures in the ’377 patent and
`
`the drawing in the provisional application as having only one box showing a server, however, the
`
`Federal Circuit has dismissed such arguments as failing to compel “departure for the general rule.”
`
`01 Communique Laboratory, 687 F.3d 1292 at 1297 (“However, the fact that a locator server
`
`computer is represented by a single box in some of the figures does not ‘necessitate’ a departure
`
`from the general rule that ‘a’ locator server computer may mean ‘one or more’ locator server
`
`computers.”). As is the case here, where the specification clearly states that one or more servers
`
`4
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 9 of 14
`
`
`
`may be used,3 the Federal Circuit found such disclosure as support that the general rule applied.
`
`01 Communique Laboratory, 687 F.3d at 1297. (“More to the point, the specification also discloses
`
`expressly that ‘Server Computer 12 may comprise one or more computers, as is well known.’”).
`
`Courts in this district have likewise applied this rule. See Long Hua Tech. Co., Ltd v. A123
`
`Sys., LLC, CV 20-11887-RGS, 2021 WL 4122740, at *5 (D. Mass. Sept. 9, 2021) (construing a
`
`battery comprised of “a” current collector substrate and “an” electrode layer on one surface of
`
`“the” current collector substrate” as “a lithium battery that uses more than one current collector
`
`substrate and has an electrode layer on one surface of at least one of those current collector
`
`substrates.); Athenahealth, Inc. v. AdvancedMD Software, Inc., 11-11260-GAO, 2013 WL
`
`6187145, at *2 (D. Mass. Nov. 26, 2013) (construing “a medical practice management server” as
`
`“one or more servers that perform functions…..” and “a payor server” as “one of more servers
`
`used by a specific payor….”).
`
`Fitbit does not provide evidence to overcome the rule either by its statements regarding the
`
`prosecution history where Fitbit simply refers to statements made by the examiner. (Dkt. 276 at
`
`13 of 17.) However, “an examiner’s unilateral statement does not give rise to a clear disavowal of
`
`claim scope by the applicant.” Alfred E. Mann Found. For Sci. Research v. Cochlear Corp., 841
`
`F.3d 1334, 1341 (Fed. Cir. 2016); see also Salazar v. Procter & Gamble Co., 414 F.3d 1342, 1347
`
`(Fed. Cir. 2005) (“This court refuses to create a rule or presumption that the applicant in this case
`
`disavowed claim scope by silence”); Sorensen v. Int’l Trade Comm’n, 427 F.3d 1375, 1378-79
`
`
`3 “It should also be noted that each of application 62, algorithm 63, external data source 74, or AI
`system 76, may physically reside on more than one server, e.g., on an array of servers for, e.g.,
`storage or multiple processing purposes. Each of application 62, algorithm 63, external data source
`74, or AI system 76, or combinations of each, may also respectively reside on different servers.”
`’377 patent at 8:45-51 (emphasis added); Fig. 4.
`
`
`5
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 10 of 14
`
`
`
`(Fed. Cir. 2005) (“[I]t is the applicant, not the examiner, who must give up or disclaim subject
`
`matter that would otherwise fall within the scope of claims.”).
`
`III. FITBIT HAS BEEN INTIMATELY AWARE OF PHILIPS’S
`INFRINGEMENT ARGUMENTS CONCERNING THE “SERVER”
`TERMS FOR NEARLY TWO YEARS
`
`Fitbit’s claim of surprise regarding Philips infringement allegations regarding what servers
`
`are referred to in the claim rings hollow. Philips’s allegation regarding the servers in claim 1 has
`
`been consistent and disclosed to Fitbit since at least May 2020. (Dkt.. 261-5.) Fitbit’s dismissive
`
`statement that the contentions were simply excerpts of “various screenshots” suggests that the
`
`screenshots contained no information about the servers Philips identified as meeting the various
`
`limitations. This is simply incorrect, as shown below “a remote server” is identified as the Apple
`
`or Google app stores where the Fitbit app can be accessed and downloaded, and the pertinent
`
`language from the screen shot was identified by being enclosed in a red rectangle. Philips did not
`
`leave Fitbit in the dark as to its theory regarding the term “a remote server.”
`
`
`
`6
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 11 of 14
`
`
`
`(Id. at 3 of 27.) Of course, even were Philips’s contentions not as clear as they actually are, Fitbit
`
`of course knows that users download the Fitbit App from Google and Apple—there was no
`
`“surprise.”
`
`Likewise, for “an internet server” in limitation 1(g) and “the server” in limitation 1(h), the
`
`screen shots clearly identify how the internet server term is met by Fitbit’s servers and are enclosed
`
`by a red rectangle. Nothing regarding Philips’s interpretation of the server terms was hidden or
`
`“concealed” from Fitbit.
`
`(Id. at 17 of 27.)
`
`(Id. at 20 of 27.)
`
`7
`
`
`
`
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 12 of 14
`
`
`
`Further, Fitbit’s own expert admits in his opening report, (served the same day as
`
`Philips’s expert’s opening report), that Philips’s infringement contentions identified that the server
`
`in limitation 1(a) was a server that the application was downloaded from, and the server that the
`
`exercise data was uploaded to and from which a calculated response was sent for limitations 1(g)
`
`and 1(h) were Fitbit servers. (Dkt. 261-03 at ¶ 1030.) It is absurd to allege that Philips somehow
`
`“concealed” its infringement allegations when Fitbit’s own expert accordingly responded to them.
`
`At bottom, there is no surprise, other than Fitbit’s failure to raise the issue until now. Fitbit
`
`argues that because Fitbit put forth its position in its non-infringement interrogatory (which is yet
`
`another admission that it was not actually “surprised” by Philips’s allegations), yet it did nothing
`
`to advance its argument during claim construction perhaps recognizing the lack of merit in
`
`advancing arguments so plainly at odds with basic principles of claim construction.
`
`IV.
`
`SUMMARY JUDGMENT BRIEFING WOULD BE THE MOST LOGICAL
`AND EFFICIENT WAY TO RESOLVE THE DISPUTE
`
`Courts regularly entertain claim construction disputes at summary judgment. MedIdea,
`
`L.L.C. v. DePuy Orthopaedics, Inc., 422 F. Supp. 3d 459, 460 (D. Mass. 2019), aff'd, 833 Fed.
`
`Appx. 338 (Fed. Cir. 2021)(unpublished) (claim construction dispute was raised in the defendant’s
`
`summary judgment motion); see also, Wi-LAN USA, Inc. v. Apple Inc., 830 F.3d 1374, 1380–81
`
`(Fed. Cir. 2016) (applying the “traditional claim construction framework to this review even
`
`though the district court reached these constructions on summary judgment and reconsideration of
`
`summary judgment rather than in the phase of the case specifically dedicated to claim
`
`construction.”); MicroStrategy Inc. v. Business Objects, S.A., 429 F.3d 1344, 1350 (Fed. Cir. 2005)
`
`(noting district court construed a limitation that was necessary to decide summary judgment
`
`motion); Fractus, S.A. v. ZTE Corp., No. 3:18-CV-2838-K, 2019 WL 5267426, at *6 (N.D. Tex.
`
`Oct. 16, 2019) (issuing a clarification of the claim term disputed during claim construction).
`
`8
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 13 of 14
`
`
`
`While Fitbit relies on MedIdea for the proposition that post-Markman claim construction
`
`is appropriate, (Dkt. 276 at 9 of 17), as noted above the MedIdea court addressed the parties’ claim
`
`construction dispute raised during summary judgment. Further, the case, In re Body Sci. LLC
`
`Patent Litig., that Fitbit relies on is distinguishable, because, as Fitbit notes, this Court addressed
`
`a claim construction dispute that “arose during expert discovery.” (Id. citing In re Body Sci. LLC
`
`Patent Litig., 167 F. Supp. 3d 152, 155-157 (D. Mass. 2016)). However, as set forth above, Fitbit
`
`was on notice of Philips’s position on the server terms well before expert discovery, and should
`
`not be allowed to further delay these proceedings based on a manufactured and untimely dispute.
`
`The March 2, 2022 deadline for dispositive motions is swiftly approaching. Fitbit does not
`
`even suggest how its proposed extra claim construction briefing would co-exist with the Court’s
`
`current schedule. Nor does Fitbit address the confusion that would ensue if the parties proceeded
`
`with Fitbit’s proposed claim construction briefing in parallel with dispositive motions. Fitbit itself
`
`has declared the disputed server terms are material to infringement and invalidity theories that
`
`would be the very issues addressed in the parties’ summary judgment arguments. As such, Fitbit’s
`
`requested relief for an extra claim construction briefing cycle and hearing should be denied, and
`
`Fitbit can raise the issue in summary judgment if it so chooses.
`
`
`
`
`
`9
`
`

`

`Case 1:19-cv-11586-FDS Document 291 Filed 01/21/22 Page 14 of 14
`
`
`
`
`
`Dated: January 21, 2022
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully Submitted,
`
`
`
`
` /s/ Ruben J. Rodrigues
`Lucas I. Silva (BBO 673,935)
`Ruben J. Rodrigues (BBO 676,573)
`John Custer (BBO 705,258)
`FOLEY & LARDNER LLP
`111 Huntington Avenue
`Suite 2500
`Boston, MA 02199-7610
`Phone: (617) 342-4000
`Fax: (617) 342-4001
`lsilva@foley.com
`rrodrigues@foley.com
`jcuster@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 Plaintiff
`Philips North America LLC
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that 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
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`10
`
`

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