throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`——————
`
`ALARM.COM INC.
`Petitioner
`
`v.
`
`VIVINT, INC.
`Patent Owner
`
`——————
`
`Case IPR2016-00116
`Patent 6,147,601
`
`——————
`
`PETITIONER’S RESPONSE TO PATENT OWNER’S MOTION FOR
`
`OBSERVATION ON CROSS EXAMINATION OF REPLY WITNESS
`
`ARTHUR ZATARAIN
`
`
`
`Mail Stop PATENT BOARD
`Patent Trial and Appeal Board
`US Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`Patent Owner Vivint submits 22 observations, none of which undermine
`
`Petitioner Alarm.com’s record evidence or further develop any existing issue in
`
`this case. Thus, as set forth below, all of the observations should be disregarded.
`
`Response to Observation 1: Vivint cites testimony suggesting that Mr.
`
`Zatarain did not “select[] the arguments” in his Reply Declaration and that attorney
`
`“wordsmithing” of Mr. Zatarain’s declaration is “relevant to the credibility of Mr.
`
`Zatarain’s opinions”. Pat. Owner’s Mot. at 1 (“Motion”) (citing Ex. 2018, 7:2-25).
`
`This observation should be disregarded for at least two reasons. First, Mr. Zatarain
`
`testified unequivocally that his Declaration was “my content, my reply”, that the
`
`attorneys identified topics addressed by Mr. Denning (Vivint’s expert), and that the
`
`attorneys assisted him in formatting citations and other similar clerical work. See
`
`id. at 7:17-22, 8:1-8. Second, Vivint’s claim about Alarm.com’s attorneys
`
`“select[ing] the arguments” is also without merit, as the attorneys merely generated
`
`a list of the “arguments” or “topics” raised by Patent Owner in its Response. See
`
`Ex. 2018, 7:13-15. There is no reason to doubt the sincerity of Mr. Zatarain’s
`
`opinions, and Vivint does not identify any specific opinion it claims is not credible
`
`for this reason.
`
`Response to Observation 2: Vivint cites Mr. Zatarain’s agreement that “a
`
`system that only obtains data from storage and does not write to storage” comports
`
`with the definitions of “access” cited in his Reply Declaration and therefore that
`1
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`the user interface in Shetty could not be used to modify user profiles. Motion at 1-
`
`2. That conclusion is without merit. Mr. Zatarain’s testimony does not contradict
`
`his opinions because he opines that a person of ordinary skill in the art (“POSA”)
`
`would understand the word “access” to include both read-only and read-write
`
`systems. See Ex. 1130, ¶ 56; see also Ex. 2018, 13:23-14:4 (“access” applies to
`
`both reading and/or writing); 16:4-9 (same); 17:4-10 (same); 18:5-14 (same). In
`
`addition, the plain language definitions of access encompass both reading and
`
`writing data, and other disclosures in Shetty make clear to a POSA that users of the
`
`system can use the interface to configure the profiles (Ex. 1130, ¶¶ 44-50, 61-72).
`
`Response to Observation 3: Vivint cites testimony of Mr. Zatarain stating
`
`that he paraphrased, rather than quoted, Mr. Denning with regard to Mr. Denning’s
`
`testimony that the word “access” includes both reading and writing data.
`
`Regardless of whether Mr. Denning used the words “as well as”, Mr. Denning
`
`testified that he agreed that both “retrieval” of data (reading) and “update” of data
`
`(writing) are “access operations”. Ex. 1118, 39:13-19. Thus, there is no
`
`substantive difference in meaning, and Mr. Denning’s testimony supports Mr.
`
`Zatarain’s contentions concerning a POSA’s understanding of the word “access”.
`
`See Ex. 1130, ¶¶ 51-55.
`
`Response to Observation 4: Vivint cites Mr. Zatarain’s statement that the
`
`Shetty reference discloses three logical databases as somehow “undermin[ing]” his
`2
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`supposed argument that “allowing [a] user to input [sic] into the [Shetty] fleet and
`
`machine database” means that “Shetty [also] discloses a user inputting data into the
`
`user profile database”. Motion at 2-3 (citing Ex. 1130, ¶ 49). But Mr. Zatarain
`
`never contended that the fleet and machine database and the user profile database
`
`are the “same database”; instead he opined that adding data to the user profile
`
`database is consistent with Shetty’s express disclosures about the fleet and machine
`
`database. Specifically, Mr. Zatarain explained that Shetty teaches a customizable
`
`system to solve “the problem of having too much data to analyze” with the solution
`
`being a “system [that] allows for the users to decide what events they want to be
`
`notified about and . . . how the system should contact them”. Ex. 1130, ¶ 47. In
`
`that context, Mr. Zatarain explained that a system would be useless if new fleet and
`
`machine data could be added to the system, but users could not be notified of
`
`events concerning the newly-added machines. Id., ¶¶ 49; 70 (“a PHOSITA would
`
`understand that the user profile database would also need to be modified when
`
`changes are made to the fleet and machine data, so that notifications could be
`
`received based on any new machines . . .”). The observation should be ignored.
`
`Response to Observation 5: Vivint cites testimony from Mr. Zatarain
`
`agreeing that the word “also” in the sentence “the user interface also allows the
`
`user to input information relating to the fleet or machine data” informs a POSA
`
`that user interface 110 would allow access to fleet and machine database 104,
`3
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`rather than also reflecting on Shetty’s use of the word “access” in the preceding
`
`sentence of the specification. Vivint misstates Mr. Zatarain’s testimony because it
`
`is incomplete. In fact, Mr. Zatarain testified at page 32, lines 5 through 25 of
`
`Exhibit 2018 that, “I think it’s using the words as they would be commonly known.
`
`Access, input, reading, is all about working with the database, as is commonly
`
`known.” Review of Mr. Zatarain’s complete testimony demonstrates that he did
`
`not contradict his opinion, as reflected in paragraphs 69 and 70 of his Reply
`
`Declaration.
`
`Response to Observation 6: Vivint cites testimony that purportedly
`
`“undermines” Mr. Zatarain’s argument “that databases are read-write unless
`
`otherwise indicated”. Motion at 4 (citing Ex. 1130, ¶ 53). First, Mr. Zatarain did
`
`not opine that “databases are read-write unless otherwise indicated”. Id. Rather,
`
`he opined that, given the plain meaning of the word “access” and Shetty’s
`
`unqualified use of that word, he would have expected Shetty to have made clear if
`
`the user’s “access” was meant to be “read-only”. Second, Mr. Zatarain cited many
`
`dictionary definitions of the word “access” to support his opinion that the plain
`
`meaning of “access” includes read-write capabilities. Id.; see also Ex. 1130, ¶ 58
`
`(addressing “special case” of online phone directory). The cited testimony does
`
`not contradict Mr. Zatarain’s declaration; the observation should be disregarded.
`
`Response to Observation 7: Vivint cites Mr. Zatarain’s testimony that there
`4
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`are “two time periods” and argues that Mr. Zatarain “admitted he was reading
`
`Shetty from a different context”. Motion at 4-5 (citing Ex. 2018, 42:4-10).
`
`Vivint’s legal conclusion is incorrect. As a logical matter, the ’601 Patent’s use of
`
`the word “access” cannot inform—and is irrelevant to—the meaning that Shetty
`
`gave to the word “access”, because Shetty was written prior to the ’601 Patent.
`
`Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 36 (1966) (warning against
`
`“the temptation to read into the prior art the teachings of the invention in issue”).
`
`Response to Observation 8: Contrary to Vivint’s contention, whether rlogin
`
`is enabled by default has no bearing on whether rlogin allows remote execution of
`
`computer programs. Indeed, Vivint’s own evidence describes rlogin as enabling a
`
`user to “use rlogin to log in on a remote host” and “then work on that system just
`
`as [he] would on [his] home system”. Ex. 1130, ¶ 91(citing Ex. 2016, 13-12). In
`
`addition, as to Mr. Zatarain’s personal usage of rlogin, Vivint misstates his
`
`testimony. Mr. Zatarain in fact testified that he had used rlogin on some UNIX
`
`systems, but could not recall whether that UNIX system utilized the HP-UX
`
`operating system. Ex. 2018, 47:6-11.
`
`Response to Observation 9: Regardless of whether rlogin is enabled by
`
`default, as Vivint’s exhibit makes clear, a user can “use rlogin to log in on a remote
`
`host” and “then work on that system just as [he] would on [his] home system”. Ex.
`
`2016, 13-12. Additionally, whether or not enabled by default, “rlogin” does not
`5
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`require any “programming”, as configuration—contrary to Vivint’s suggestion—is
`
`not programming. Ex. 1130, ¶¶ 125-28. Finally, Mr. Zatarain only cited rlogin to
`
`rebut Mr. Denning’s claim that remote shell access was limited to non-interactive
`
`programs. Ex. 2018, 44:14-45:16; 47:12-20; Ex. 1130, ¶¶ 90-93.
`
`Response to Observation 10: The cited testimony is taken out of context.
`
`Whether rlogin and remote shell enable remote access is itself irrelevant, as Mr.
`
`Zatarain cited rlogin only in response to Mr. Denning. Ex. 2018, 44:14-45:16;
`
`47:12-20. As Mr. Zatarain noted, Shetty has a “clear” teaching of remote access.
`
`Ex. 1130, ¶ 76; see also ¶¶ 78-84. Additionally, as Mr. Zatarain testified, “remote
`
`logins were common among UNIX and HP-UX systems for many years prior to
`
`the asserted patents”. Ex. 1130, ¶ 92. As such, the cited testimony is not relevant
`
`to Mr. Zatarain’s assertions in paragraphs 92-93 of his Reply Declaration. In
`
`addition, the disclosure of HP-UX in Shetty is consistent with Shetty’s teaching of
`
`remote user workstations communicating with a central data manager, because
`
`such capabilities were standard in the HP-UX operating system. Ex. 1107, ¶ 82.
`
`Response to Observation 11: Vivint cites Mr. Zatarain’s testimony that “a
`
`computer is going to have certain accessible and non-accessible things for a
`
`particular user” and that rlogin will give a user the same access he would have had
`
`locally. Motion at 6-7. Vivint states that this testimony “contradicts” Alarm.com’s
`
`argument that Shetty teaches “remotely accessing [the] user profile database”. Id.,
`6
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`7. Vivint is incorrect. Regardless of whether rlogin allows a user to “access
`
`everything”, Shetty states that the user can “access the data stored on the third
`
`work station”, including the user profile database—a point that Mr. Zatarain
`
`explained in detail in his Reply Declaration at paragraphs 78 to 84.
`
`Response to Observation 12: Vivint contends that Mr. Zatarain admitted to
`
`“new arguments in the Reply Declaration” that are not discussed in his Opening
`
`Declaration. However, Vivint fails to cite any new argument in the Reply
`
`Declaration (Ex. 1130) that is not discussed in the Opening Declaration (Ex. 1107).
`
`For example, Vivint’s reference to paragraph 95 of the Reply Declaration is not
`
`new because that paragraph expressly cross-references paragraphs 82 to 85 of the
`
`Opening Declaration. Further, Vivint admits that Mr. Zatarain, in his Opening
`
`Declaration, identified Shetty’s disclosure of users receiving notifications at
`
`remote locations as a motivation to extend Shetty’s teachings to allow those users
`
`to remotely configure user profiles as well. Motion at 7.
`
`Response to Observation 13: Vivint states that Mr. Zatarain’s Reply
`
`Declaration included supposedly “new Reply Declaration arguments that allege
`
`commonality of remote configuration”. Vivint’s own argument contradicts its
`
`claim. Vivint discusses the presence of remote configuration in commercial alarm
`
`systems of the time—a point that Vivint acknowledges Mr. Zatarain identified and
`
`discussed in his Opening Declaration at paragraph 84. Not only did Mr. Zatarain
`7
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`cite specific examples of such systems in paragraph 46 of the same declaration, but
`
`Vivint also specifically responded to Alarm.com’s evidence at pages 26-28 of its
`
`Response (Paper 20), demonstrating that Vivint understood Alarm.com’s
`
`contentions and evidence and responded to them substantively.
`
`Response to Observation 14: Vivint reiterates its argument that the need for
`
`remote access by remote users was unknown prior to the ’601 Patent as support for
`
`its incorrect claim that Mr. Zatarain used hindsight reasoning regarding his ease-
`
`of-use opinions. This observation should be disregarded. For one thing, Vivint
`
`already made this argument in its Response (Paper 20, 30-32), and Observation 14
`
`is cumulative. In addition, Mr. Zatarain’s reply testimony demonstrates that the
`
`need for remote access was known in preexisting alarm systems and thus not
`
`hindsight. As Mr. Zatarain explained, some alarm systems of the time enabled
`
`remote access while others did not. Ex. 2018, 132:13-133:3. He further explained
`
`that it was a known problem that users would be required to travel to a central
`
`location to configure the system for those alarm systems that did not enable remote
`
`access. Id. Rather than “hindsight reasoning”, as Vivint contends, Mr. Zatarain’s
`
`testimony relates to his experience with actual systems from the relevant time.
`
`Finally, Mr. Zatarain disclosed several examples of such systems, with citations to
`
`the record. See Ex. 1107, ¶¶ 45, 46; see also Ex. 2018, 135:2-14.
`
`8
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`Response to Observation 15: Vivint observes that the system described in
`
`French provided for remote notification of users, but only local, and not remote
`
`configuration. But neither Alarm.com nor Mr. Zatarain ever claimed that all pre-
`
`existing alarm notification systems supported remote access. French was filed in
`
`1990—years prior to the 1999 invention date at issue—and later prior art alarm
`
`systems, such as Scadaware (manual dated 1994), Shetty (filed 1996), and Levac
`
`(filed 1997), supported remote configuration, thus demonstrating that the industry
`
`had (i) recognized the problem illustrated by French and (ii) arrived at the solution
`
`well prior to the ’601 Patent’s filing date in 1999. See Ex. 1107, ¶¶ 46, 82, 110-11.
`
`Thus, this observation adds nothing new and should be disregarded as cumulative,
`
`including since Vivint raised this very issue in its Response (Paper 20, 26-28).
`
`Response to Observation 16: Vivint misinterprets Mr. Zatarain’s reply
`
`testimony to argue that Shetty and Verbatim are the only prior art systems he cited
`
`as expressly teaching remote configuration. Mr. Zatarain did not agree with the
`
`questioner’s assertion on page 75, lines 17-21 of Exhibit 2018 that he had cited
`
`only Shetty and Verbatim for this proposition. In fact, in response to the question,
`
`Mr. Zatarain expressly referred to the prior art system he developed, Scadaware.
`
`Id., 76:21-23. Mr. Zatarain’s Opening Declaration cited both Scadaware (Ex.
`
`1107, ¶ 46) and Levac (id., ¶¶ 110-11) as prior art systems that taught remote
`
`configuration, as his testimony confirmed. Ex. 2018, 133:19-136:19.
`9
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`Response to Observation 17: Vivint appears to contend that because Levac
`
`and Scadaware are not part of the instituted grounds for the independent claims of
`
`the ’601 Patent, they should be disregarded. For one thing, Levac and Scadaware
`
`are cited as documentary support for Mr. Zatarain’s statement that, “By 1998 it
`
`was common for remote notification systems (such as alarm auto-dialers) to
`
`include remote configuration of callout phone numbers, alarm triggers, and other
`
`system parameters.” Ex. 1107, ¶ 84; see also id., ¶¶ 46, 111. Parties may submit,
`
`and the Board may consider, additional documentary evidence to establish the
`
`knowledge of a POSA, even if such evidence is not part of the instituted grounds.
`
`Genzyme Therapeutic Prods. Ltd. v. Biomarin Pharm. Inc., 825 F.3d 1360, 1369
`
`(Fed. Cir. 2016) (“[T]he Board may consider a prior art reference to show the state
`
`of the art at the time of the invention, regardless of whether that reference was
`
`cited in the Board’s institution decision.”). In addition, Levac is prior art for the
`
`instituted grounds for dependent claims 7, 19, 20, 28, 39 and 41.
`
`Response to Observation 18: The cited testimony misconstrues
`
`Alarm.com’s argument and is not relevant to Mr. Zatarain’s opinions on the
`
`construction of the term “message profile”. Vivint and Mr. Denning argued that
`
`the ’601 Patent, at column 4, lines 39-47, “explicitly define[d]” the term “message
`
`profile.” Ex. 1130, ¶ 27 (internal citations omitted). Mr. Zatarain opined in his
`
`Reply Declaration that, if that excerpt were a definition of message profile as
`10
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`Vivint and Mr. Denning proposed, then all of the functionality stated in that
`
`teaching—rather than some of the functionality—must be included in the
`
`“definition” of message profile. Mr. Zatarain has consistently opined that this
`
`excerpt does not reflect a definition of “message profile” (Ex. 1130, ¶¶ 28-29), and
`
`Alarm.com has argued that “account” and “access via the internet” are not part of
`
`the message profile (Reply, Paper 26, 2).
`
`Response to Observation 19: Vivint cites Mr. Zatarain’s testimony as
`
`purportedly relevant to whether Shetty teaches a “message profile” under Vivint’s
`
`proposed construction of that term. Motion at 11-12. However, the testimony to
`
`which Vivint refers—that Shetty “indicate[s] that a profile is tied to a specific
`
`user”, (Ex. 2018, 94:11-13)—is entirely consistent with Mr. Zatarain’s opinion that
`
`Shetty teaches a message profile even under Vivint’s construction:
`
`“[E]ach profile identifies an individual who is to receive the
`
`outgoing message, and how they are to be contacted. Ex. 1103
`
`2:53-61 (defining multiple profiles for ‘user one’ and ‘user two’).
`
`Because Shetty teaches multiple profiles for individual users, it
`
`teaches a data record that specifies one or more devices associated
`
`with one or more individuals to which an outgoing message can
`
`be routed in response to an incoming exception message, even
`
`under Patent Owner’s construction.” Ex. 1130, ¶ 43.
`
`11
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`Thus, this observation adds nothing that Mr. Zatarain has not already stated in his
`
`declaration, and should be disregarded as cumulative.
`
`Response to Observation 20: The testimony cited by Vivint misconstrues
`
`Mr. Zatarain’s testimony and is irrelevant. Motion at 12. An “equipment
`
`identification code” is a “separate number” from a “communication device
`
`identification code”. Ex. 2018, 111:4-112: 19. While an equipment identification
`
`code could be an ESN, as Mr. Zatarain made clear, a “PHOSITA would not expect
`
`the ‘communication device identification code’ of a user’s device that receives
`
`outgoing messages to include an ESN without explicit disclosure in the Patent”.
`
`Ex. 1130, ¶ 150; see also id., ¶¶148-49.
`
`Response to Observation 21: The cited testimony regarding the Verbatim
`
`reference (Ex. 1120) is not relevant to whether new arguments have been made.
`
`By Vivint’s own admission, it “challenged” an argument that Mr. Zatarain made—
`
`that “remote configuration was common in the art”—and Mr. Zatarain identified
`
`the Verbatim reference (Ex. 1120) in response to that “challenge[]” of his
`
`argument. For that reason, Exhibit 1120 is proper rebuttal evidence, and Mr.
`
`Zatarain’s use of Exhibit 1120 is not relevant to whether Alarm.com and Mr.
`
`Zatarain raised “new arguments and new evidence” in the Reply and Reply
`
`Declaration, respectively. See Ex. 2018, 74:18-75:16 (detailing argument in Mr.
`
`Zatarain’s Opening Declaration).
`
`12
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`Response to Observation 22: Vivint claims that Mr. Zatarain did not
`
`“specifically suggest any particular market pressures” to motivate a modification
`
`of Shetty. Motion at 13. But the testimony cited by Vivint is incomplete, and the
`
`observation should therefore be disregarded. Specifically, Vivint asks Mr. Zatarain
`
`to locate “market pressures” in his Reply Declaration. Although the testimony that
`
`Vivint cites, which references paragraphs 101 through 104 of Mr. Zatarain’s Reply
`
`Declaration, does not identify a particular market pressure (Ex. 2018, 50:23-
`
`51:10), Mr. Zatarain cites to paragraph 95 of his Reply Declaration in the
`
`testimony that immediately follows, which does. The uncited testimony (Ex. 2018,
`
`51:18-52:17) discusses motivations to modify Shetty, which Mr. Zatarain explains
`
`constitute “market pressure or design emphasis” that would motivate a POSA.
`
`Furthermore, paragraph 95 cites paragraphs 82 to 85 of Mr. Zatarain’s Opening
`
`Declaration, in which he discusses the availability of remote configuration of
`
`notification parameters in other alarm systems as a motivation to include that
`
`feature in Shetty. Mr. Zatarain thus identified specific reasons to extend Shetty in
`
`his Opening Declaration, and then cited to those reasons in his Reply Declaration,
`
`as he explained in response to Vivint’s questioning at his deposition.
`
`
`
`
`
`*
`
`
`
`
`
`*
`
`
`
`
`
`*
`
`For the reasons cited above, Alarm.com respectfully submits the Board
`
`should disregard all of Vivint’s observations.
`
`13
`
`
`
`

`
`
`
`
`
`
`
`
`
`
`
`Dated: January 10, 2017
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`
`
`Respectfully submitted,
`
`By: /s/ Brian K. Shelton
`
`Brian K. Shelton
`
`Registration No. 50,245
`
`Counsel for Petitioner
`
`14
`
`
`
`

`
`Case IPR2016-00116 of
`U.S. Patent No. 6,147,601
`
`
`CERTIFICATE OF SERVICE
`
`
`The undersigned certifies that a copy of the attached PETITIONER'S
`
`
`
`RESPONSE TO PATENT OWNER'S MOTION FOR OBSERVATION ON
`
`CROSS EXAMINATION OF REPLY was sent via electronic mail on January 10,
`
`2017 to the following:
`
`Robert G. Sterne (rsterne-PTAB@skgf.com)
`Jason D. Eisenberg (jasone-PTAB@skgf.com)
`PTAB@skgf.com
`STERNE, KESSLER, GOLDSTEIN & FOX
`1100 New York Avenue, N.W.
`Washington, DC 20005
`
`Counsel of Record for the Patent Owner in this proceeding
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`By: /s/ Brian K. Shelton
`
`Brian K. Shelton
`
`Registration No. 50,245
`
`Counsel for Petitioner
`
`Dated: January 10, 2017
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`15

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