throbber
Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 1 of 16
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`
`FLYPSI, INC. (D/B/A FLYP),
`
` Plaintiff,
`
` vs.
`
`GOOGLE LLC,
`
` Defendant.
`
`
`Civil Action No. 6:22-cv-31-ADA
`
`
`
`
`
`
`
`
`
`
`PLAINTIFF FLYPSI, INC.’S MOTION FOR AN EXCEPTIONAL CASE FINDING
`UNDER 35 U.S.C. § 273(F) AND FOR AN AWARD OF ATTORNEY FEES
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 2 of 16
`
`
`
`I.
`
`II.
`
`TABLE OF CONTENTS
`
`Page
`
`INTRODUCTION .............................................................................................................. 1
`
`FACTUAL BACKGROUND ............................................................................................. 1
`
`III.
`
`LEGAL STANDARDS ...................................................................................................... 3
`
`IV. ARGUMENT ...................................................................................................................... 3
`
`A. Google Cannot Show a Reasonable Basis for Asserting a Defense Under § 273 ........ 3
`
`1. Google Cannot Show a Reasonable Basis Regarding the Inbound Patents ............ 3
`
`2. Google Cannot Show a Reasonable Basis Regarding the Outbound Patents ......... 7
`
`B. The Court Should Award Flyp Attorney Fees .............................................................. 9
`
`CONCLUSION ................................................................................................................. 11
`
`
`
`V.
`
`
`
`i
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 3 of 16
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`
`
`Cases
`
`Coherus Biosciences, Inc. v. Amgen Inc.,
`2020 WL 13634847 (D. Del. June 11, 2020) .............................................................................3
`
`Drop Stop LLC v. Jian Qing Zhu,
`757 Fed. App’x 994 (Fed. Cir. 2019).........................................................................................8
`
`Medtronic Navigation, Inc. v. BrainLAB Medizinische Computersystems Gmbh,
`2008 WL 410413 (D. Col. Feb. 12, 2008) ...............................................................................10
`
`Octane Fitness, LLC v. ICON Health & Fitness,
`572 U.S. 545 (2014) ...................................................................................................................3
`
`Statutes
`
`35 U.S.C. § 103 ................................................................................................................................4
`
`35 U.S.C. § 273 ...................................................................................................................... passim
`
`35 U.S.C. § 285 ................................................................................................................................3
`
`
`
`ii
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 4 of 16
`
`
`
`I.
`
`INTRODUCTION
`
`Throughout this case, Google pursued a prior-use defense based on the falsehood that
`
`Google Voice had not changed in more than a decade. Google presented this argument to the
`
`Court and jury despite
`
`
`
`
`
`. In view of the full
`
`record, Google’s maintenance of this defense was unreasonable. As a result, this case is
`
`exceptional and an award of fees to Flyp is warranted.
`
`II.
`
`FACTUAL BACKGROUND
`
`Flyp sued Google for infringing five patents (the “Asserted Patents”). Dkt. 103 (Flyp’s
`
`Second Am. Compl.). Two of these patents claimed methods for receiving a call on a single mobile
`
`device that contained multiple numbers (the “Inbound Patents”), and three claimed methods for
`
`making a call from a single mobile device that contained multiple phone numbers (the “Outbound
`
`Patents”). See id. Although Google did not plead it (see Dkt. 245 (Google’s First Am. Ans. to
`
`Second Am. Compl.)), at trial, Google raised and submitted to the jury a prior-commercial-use
`
`defense under 35 U.S.C. § 273 based upon its use of pre-2013 Google Voice. Google argued that
`
`the accused versions of Google Voice were the same in all material aspects to the versions of
`
`Google Voice in operation before the priority date of the Asserted Patents (the “pre-2013 Google
`
`Voice”). The testimony and evidence adduced at trial showed that this defense was unreasonable.
`
`For the Inbound Patents, it is indisputable that the accused feature (
`
`
`
`) did not exist in the Google Voice
`
`application
`
`. Tr. at 201:17-202:14, 211:6-10, 292:3-10, 1264:17-1266:9. Google thus
`
`tried to cobble together a prior-use defense based on other, disparate products—and notably made
`
`no argument that
`
` feature Flyp had actually accused of infringement was in prior
`
`1
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 5 of 16
`
`
`
`commercial use. Google’s theory was that a Google Voice precursor, GrandCentral, could forward
`
`inbound calls to various telephone numbers. Id. at 920:3-921:16. Google alleged that a
`
`GrandCentral user could thus forward calls to a VoIP service called Gizmo5, and therefore receive
`
`inbound VoIP calls to a handset. Id. Flyp submitted substantial evidence to the jury that this was
`
`not true. Id. at 1249:6-1253:23, 1267:8-12. This proposed combination did not practice key
`
`limitations from the inventions, including transmitting the handset-associated telephone number
`
`to the handset, which is a feature Google first added to Google Voice using push notification in
`
`2019. Id. at 292:3-24, 1203:15-1204:4, 1246:14-1260:17. Worse, Google’s key fact witness on
`
`Gizmo, Mr. Matt Reilly, admitted that Gizmo “turned off the servers that were running the Gizmo
`
`service” by 2011. Id. at 867:10-14. There was no reasonable basis for Google arguing during trial
`
`that the purported Gizmo prior art was in commercial use when Google had abandoned any
`
`purported use more than a decade before.
`
`Likewise, for the Outbound Patents, pre-2013 Google Voice did not use the inventive
`
`telephone number pairings from the claims—a limitation that Google’s expert confirmed was the
`
`“genius” of the invention (id. at 1056:11-14)—
`
`
`
`. See id. at 1037:18-1059:16, 1077:12-18, 1083:23-1285:6,
`
`1234:3-1242:2, 1299:13-1309:22, 1310:19-1311:25, 1343:16-1344:5, 1346:12-1347:12. And
`
`Google’s engineer, Mr. Tom Ford, who helped launch Google Voice and worked on the project
`
`through the priority date of the Asserted Patents, testified that Google never transmitted data to a
`
`mobile handset with the bridge telephone number (id. at 1198:4-1201:15), as the invention
`
`requires. There was thus no reasonable basis for Google to assert that pre-2013 Google Voice was
`
`using these inventions before the priority date either.
`
`2
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 6 of 16
`
`
`
`III. LEGAL STANDARDS
`
`In limited circumstances, an accused infringer may assert prior commercial use as a defense
`
`to infringement. 35 U.S.C. § 273(a) (requiring accused instrumentality was “in good faith,
`
`commercially used” more than one year before the priority date such that it “would otherwise
`
`infringe a claimed invention being asserted”). This defense is unavailable if the accused infringer
`
`abandoned the purported prior commercial use. Id. at § 273(e)(4). And the accused infringer bears
`
`the burden of showing it did not do so. Tr. at 941:8-942:1.
`
`As this defense may be at odds with public patent policies (e.g., encouraging disclosure)
`
`and the first-to-file system that Congress also enacted in the America Invents Act, the statute
`
`provides a deterrent to misuse—it requires courts to find cases exceptional if an accused infringer
`
`asserts the defense unreasonably. 35 U.S.C. § 273(f) (requiring that when an accused infringer
`
`“subsequently fails to demonstrate a reasonable basis for asserting the defense, the court shall find
`
`the case exceptional for the purpose of awarding attorney fees under section 285”). To determine
`
`whether an assertion was unreasonable, courts consider the totality of the circumstances—
`
`including the relative weaknesses of the assertion. See Coherus Biosciences, Inc. v. Amgen Inc.,
`
`2020 WL 13634847, at *6 (D. Del. June 11, 2020) (citing Octane Fitness, LLC v. ICON Health &
`
`Fitness, 572 U.S. 545, 554 (2014)).
`
`IV. ARGUMENT
`
`A.
`
`Google Cannot Show a Reasonable Basis for Asserting a Defense Under § 273
`
`1.
`
`Google Cannot Show a Reasonable Basis Regarding the Inbound
`Patents
`
`Google’s prior-use defense for the Inbound Patents was unreasonable because Google did
`
`not incorporate the accused functionality into Google Voice until years after the priority date.
`
`Given this plain infirmity, Google improperly and unreasonably cobbled together a prior-use story
`
`3
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 7 of 16
`
`
`
`based on a combination of products that it abandoned more than a decade before trial, thus failing
`
`the continued use requirement of section 273(e)(4).
`
`At trial, Google could not dispute that it added the accused functionality—
`
`
`
`. Tr. at 201:17-202:14, 211:6-10, 292:3-
`
`10, 1264:17-1266:9. However, it argued that two “VoIP endpoints” that consumers could allegedly
`
`use with pre-2013 Google Voice could have fulfilled this limitation. See, e.g., id. at 728:15-20.
`
`The first was a service called Gizmo5. Google’s theory was that a Google Voice precursor called
`
`GrandCentral, which was a call forwarding service, “allowed users to enter a Gizmo5 (a third-
`
`party, VoIP service) Session Initiation Protocol (‘SIP’) address as a forwarding phone,” and that
`
`Google Voice also gave “users the option to forward calls to a Gizmo5 VoIP endpoint, in which
`
`case such calls would be sent directly to the Gizmo5 client via SIP.” DX033.005-06 (October 2009
`
`letter from Google to FCC allegedly describing pre-2013 Google Voice); see also, e.g., Tr.
`
`at 323:16-15 (discussing the FCC letter), 402:17-19 (same).
`
`Notably, for the purposes of invalidity, Google presented this as a Section 103 argument—
`
`tacitly conceding that this was a combination and not part of a single prior commercial use. Tr.
`
`at 952:10-953:2. And Flyp adduced substantial evidence that this proposed combination did not
`
`practice all the limitations in the asserted claims, including because it used neither the claimed
`
`. Id. at 292:3-24, 1203:15-1204:4, 1246:14-
`
`
`
`1260:17. Google left much of this evidence largely unrebutted, evidencing the relative weakness
`
`of its position.
`
`But this is not a situation where Google simply lost based on the balance of the facts.
`
`Google’s Gizmo-based theory, even if it satisfied all the claim limitations (it did not), could not
`
`4
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 8 of 16
`
`
`
`qualify for the prior-use defense as a matter of law because of abandonment. Unrebutted testimony
`
`by Google engineer Mr. Matt Reilly established that had Google discontinued Gizmo5 by 2011.
`
`Mr. Reilly was an engineer at Gizmo from 2004 until its acquisition by Google in 2009, and he has
`
`been at Google ever since. Id. at 839:3-24, 840:12-13, 845:21-846:3. After joining Google,
`
`Mr. Reilly continued working on Gizmo, and his job responsibilities included attempting to adapt
`
`Gizmo to Google Voice. Id. at 846:19-847:3. He confirmed on cross-examination that Google
`
`abandoned whatever functionality it contends Gizmo offered in conjunction with its pre-2013
`
`Google Voice product when Google stopped using Gizmo and actually turned off the servers that
`
`were running the Gizmo service in 2011:
`
`Q. And then I believe you mentioned, moving a little bit further
`ahead in time, that at some point, Google discontinued the Gizmo
`service; is that right?
`
`A. Yes. It was about a year and a half after the acquisition.
`
`Q. So a year and a half after the acquisition -- what date did you say
`the acquisition was again?
`
`A. The acquisition was in November 2009.
`
`Q. So we’re talking sometime in 2011; is that right?
`
`A. Yes.
`
`Q. And after that point, Google had essentially stopped using
`Gizmo, if I’m understanding your testimony correctly, right?
`
`A. In 2011, we turned off the servers that were running the Gizmo
`service.
`
`Id. at 866:24-867:14.
`
`Google did not present any evidence contradicting Mr. Reilly’s testimony that Gizmo was
`
`taken offline—totally and finally—two years before the priority date of the Asserted Patents.
`
`Whatever the temporal bounds for abandonment, a cessation of use of at least two years before the
`
`priority date of July 2013, and thirteen years before Google asserted the defense at trial, qualified.
`
`5
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 9 of 16
`
`
`
`Moreover, Section 273(a)(2) requires that any alleged commercial use must occur at least one year
`
`before the priority date. Here, Google had already abandoned Gizmo even before then. Google’s
`
`assertion of the Gizmo-based prior-use defense was therefore unreasonable.
`
`The second alleged VoIP endpoint was Gmail (also called “Google Talk” or “Google
`
`Hangouts”). Id. at 853:21-854:20. Ostensibly, a Google Voice user could also select Google Talk
`
`as an endpoint. But evidence presented at trial through the testimony of Google’s engineer
`
`Mr. Anthony Jawad and Google’s own documents established that this likewise did not practice
`
`the claim limitation because Gmail was accessed through a browser and the claimed pre-call
`
`information was never sent to a handset. See, e.g., id. at 823:24-829:1, 853:21-854:20, 1253:24-
`
`1254:24; DX23; DX261; PTX-107. Moreover, like Gizmo, Google Talk was abandoned at least
`
`by 2018 or early 2019 (Tr. at 731:3-731:9), long before Google asserted it as commercial prior use
`
`during trial.
`
`In short, Google’s assertion of a prior-use defense for the Inbound Patents was
`
`unreasonable because it was based on a contrived combination of abandoned products that did not
`
`even together practice all of the claim limitations. In particular, its presentation of long-abandoned
`
`products—like Gizmo and Google Talk—in a prior-use defense was improper as a matter of law
`
`and served only to confuse the issues of infringement and validity, elongating and complicating
`
`trial (and now post-trial briefing). The Court should therefore find Google’s assertion of the prior-
`
`use defense for the Inbound Patents to be unreasonable and to accordingly render this case
`
`exceptional for the purposes of awarding attorney fees.
`
`6
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 10 of 16
`
`
`
`2.
`
`Google Cannot Show a Reasonable Basis Regarding the Outbound
`Patents
`
`Google’s assertion of a prior-use defense for the Outbound Patents was similarly
`
`unreasonable. During trial, Google’s witnesses and documents confirmed that Google Voice did
`
`not begin practicing limitations from the Outbound Patents until years after the priority date.
`
`This begins with the unique telephone number pairings in the asserted claims. Google’s
`
`expert, Dr. Gottesman, confirmed on cross-examination that this pairing was the “genius” of the
`
`Outbound Patents. Tr. at 1056:11-14. He also conceded that Google did not implement those
`
`pairings
`
`testimony
`
`time,
`
` (id. at 1039:2-1043:21), well after the priority date. That
`
`. Id. at 1038:1-1039:4; PTX-385.
`
`. Tr. at 1043:22-1044:5.
`
`
`
`
`
`
`
`. PTX-385; Tr. at 1045:11-1054:14. At that
`
` Tr. at 1057:3-25.
`
`. Id. at 1048:7-20.
`
`. Id. at 1053:20-1054:2. That is,
`
`. Id.; see also PTX-385.
`
`This document was not a surprise to Google.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`. PTX-385; Tr. at 1038:7-9. At trial, Google
`
`7
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 11 of 16
`
`
`
`provided no reasonable explanation for this document other than the clear inference that it
`
`
`
`unambiguously
`
`. A document clearly and
`
`
`
`, makes Google’s assertion of the prior-use
`
`defense for the Outbound Patents unreasonable.
`
`And the problems do not end there. Mr. Tom Ford, an engineer who helped launch Google
`
`Voice and was there through Flyp’s patents’ priority dates, testified that Google never transmitted
`
`data to a mobile handset with the bridge telephone number. Tr. at 1198:4-1201:15. Despite this
`
`clear testimony from its own engineer,
`
`. Id. at 1231:8-1232:1.
`
`. Id. at 1230:3-1232:1.
`
`
`
`
`
`
`
`
`
`
`
` Id.; PTX-646. Presenting and advocating
`
`from this weak and very misleading evidence at trial in the face of contradictory testimony from
`
`Mr. Ford—the only engineer who testified with firsthand knowledge about the operation of Google
`
`Voice from its beginning through the priority date—was unreasonable.
`
`In sum, Google’s witnesses and documents confirmed that pre-2013 Google Voice never
`
`practiced various limitations in the Outbound Patents, including because
`
`
`
`Google’s assertion of the prior-use defense for the Outbound Patents to be unreasonable and,
`
`accordingly, to render this case exceptional for the purposes of awarding attorney fees.
`
`. The Court should accordingly find
`
`8
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 12 of 16
`
`
`
`B.
`
`The Court Should Award Flyp Attorney Fees
`
`For the reasons stated above, Google cannot demonstrate a reasonable basis for its assertion
`
`of a prior-use defense, and the Court should exercise its discretion and award Flyp attorney fees.
`
`Like the analysis for determining whether a case is exceptional, courts use a totality of the
`
`circumstances test to evaluate the proper amount of fees. Drop Stop LLC v. Jian Qing Zhu, 757
`
`Fed. App’x 994, 998 (Fed. Cir. 2019).
`
`Under the totality of the circumstances in this case, the Court should award fees because
`
`Google’s unreasonable assertion of the prior-use defense was needlessly cumulative and
`
`potentially confusing to the jury. For example, during trial, Google did not deny that Google Voice
`
`practiced any limitations from the asserted claims in the Outbound Patents. Tr. at 1174:8-1175:4.
`
`Yet Google demanded that the jury be polled on infringement because of its unreasonable prior-
`
`use defense, even though there was a separate jury question on prior use. Id. Likewise, Google
`
`asserted its Gizmo-based and Google Talk-based theories as obviousness arguments for invalidity
`
`but then conflated those systems with the current version of Google Voice by presenting an
`
`unreasonable prior-use defense based on this combination of long-abandoned products. Id.
`
`at 731:3-731:9, 867:10-14. This needlessly complicated trial, the presentation to the jury, and the
`
`jury instructions, not to mention discovery, summary judgment, and post-trial briefing.
`
`Google’s assertion of the prior-use defense was also needlessly cumulative. By trial,
`
`Google’s only invalidity argument was based upon prior-2013 Google Voice. Never did Flyp argue
`
`that pre-2013 Google Voice would not qualify as prior art on the basis that it was not public, or for
`
`any other reason that would require Google to avail itself of a prior-use defense instead.
`
`Nonetheless, throughout the case, into trial, and through post-trial briefing, Flyp has been forced
`
`to conduct discovery, draft briefing, and argue before the Court matters concerning this defense
`
`when, in effect, Google was making the same arguments for both. Because the assertion of a
`
`9
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 13 of 16
`
`
`
`section 273 defense is uncommon, Flyp had to dedicate considerable time and expense to
`
`researching and briefing the novel issues associated with it. Some of this briefing occurred during
`
`trial, when the Court well knows time and resources are precious.
`
`Likewise, Google’s assertion of this defense was needlessly confusing to the jury when it
`
`offered no practical or legal benefit beyond Google’s invalidity case. Instead, it required the jury
`
`to be instructed on another section of the patent code and engage in an additional burden weighing
`
`exercise. As the District of Colorado observed, “[p]atent law is complex and not intuitive to the
`
`average juror. Parties and counsel have an obligation to refrain from seeking to take advantage of
`
`those complexities by employing misleading strategies.” Medtronic Navigation, Inc. v. BrainLAB
`
`Medizinische Computersystems Gmbh, 2008 WL 410413, at *9 (D. Col. Feb. 12, 2008). Here,
`
`when pre-2013 Google Voice was offered both as prior art and as prior commercial use, and when
`
`Google also argued that Google Voice remained unchanged from 2013 to the present day, but also
`
`that it did not infringe, the addition of the complexity of a flawed and facially unreasonable prior-
`
`use defense was needlessly confusing. The Court should award fees to deter this in the future.
`
`Finally, as indicated above, Flyp had to dedicate time and effort to battling Google’s
`
`unreasonable defense at strategically disadvantageous times to Flyp. For instance, during trial,
`
`Flyp was required to engage in urgent briefing regarding what the proper jury instruction would
`
`be on this defense. See Dkt. 285; Dkt. 286. This briefing was entirely Google’s fault because of
`
`its misapprehension that it did not carry the burden on the entirety of its proffered defense,
`
`including on the abandonment issue. An issue that it suggested it had never considered before
`
`trial, despite the fact that Flyp raised it during summary judgment. Dkt. 174 at 10.
`
`Given the totality of the circumstances, including the remarkable weaknesses of Google’s
`
`prior-use defense as described above, the Court should award Flyp attorney fees to avoid the
`
`10
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 14 of 16
`
`
`
`injustice of Flyp bearing the burden for Google’s unreasonable assertion of the prior-use defense,
`
`and to deter such unreasonable assertions in the future.
`
`V.
`
`CONCLUSION
`
`For the reasons expressed above, Flyp respectfully requests this Court hold that Google’s
`
`assertion of the prior-use defense was unreasonable and award Flyp its attorney fees in accordance
`
`with an accounting of fees and costs to be filed at a time the Court deems appropriate.
`
`11
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 15 of 16
`
`DATED: May 23, 2024
`
`
`
`
`
`Respectfully submitted,
`
`/s/ Michael A. Bittner
`Thomas M. Melsheimer
`tmelsheimer@winston.com
`M. Brett Johnson
`mbjohnson@winston.com
`Michael A. Bittner
`mbittner@winston.com
`C. Charles Liu
`ccliu@winston.com
`Steven R. Laxton
`slaxton@winston.com
`Jack Myers
`jmyers@winston.com
`WINSTON & STRAWN LLP
`2121 North Pearl Street, Suite 900
`Dallas, TX 75201
`Telephone: (214) 453-6500
`
`Samantha M. Lerner (pro hac vice)
`slerner@winston.com
`WINSTON & STRAWN LLP
`35 W. Wacker Drive, Suite 4100
`Chicago, IL 60601
`Telephone: (312) 558-5600
`
`Matthew R. McCullough
`mrmccullough@winston.com
`WINSTON & STRAWN LLP
`275 Middlefield Road, Suite 205
`Menlo Park, CA 94025
`Telephone: (650) 858-6500
`
`William M. Logan
`wlogan@winston.com
`Evan D. Lewis
`edlewis@winston.com
`WINSTON & STRAWN LLP
`800 Capitol Street, Suite 2400
`Houston, TX 77002
`Telephone: (713) 651-2766
`
`ATTORNEYS FOR PLAINTIFF
`
`
`
`12
`
`
`
`

`

`Case 6:22-cv-00031-ADA Document 323 Filed 05/29/24 Page 16 of 16
`
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that a sealed copy of the foregoing document was filed electronically in
`
`compliance with Local Rule CV-5. Thereafter, this document was served on all counsel via
`
`electronic mail on May 23, 2024.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Michael A. Bittner
`Michael A. Bittner
`
`
`
`
`
`
`
`
`
`
`
`13
`
`

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