throbber
Paper No. __
`
`Filed on behalf of Petitioner
`By:
`/Richard F. Giunta/
`
`Richard F. Giunta
`Elisabeth H. Hunt
`Randy J. Pritzker
`WOLF, GREENFIELD & SACKS, P.C.
`600 Atlantic Avenue
`Boston, MA 02210
`Tel: (617) 646-8000
`Fax: (617) 646-8646
`RGiunta-PTAB@wolfgreenfield.com
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`_____________
`RPX Corporation
`Petitioner
`v.
`Applications in Internet Time, LLC
`Patent Owner
`_____________
`
`Case IPR2015-01750
`Patent 8,484,111 B2
`
`Case IPR2015-01751
`Case IPR2015-01752
`Patent 7,356,482 B21
`
`_____________
`PETITIONER’S (REDACTED) REPLY TO PATENT OWNER’S
`PRELIMINARY RESPONSE ON REAL-PARTY-IN-INTEREST(RPI)
`
`
`1 The word-for-word identical paper is filed in each proceeding identified in the
`heading.
`
`
`
`
`
`

`
`TABLE OF CONTENTS
`
`TABLE OF CONTENTS
`
`!—1
`
`INTRODUCTION ........................................................................................... ..1
`
`III.
`
`THE FACTS RELEVANT TO RPI ................................................................ ..5
`
`IV.
`
`SALESFORCE IS NOT AN RPI .................................................................... ..8
`
`A. RPX Pursues Its Own Interests In These IPRs .......................................... ..8
`
`THE LAW ON RPI ......................................................................................... ..2
`
`INTRODUCTION ............................................................................................. 1
`I.
`II. THE LAW ON RPI ........................................................................................... 2
`III. THE FACTS RELEVANT TO RPI .................................................................. 5
`IV. SALESFORCE IS NOT AN RPI ...................................................................... 8
`A. RPX Pursues Its Own Interests In These IPRs ............................................ 8
`B. RPX Is Not Salesforce’s Proxy and Did Not File at Its Behest .................. 9
`B. RPX Is Not Salesforce’s Proxy and Did Not File at Its Behest ................ ..9
`1. Salesforce Did Not Pay For the IPRs ..................................................10
`1. Salesforce Did Not Pay For the IPRs ................................................ .. 10
`2. Salesforce Had No Role in the IPRs ...................................................10
`3. There Was No Communication About the Petitions ...........................10
`4. Shared Board Member Robertson Was Uninvolved ...........................11
` ................................12
`C.
`c.T .............................. -12
`D. AIT Mischaracterizes RPX’s History In Filing IPRs ................................13
`D. AIT Mischaracterizes RPX’s History In Filing IPRs .............................. ..l3
`V. AIT REPEATEDLY AND KNOWINGLY MISREPRESENTS
`FACTS .............................................................................................................15
`
`
`2 Salesforce Had No Role in the IPRs ................................................. ..lO
`
`3. There Was No Communication About the Petitions ......................... .. 10
`
`4. Shared Board Member Robertson Was Uninvolved ......................... ..1l
`
`AIT REPEATEDLY AND KNOWINGLY MISREPRESENTS
`
`FACTS ........................................................................................................... .. l 5
`
`
`
`
`
`

`
`TABLE OF AUTHORITIES
`
`CASES
`Butamax,
`IPR 2013-00214, Paper 11 ...................................................................................12
`
`Expert Electric, Inc. v. Levine,
`554 F.2d 1227 (2nd Cir. 1977) ............................................................................... 9
`
`General Foods Corp. v. Massachusetts Dept. of Public Health,
`648 F.2d 784 (1st Cir. 1981) .................................................................................. 9
`
`Global-Tech Appliances v. SEB S.A.,
`131 S.Ct. 2060 (2011) ..........................................................................................15
`
`ParkerVision,
`IPR 2014-00946, Paper 27 ...................................................................................14
`
`RPX Corporation v. Macrosolve, Inc.,
`Case IPR2014-00140 (PTAB May 16, 2014) (Paper 9)......................................... 3
`
`RPX Corporation. v. VirnetX, Inc.,
`Case IPR2014-00171 (PTAB Jun. 5, 2014) (Paper 49) ...................................6, 14
`
`Taylor v. Sturgell,
`553 U.S. 880 (2008) ...................................................................................... 4, 5, 9
`
`TRW Automotive U.S. LLC v. Magna Electronics Inc.,
`Case IPR2015-00950 (PTAB Sept. 17, 2015) (Paper No. 8) ................................. 3
`
`Unified Patents Inc. v. Hall Data Sync Technoogies, LLC,
`Case IPR2015-00874 (PTAB Sept. 17, 2015) (Paper 11) ...................................... 3
`
`Unified Patents, Inc. v. Dragon Intellectual Property, LLC,
`Case IPR2014-01252 (PTAB Feb. 12, 2015) (Paper 37) ............................ 3, 8, 12
`
`Zerto,
`IPR2014-01295, Paper 31 ...................................................................................... 2
`
`Zoll,
`IPR2013-00609, paper 15 ....................................................................................... 4
`
`RULES
`
`
`
`

`
`77 F. Reg. at 48759 ........................................................................................... 3, 4, 8
`77 F. Reg. at 48759 ......................................................................................... .. 3, 4, 8
`
`
`
`

`
`I.
`
`
`
`INTRODUCTION
`
`RPX filed the petitions to further its own interests and is the sole RPI. The
`
`petitions’ identification of RPI is presumed correct. To rebut that presumption AIT
`
`must provide sufficient evidence to call RPX’s identification of RPI into question.
`
`AIT was granted extensive discovery into (1) agreements between RPX and
`
`Salesforce; (2) communications between RPX and Salesforce, including any
`
`relating to these IPRs, the underlying patents and/or the litigation involving them;
`
`(3) any funds RPX received to pay for the IPRs; and (4) the reasons why RPX filed
`
`the IPRs. Paper 11. RPX provided all responsive documents and a sworn
`
`declaration from William Chuang, VP of Client Relations at RPX, who was
`
`involved in and explains RPX’s decision to file the IPRs. Ex. 1019 at ¶¶1, 5 and
`
`
`
`
`
`
`
`
`
`34.2
`
` Id. at ¶47.
`
`As Mr. Chuang states unequivocally, “RPX had no communication with
`
`Salesforce whatsoever regarding the filing of IPR petitions against the AIT Patents
`
`
`2 Citations are to the Exhibit numbers used in IPR2015-01750 and IPR2015-01751.
`
`
`
`
`
`
`

`
`before the AIT IPRs were filed. Salesforce did not request that RPX file the AIT
`
`IPRs, was not consulted about the decision by RPX to file the IPRs, and did not
`
`communicate with RPX about the searching for or selection of prior art asserted in
`
`the AIT IPRs, the selection of counsel for the IPRs, the selection of an expert for
`
`the IPRs, or any other aspect of the IPRs. RPX had no obligation (contractual or
`
`otherwise) to Salesforce to file the AIT IPRs and Salesforce did not fund the AIT
`
`IPRs.” Id. at ¶20.
`
`After representing that the evidence RPX produced,
`
`
`
` and the highly confidential reasons why RPX filed the IPRs, was
`
`“needed” to determine whether Salesforce was an RPI, AIT completely ignored
`
`this evidence in its Preliminary Response (PR). Mot. for Discovery at 5. Instead,
`
`AIT invites the Board to speculate and draw unsupported inferences directly
`
`refuted by the evidence RPX produced and AIT kept from the Board. AIT presents
`
`no evidence to rebut the presumption that RPX properly named itself the sole RPI,
`
`and the evidence overwhelmingly establishes that Salesforce is not an RPI.
`
`II. THE LAW ON RPI
`The petition is presumed to correctly name the RPI. Zerto, IPR2014-01295,
`
`Paper 31 at 6-73. Only if the patent owner “provides sufficient rebuttal evidence
`
`that reasonably brings into question the accuracy of petitioner’s identification” of
`
`
`3 Full citations to all cited Board decisions are provided in the Table of Authorities.
`
`
`
`
`

`
`RPI must the petitioner present evidence to establish that RPI was properly
`
`identified. Id. An RPI is a party that “desires review,” which the Trial Practice
`
`Guide (TPG) defines as the petitioner and/or a party “at whose behest the petition
`
`has been filed.” 77 Fed. Reg. at 48,759. In determining RPI, the Board most
`
`commonly considers (1) “whether the non-party exercised or could have exercised
`
`control over a party’s participation in a proceeding” and (2) “whether the non-party
`
`funded the proceeding.” Id. at 48759-48760.
`
`The Board has never held, and there is no law to support, that a non-party
`
`“desires review” simply because it might benefit from invalidation of a challenged
`
`patent and has a relationship with the petitioner unrelated to the IPR. While the
`
`relationship of an unnamed party to the petitioner is relevant, “[t]he key inquiry is
`
`‘the relationship between a party and a proceeding’ rather than ‘the relationship
`
`between parties.’” TRW, IPR 2015-00950, Paper No. 8 at 6 (emphasis in original).
`
`The Board has consistently held that clients of an entity that challenges patents as
`
`part of its business are not RPIs absent involvement in the IPR. RPX v.
`
`Macrosolve, IPR 2014-00140 (Paper 9 at 3-4) (“Mere membership in petitioner
`
`RPX Corporation … does not demonstrate the requisite control over petitioner by
`
`the alleged unnamed” RPI.); Unified, IPR 2015-00874, Paper 11 at 3-4; see also
`
`the TPG’s explanation that trade association members are not automatically RPIs
`
`in an IPR filed by the association. TPG at 48,760.
`
`
`
`
`
`

`
`While the RPI inquiry is “highly fact-dependent,” the TPG is clear that
`
`whatever the facts, they are analyzed to determine whether they establish
`
`“relationships and considerations sufficient to justify applying conventional
`
`principles of estoppel and preclusion.” 77 Fed. Reg. at 48,759. In Taylor (cited in
`
`the TPG and by AIT), the Supreme Court (“SCOTUS”) emphasized that there are
`
`only “discrete exceptions that apply in ‘limited circumstances’” to the general rule
`
`that a non-party is not bound by a judgment, and that an “amorphous balancing test
`
`is at odds with the constrained approach to nonparty preclusion our decisions
`
`advance.” Taylor v. Sturgell, 553 U.S. 880, 898 (2008).
`
`AIT specifically asserts that Salesforce is an unnamed RPI because RPX
`
`filed the petitions as a proxy or agent for Salesforce. PR at 5, 8. However, the
`
`SCOTUS has held that under the proxy/agent exception “preclusion is appropriate
`
`only if the putative agent’s conduct of the suit is subject to the control of the party
`
`who is bound by the prior adjudication.” Taylor, 553 U.S. at 905, 906. Thus, the
`
`proxy/agent exception AIT relies upon requires a showing of control. AIT quotes
`
`Zoll (without attribution) for the proposition that the non-party’s participation may
`
`be overt or covert and that evidence may be direct or circumstantial, but omits the
`
`critical remainder of the sentence in which the Board emphasized that “the
`
`evidence as a whole must show that the non-party possessed effective control from
`
`a practical standpoint.” PR at 5; Zoll, IPR2013-00609, paper 15 at 10.
`
`
`
`
`
`

`
`AIT suggests that a third party may be an RPI even though it did not fund,
`
`control or direct the IPR, did not ask the petitioner to file at its behest and was not
`
`even aware of the filing beforehand. All the relevant authority refutes this.
`
`Identifying a party as an RPI carries important estoppel implications and as Taylor
`
`makes clear, it would be entirely inappropriate to find a non-party an RPI and bind
`
`it to the outcome of a matter not filed at its behest (indeed of which the non-party
`
`was not even aware) and over which the non-party had no control or opportunity to
`
`control. Taylor, 553 U.S. at 905, 906.
`
`III. THE FACTS RELEVANT TO RPI
`As stated in §I supra, Salesforce was totally uninvolved in RPX’s filing of
`
`the IPRs. Ex. 1019 at ¶20. RPX did not have any contractual obligation to file the
`
`IPRs or any “unwritten,” implicit or covert understanding with Salesforce that it
`
`would do so. Id. at ¶45.
`
` none obligate RPX to file IPRs.4 Ex. 1020-1022.
`
`
`4
`
`Ex. 1019 at ¶33.
`
`
`
`
`
`
`
`
`
`
`
`
`
` Id.
`
`
`
`
`
`

`
`The Board ordered discovery of all communications with Salesforce relating
`
`to the challenged patents, the litigation or the IPRs. Paper 11.
`
`
`
` Ex. 1019 at
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`¶¶20-30.
`
`1023; Ex. 1025.
`
` Id at ¶¶20-21; Ex.
`
` Ex. 1019 at ¶¶22 and 29.
`
`
`
` Id. at ¶¶14, 16, and 19; Ex. 2018.
`
` Ex. 1019 at ¶¶14, 40.
`
` Id. at ¶19 (citing examples).
`
`Id. at ¶7.
`
`
`
`
`
`

`
`
`
`
`
` Id. at ¶¶8-10.
`— Id- W118-10.—
`
` Id. at ¶¶11-13.
` Id- at‘1I‘1I11-13.
`
`
`
` Id. at ¶¶34-44.
`— Id. at $9134-44.‘
`
`
`
`
`
` Id. at ¶47.
`
` Id. at ¶¶43 and 47.
`
` Id. at ¶37; Ex. 1024.
`
` Ex. 1019 at ¶37.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`
`
`
` Id. at ¶18.
`
`
`
`
`
` Id. at ¶47.
`
`Any assertion that Mr. Chuang’s declaration should be disregarded fails. Mr.
`
`Chuang is not in-house counsel for RPX - he is a VP of Client Relations. Id. at ¶1.
`
`Mr. Chuang is indisputably a fact witness and his testimony is corroborated by
`
`documents RPX produced and directly responsive to the ordered discovery
`
`(including a request for oral communications). Id. at ¶¶1, 5, 34.
`
`IV. SALESFORCE IS NOT AN RPI
`AIT misstates the law and invites the Board to speculate and draw inferences
`
`that are unsupported and directly refuted by the evidence. What the evidence
`
`shows is that RPX filed the IPRs to pursue its own interests, the IPRs were not
`
`filed at Salesforce’s behest, and Salesforce did not fund the IPRs, nor have any
`
`control, opportunity to control or involvement in them. RPX is the sole RPI.
`
`A. RPX Pursues Its Own Interests In These IPRs
`AIT asserts that RPX has no interest in these IPRs because it has not been
`
`sued on the AIT Patents. PR at 1, 6-7, 13. This fact is “unremarkable” for an IPR
`
`(as opposed to a CBM). Unified v. Dragon, Paper 37 at 13; §II, supra. As
`
`
`
`
`
`

`
`described in §III supra, the evidence overwhelmingly shows that RPX had its own,
`
`independent reasons to file the IPRs. Ex. 1019 at ¶¶6-13, 16, 35-47.
`
`AIT’s citations to General Foods and Expert Electric are inapposite. PR at
`
`19. General Foods held that “a member of a trade association who finances an
`
`action which [the association] brings on behalf of its members impliedly authorizes
`
`the trade association to represent him in that action.” General Foods Corp. v.
`
`Massachusetts Dept. of Public Health, 648 F.2d 784 (1st Cir. 1981). Salesforce
`
`did not finance the IPRs and RPX filed them to pursue its own interests rather than
`
`Salesforce’s. §III, supra. Expert Electric, Inc. v. Levine, 554 F.2d 1227, 1233-
`
`1235 (2nd Cir. 1977) also involved different facts, including a labor regulatory
`
`scheme that recognized an association “as the single representative of all [its]
`
`participants” in connection with an overseeing agency, and recognized the
`
`association as having “standing to assert the interests of its members.”
`
`B. RPX Is Not Salesforce’s Proxy and Did Not File at Its Behest
`AIT asserts repeatedly that RPX filed as a proxy or agent for Salesforce. PR
`
`at 1-2, 13-20. Saying it repeatedly does not make it so. A finding that RPX acted
`
`as a proxy for Salesforce would only be “appropriate” if RPX’s filing was “subject
`
`to the control” of Salesforce. Taylor, 553 U.S. at 905, 906. AIT cites no evidence
`
`of this, and AIT’s assertions and speculation are directly refuted by the evidence.
`
`Ex. 1019 at ¶¶20 and 45. The IPRs were not filed at Salesforce’s behest (i.e.,
`
`
`
`
`
`

`
`command), as Salesforce did not request, let alone command, that RPX file them,
`
`and indeed was not even aware that RPX would file. Id.; Ex. 1018.
`
`1.
`
`Salesforce Did Not Pay For the IPRs
`
`
`
`
`
`
`
`
`
`
`
`
`
` PR at 2 and 11-12.
`
` Exs. 1020-1022. Mr. Chuang confirms
`
`unequivocally, “Salesforce did not fund the AIT IPRs.” Ex. 1019 at ¶¶20 and 45.
`
`Salesforce Had No Role in the IPRs
`
`2.
`AIT misrepresents that “RPX does not state affirmatively … that Salesforce
`
`had no role in the petition.” PR at 9. RPX has stated this repeatedly, including in
`
`the Petitions (§II.A), in RPX’s motion opposing discovery (at 1) and in Mr.
`
`Chuang’s declaration (Ex. 1019 at ¶20 and 45).
`
`3.
`
`There Was No Communication About the Petitions
`
`
`
` PR at 13-19.
`
`
`
`
`
`
`
`
`

`
`
`
`
`
`
`
`PR at 17-18.
`
`These misrepresentations are extraordinary. Discovery Request No. 3
`
`sought actual communications relating to the AIT Patents, the litigation or the IPRs
`
`and Request No. 4 sought only documents sufficient to show (not actual
`
`communications) the names, dates, locations and times (but not the content) of all
`
`communications (include those unrelated to the litigation, the AIT Patents or the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`IPRs) after the litigation began. Paper 11.
`
`Ex. 1019 at ¶32.
`
` while withholding Mr. Chuang’s
`
`declaration that swears this to not be true is stunning. PR at 17-18.
`
`4.
`
`Shared Board Member Robertson Was Uninvolved
`
`
`
`
`
`

`
`AIT concedes that given the absence of any contrary evidence, the “only
`
`inference” is that Mr. Robertson “has dutifully served both [RPX and Salesforce]
`
`companies.” PR at 13. Inexplicably, AIT suggests that this somehow evidences
`
`RPX’s “plausible deniability” of Salesforce’s involvement in the IPRs. Id. Mr.
`
`Chuang, who participated in RPX’s decision to pursue the IPRs, explains that Mr.
`
`Robertson was uninvolved in the decision. Ex. 1019 at ¶51-52. An overlapping
`
`board member uninvolved in the IPR decision does not demonstrate Salesforce
`
`control or involvement in the IPRs. Butamax, IPR 2013-00214, Paper 11 at 4.
`
`AIT asserts that “Petitioner’s business model is built upon petitioner acting
`
`
`
`
`
`as an agent or proxy for third parties in cases just like this.” PR at 6-7.
`
` The Board has held that even if a “Petitioner
`
`engages in no activity of practical significance other than filing IPR petitions with
`
`money received from its members, this does not demonstrate that any member
`
`paid, directed, or suggested to Petitioner to challenge the [patent], specifically.”
`
`Unified v. Dragon, IPR 2014-01252, Paper 37 at 12-13.
`
`
`
`
`
` Ex. 1020 at §2; Ex. 1019 at ¶45 (“RPX has no contractual obligation to
`
`
`
`
`
`

`
`Salesforce to file an IPR under any circumstances … and has no “unwritten” or
`
`
`
`implicit understanding … [to] do so.”)
`
` Instead, AIT focuses the Board on out-of-context quotes
`
`from three public documents
`
`
`
` In the cited materials, serving as an extension of a client’s in-house
`
`legal team does not refer to attacking patents, but to RPX sharing insight about the
`
`patent market. Ex. 2006. The reference to “clear[ing]” liability refers not to
`
`attacking patents but to RPX acquiring “a license to the litigated patent.” Ex.
`
`2007. The reference to “challenging patents” is a “complementary solution.” Ex.
`
`2008 at 4. The reference to RPX acting as an agent relates to special “syndicated
`
`acquisitions” where RPX acquires patent rights “on behalf of clients who are
`
`paying for such rights separately from their subscription arrangements.” Id. at 26,
`
`53. AIT’s speculation is unsupported by the cited materials and directly refuted by
`
` sworn testimony that make clear that RPX did not
`
`file these petitions on behalf of Salesforce. Ex. 1020; Ex. 1019 at ¶45.
`
`D. AIT Mischaracterizes RPX’s History In Filing IPRs
`RPX has filed 21 petitions against 10 different patent owners.
`
`
`
` when RPX works with another party, the other party is named an
`
`RPI. Ex. 1019 at ¶19. Contrary to AIT’s misrepresentations, the Board in
`
`
`
`
`
`

`
`ParkerVision did not find that RPX acted as a proxy for a concealed RPI. PR. at 9.
`
`Despite the Board’s invitation to revisit RPI if granted discovery proved fruitful,
`
`the patent owner did not do so because discovery revealed no other RPI.
`
`ParkerVision, IPR 2014-00946, Paper 27 at 1-2.
`
`VirnetX, IPR 2014-00171, and the related IPRs (collectively “VirnetX”) was
`
`an early case on previously unsettled RPI law and was an outlier. None of RPX’s
`
`other filings has been found to involve an unnamed RPI. The facts the Board
`
`focused on in VirnetX are not present here. The Board found that Apple paid RPX
`
`to file IPRs as part of a “newly created program” and “at least suggested that RPX
`
`file challenges to the specific VirnetX Patents.” VirnetX at 4, 7. Salesforce is not
`
`part of any such program and never suggested or implied that RPX should file
`
`these IPRs. The Board also found that RPX used “Apple’s expert” and law firm to
`
`file a petition with “substantially identical” grounds to Apple’s. Id. at 6-7.
`
`Salesforce’s CBMs used different counsel, a different expert and different grounds.
`
`VirnetX does not apply.
`
`
`
`
`
` PR at 9-10. Filing IPRs serves
`
`RPX’s own important business interests and RPX takes its obligation to properly
`
`name RPIs very seriously. Ex. 1019 at ¶¶6-13.
`
`
`
`
`
`
`
`

`
`
`
`
`
`
`
` Id. at ¶45; Ex. 2018.
`
` PR at 10. Global-Tech concerns imputing
`
`knowledge for induced infringement and is completely irrelevant to the
`
`determination of RPI. Global-Tech Appliances v. SEB S.A., 131 S.Ct. 2060, 2068-
`
`2072 (2011). RPX’s careful actions to name all involved parties an RPI and avoid
`
`outside input from others cannot support finding an uninvolved party an RPI.
`
`V. AIT REPEATEDLY AND KNOWINGLY MISREPRESENTS FACTS
`AIT makes numerous false factual assertions refuted by evidence it withheld
`
`from the Board (see supra §IV.B.1
`
`, §IV.B.2 re RPX not
`
`stating Salesforce uninvolved, §IV.B.3
`
`Mr. Robertson’s involvement and §IV.C re
`
`, §IV.B.4 re
`
`). AIT’s
`
`PR also falsely asserts that RPX filed 25 IPRs (only 20 had been filed at the time)
`
`and that the AIT IPR petitions were already prepared when the Salesforce CBMs
`
`were denied. PR at 18 and 40. AIT also falsely stated on a call that Mr. Chuang is
`
`in-house counsel for RPX when seeking to keep his declaration from the Board.
`
`Given AIT’s demonstrated recklessness with the facts, RPX requests the Board’s
`
`vigilance in scrutinizing representations AIT makes in its sur-reply.
`
`
`
`
`
`

`
`CERTIFICATE OF SERVICE UNDER 37 C.F.R. § 42.6 (e)(4)
`
`It is hereby certified that on this 14th day of December 2015, a copy of the
`
`foregoing document was served via electronic mail, as previously consented to by
`
`Patent Owner upon the following counsel of record:
`
`Steven C. Sereboff (Reg. No. 37,035)
`M. Kala Sarvaiya (Reg. No. 58,912)
`Jonathan Pearce (Reg. No. 60,972)
`SoCal IP Law Group LLP
`310 N. Westlake Boulevard, Suite 120
`Westlake Village, CA 91362
`uspto@socalip.com
`
`
`
`
`
`Date: December 14, 2015
`
`/Richard F. Giunta/
`Richard F. Giunta

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