throbber

`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`MOBOTIX CORP.
`Petitioner
`
`v.
`
`E-WATCH, Inc.
`Patent Owner
`
`
`
`Case IPR2013-00255
`Patent No. 6,970,183
`
`
`
`
` PETITIONER’S REPLY TO PATENT OWNER’S RESPONSE
`UNDER 37 C.F.R. § 42.23
`
`
`
`
`
`
`
`
`

`
`
`
`1
`
`

`

`INTRODUCTION
`
`
`
`The Board instituted Inter Partes Review as to claim 1-25 and 32-34 of the ‘183
`
`Patent based on the following references: Claims 1-9, 12-17, 25 and 32 as obvious over Ely
`
`(Document 5: Exhibit 1004) and Fernandez (Document 9:Exhibit 1008)(Ground 1); Claims
`
`10, 11 and 18-23 as obvious over Ely, Fernandez and Imaide (Document 10: Exhibit
`
`1009)(Ground 2); Claim 24 as obvious over Ely, Fernandez and Barzdins (Document
`
`11:Exhibit 1010)(Ground 3); Claims 25 and 33 as anticipated by Kogane (Document
`
`8:Exhibit 1007)(Ground 4); and Claims 32 and 34 as obvious over Kogane and Fernandez
`
`(Ground 5). Decision (Document 27), p. 34.
`
`
`
`E-Watch’s Patent Owner Response (“POR”) fails to make a prima facie case for
`
`patentability of any of claims 1-25, or 32-34 of the ’183 patent. As a threshold matter, the
`
`POR is basically a copy of the Patent Owner’s Preliminary Response (POPR)(Document
`
`26). The Board already reviewed the POPR and decided to institute the Inter Partes
`
`Review. Since no material new facts or substantive new arguments are provided by Patent
`
`Owner (PO) in the POR the Board should come to the same conclusion as it did when the
`
`Inter Partes Review was instituted.
`
`ARGUMENT
`
`
`
`PO argues only the independent claims 1, 18 and 25 and submits that the dependent
`
`claims stand and fall with the independent claims, and PO has failed to separately address
`

`
`2
`
`

`

`the dependent claims. POR, p. 6. Accordingly, Petitioner will address only the independent
`
`claims herein.
`
`A.
`
`PO has Failed to Overcome the Showing that Claim 1 (and 2-9, and 12-17) and
`
`Claim 25 are Unpatentable Over Ely and Fernandez (Ground 1)
`
`1. Ely alone and Ely and Fernandez show a network based server storing data
`
`digitally
`
`
`
`Claim 1 requires “a surveillance sensor appliance controlled by the (network based)
`
`server for monitoring an area and generating a signal indicating a condition in the monitored
`
`area in a programmed response mode controlled by the server, whereby the server receives
`
`and logs data transmitted by both the conventional sensor and the sensor appliance.”
`
`Claim 25 likewise requires “a plurality of sensor appliances adapted to [be] connected to a
`
`network based server for monitoring, logging, and transmitting data to the server”
`
`(parenthetical added).
`
`
`
`The POR states that Ely does not include a network based server and does not have
`
`a central storage for storing data from all cameras digitally. POR, pp. 7 and 8. In particular,
`
`PO states that the retrieved video data are recorded on a VCR, not a server or computer.
`
`POR, p. 8. These arguments are nearly verbatim repeats of the arguments made in the
`
`POPR.
`
`The Board has previously recognized that Ely individually and in combination with
`
`3
`
`
`

`
`

`

`Fernandez show a network based server. Decision, p. 18. PO has provided no new
`
`evidence or substantive arguments to rebut the Board’s decision.
`
`
`
`As Petitioner has previously demonstrated, the host computer 104 of Ely comprises
`
`hardware and software providing the same functionalities as the server in the ‘183 Patent.
`
`The host computer 104 communicates with the camera units 114 and sensor devices 120
`
`over the LAN 112. Ely, 9, 12-181; Figure 2. The camera units 114 capture and transmit
`
`(compressed) surveillance data (video data) to the host computer 104 and the host
`
`computer 104 controls the camera units 114. The host computer 104 receives the
`
`compressed video data from the camera unit 114 through the LAN 112 and provides these
`
`data in an appropriate manner to the DVTR 110 for digital recording. Ely, 16, 9-14 and 24-
`
`31. Further, the DVTR 110 or the data recorder can be considered part of the host
`
`computer 104 because it is controlled by the host computer 104. Ely, 16, 4-6 and 35-36.
`
`Finally, Fernandez teaches a central controller 6 as a network based server including a
`
`digital storage 49 for storing the data digitally. Fernandez, 2:23-272; 8:27-30; Figure 3.
`
`
`
`Accordingly, Ely and the combination of Ely and Fernandez show a network based
`
`server storing data digitally.
`
`2. Ely alone and Ely and Fernandez show receiving and logging data from both
`
`the conventional sensors and the sensor appliances.
`
`                                                            
`1 Page 9, lines 12-18
`2 Column 2, lines 23-27 
`

`
`4
`
`

`

`
`
`Claim 1 further requires “whereby the server receives and logs data transmitted by
`
`both the conventional sensor and the sensor appliance.”
`
`
`
`PO erroneously states that Ely does not show receiving and logging data from both
`
`the conventional sensors and the sensor appliances. POR, p. 8. In particular, PO contends
`
`that the lack of a server in Ely precludes logging data on a host, particularly alarm data. Id.
`
`This position is, again, nearly identical to the unpersuasive arguments raised by PO in the
`
`POPR.
`
`
`
`The Decision addresses this issue on pages 19-20 and comes to the conclusion that
`
`Ely shows a server receiving and logging data transmitted by both the conventional sensor
`
`and the sensor appliance. In the absence of any new evidence or even argument by PO,
`
`the Board’s decision should stand.
`
`
`
`As the Board has recognized, Ely shows receiving and logging alarm data on the
`
`server. In his declaration, the Expert Dr. Tal Lavian states that Ely inherently teaches a
`
`server receiving and logging conventional sensor data and video data because the main
`
`operational function of a computer in the security application environment is to receive and
`
`log alarm data, sensor data, video data and other relevant security data. Declaration
`
`(Document 4), ¶ 29. Receiving video data without knowing when, where and under what
`
`condition they were taken is useless in a security setting.
`
`
`
`Moreover, Ely expressly discloses a server as a host computer 104 and a data
`
`recorder. Ely, 16, 32-17, 2; Figure 2. The data recorder (under the control of the host
`

`
`5
`
`

`

`computer 104) records all traffic on the LAN 112 which necessarily includes also sensor
`
`data.
`
`
`
`Finally, Fernandez teaches that the storage 49 of the central controller receives and
`
`logs video and sensor data. Fernandez, 2:66-3:15; 3:23-25; 4:23-36; 6:41-44 and 16:52-56.
`
`
`
`Accordingly, Ely alone and Ely combined with Fernandez show receiving and logging
`
`data from both the conventional sensors and the sensor appliances.
`
`3. Ely shows a converter for converting the conventional sensor signal in a
`
`network based signal
`
`
`
`Claim 1 further requires “a convertor for converting the conventional sensor signal
`
`into a network compatible signal and adapted for sending the converted signal via the
`
`network to the server.”
`
`
`
`PO, without any reasoning, states that the conversion is not taught or suggested
`
`anywhere in Ely. POR, p. 12.
`
`
`
`The Decision addresses this issue on page 20 and recognizes that Ely shows a
`
`convertor for converting the conventional sensor signal into a network compatible signal.
`
`
`
`It is clear and unrebutted that an empirical (analog) sensor signal must be converted
`
`to a (digital) network based signal after it is received by a sensor to be sent over the digital
`
`network. Declaration, ¶¶ 27, 28.
`
`
`
`Accordingly, Ely shows a converter for converting the conventional sensor signal in a
`
`network based signal.
`

`
`6
`
`

`

`4. Neither Claim 1 nor Claim 25 Requires a Computer to Display Video
`
`
`
`PO states that Ely does not use a computer to display video. POR, p. 8. However,
`
`neither claim 1 nor claim 25 requires a computer displaying video. Further, as noted by the
`
`Board, one skilled in the art would recognize that Ely’s teaching of video data makes
`
`obvious that video data is transmitted to a monitor for viewing. Decision, p. 22.
`
`5. Neither Claim 1 nor Claim 25 Requires Transmission of Signals of All Cameras
`
`Simultaneously In or at Real Time
`
`
`
`PO argues a “key omission” of Ely is the ability to transmit all cameras
`
`simultaneously in or at real time. POR, p. 8. Neither claim 1 nor claim 25, however,
`
`requires transmission of signals of all cameras simultaneously in or at real time. Moreover,
`
`contrary to the contentions of PO, Ely shows real time transmission of captured video data
`
`to the central station. Ely, 12, 9-17; Block 152 of Figure 4. As also noted by the Board, Ely
`
`teaches simultaneously transmitting video data because Ely describes a conventional split
`
`screen technique including video multiplexers to display video streams from different
`
`cameras. Ely, 15, 36-16, 3; Decision, p. 19.
`
`6. Neither Claim 1 nor Claim 25 Requires Distinguishing Multiple Cameras and
`
`Multiple Sensors from One Another
`
`
`
`PO states that Ely does not disclose how each of the cameras (114) and sensors
`
`(120) provides a signal distinguishing the multiple cameras and the multiple sensors from
`7
`

`
`

`

`one another. POR, p. 12. However, neither claim 1 nor claim 25 requires a signal
`
`distinguishing the multiple cameras and the multiple sensors. Furthermore, as the Board
`
`has recognized, Ely teaches that cameras are differentiated because video data may be
`
`routed from a selected camera and that selected cameras may be instructed not to transmit
`
`video data. Decision, p. 22.
`
`7. Neither Claim 1 nor Claim 25 Requires “Full Motion Video”
`
`
`
`PO states that Ely fails to deal with full motion video. POR, p. 6. However, neither
`
`claim 1 nor claim 25 requires full motion video. Further, the Board has previously
`
`recognized that Ely’s disclosure of the H.261 video compression standard teaches full
`
`motion video to one skilled in the art. Decision, pp. 22-23.
`
`8. Claim 25 does not require storing still images.
`
`
`
`PO asserts that Ely does not anticipate claim 25 because it does not teach or
`
`suggest that both stills and video are recorded and logged. POR, p. 13. However, claim 25
`
`does not require that both stills and videos be recorded and logged.
`
`PO has Failed to Overcome the Showing that Claim 18 (and 19-23) are
`B.
`Unpatentable Over Ely, Fernandez and Imaide (Ground 2)
`1. Ely alone and Ely and Fernandez show a network based server storing data
`digitally
`Claim 18 recites in the preamble “a plurality of sensor appliances adapted to [be]
`
`
`
`connected to a network based server for monitoring, logging, and transmitting data to the
`

`
`8
`
`

`

`server” (parenthetical added). PO states with regard to both claim 18 and claim 1 that Ely
`
`does not include a network based server and does not have a central storage for storing
`
`data digitally from all cameras. POR, pp. 7 and 8. In response, Petitioner incorporates by
`
`reference the arguments provided above with respect to claim 1 at Sections A.1 and A.2.
`
`2. Ely shows (full) motion video images
`
`
`
`Claim 18 recites “a multi-function image sensor appliance adapted for generating an
`
`image signal representing the visual condition of a monitored zone of operation, the image
`
`signal comprising both still frame image data and motion video image data.” Here, PO
`
`makes contradictory statements by first asserting that Ely fails to teach full motion video and
`
`then contending that Ely stores short video clips in each camera. POR, pp. 6 and 7.
`
`Regardless, the system 100 of Ely is adapted to use the H.261 standard, which standard
`
`includes (full) motion video. Ely, 11, 33. Accordingly the cameras are adapted to generate
`
`still frame data and (full) motion video data. Declaration, ¶30.
`
`3. Claim 18 does not require storing and retrieval of still frames
`
`
`
`PO asserts, without citation or evidentiary support, that Ely does not teach collection,
`
`storing and retrieval of still frames because a VCR cannot store still frames independently of
`
`motion video. POR, p. 8.
`
`
`
`Once again, the POR provides no new evidence, citation to authority, or even new
`
`attorney argument to bolster PO’s position. Hence, PO has failed to offer any basis to
`

`
`9
`
`

`

`change the Board’s initial conclusion that Ely alone, and Ely and Fernandez, show storing
`
`and retrieval of still frames. Decision, pp. 22-23. Petitioner further notes that Ely does not
`
`only show a VCR but other image storing devices such as a DVTR. Ely, 16, 9-14 and 24-
`
`31.
`
`
`
`Moreover, claim 18 does not require collection, storing and retrieval of still frames on
`
`a server, as PO has apparently alleged. Rather, the relevant portion of claim 18 recites “a
`
`multi-function image sensor appliance adapted for generating an image signal …, the image
`
`signal comprising both still frame image data and motion video image data” and “a
`
`transmitter for sending (the?) image data (signal?) to the server” (parentheticals added).
`
`PO has failed to identify any claim element that requires a server storing or retrieving still
`
`frame data. Even when the preamble is pulled in the claim refers (only) to data being
`
`logged on the server. The preamble does not require still frame (or still frame independent
`
`of motion video) data. Rather, Ely (in combination with Fernandez and Imaide) teaches all
`
`of the claim elements actually recited in claim 18, as has been demonstrated by Petitioner.
`
`Petition, pp. 37-39.
`
`4. Other Arguments of PO with Respect to claim 18
`
`
`
`Similar to the irrelevant arguments made by PO with regard to claim 1, claim 18 does
`
`not require a “computer displaying video,” “transmission of signals of all cameras
`
`simultaneously in or at real time,” or “providing signals distinguishing the multiple cameras
`

`
`10
`
`

`

`and multiple sensors from each other.” PO’s reliance upon these non-claim elements is
`
`misplaced, as addressed above in Sections A.4-A6.
`
`PO has Failed to Overcome the Showing that Claim 25 (and 33) is Anticipated
`C.
`By Kogane (Ground 4)
`1. Kogane shows a server storing digitized video
`
`
`
`Claim 25 requires “a plurality surveillance sensor appliances controlled by the server
`
`for monitoring an area and generating a data signal indicating a condition in the monitored
`
`area controlled by the server, whereby the server receives and logs signal data.” PO
`
`contends that the control server 5 stores only meta data. POR, p. 10. This is incorrect, as
`
`the Board has previously recognized. Decision, pp. 26-27. Kogane shows a control server
`
`5 including a data base 47 for storing sets of video data from camera units 1 (1a-1c).
`
`Kogane, 6:4-8; Figure 2.
`
`2. Kogane shows a server adapted for collecting and managing data
`
`transmitted by the plurality of sensor appliances
`
`
`
`PO asserts that the control server 5 of Kogane is used to “control the camera image
`
`and video collection process, not the collection and the management of transmitted data.”
`
`POR, pp. 14-15. PO further states that the control server of Kogane” manages the way
`
`data is collected, not the way collected data is managed.” POR, p. 14. This cryptic
`
`argument is virtually unchanged from the POPR and remains unsupported by citation to
`

`
`11
`
`

`

`authority, by evidence, or by expert testimony.
`
`
`
`The plain language of claim 25 requires a server adapted for collecting and
`
`managing data (not necessarily video data) transmitted by the sensor appliances. Kogane
`
`not only shows that the control server 5 controls lens unit 21 etc. but also that it stores alarm
`
`related data and sets of video data from camera units 1 (1a-1c). Kogane, 3:66-4:2; 6:4-8.
`
`The storing of sets of alarm related data and video data certainly includes collecting and
`
`managing data transmitted by the sensor appliances. For example, control server 5 marks
`
`the video data not be searched when there is an error or to transmit alarm related data to
`
`the display terminal 4. Kogane, 6:8-21.
`
`3. Claim 25 does not require (streaming) motion video
`
`
`
`PO states that Kogane does not show any (streaming) motion video because it
`
`refers to JPEG only. POR, p. 10. Claim 25 does not require (streaming) motion video but
`
`rather “signal data.”
`
`4. Claim 25 does not require a computer displaying video
`
`
`
`PO states that Kogane does not use a computer to display video. POR, p. 10.
`
`Claim 25 does not require a computer displaying video.
`
`D.
`
`PO has Failed to Overcome the Showing that Claim 32 (and 34) is Unpatentable
`
`Over Kogane and Fernandez (Ground 5)
`

`
`12
`
`

`

`
`
`The only real new submission PO provides in the POR relative to the POPR is the
`
`discussion of Fernandez with reference to the teaching of a “dispatch generator” in claims
`
`32 and 34 (both of which depend from claim 25). POR, pp. 11-12. PO has failed, however,
`
`to distinguish claims 32 or 34 over the prior art and has instead expressly relied solely upon
`
`its arguments relating to independent claim 25 to assert patentability of claims 32 and 34.
`
`POR, p. 6. PO has simply failed to provide any evidence or rationale or citation to address,
`
`much less overcome, the decision of the Board that the combination of Kogane and
`
`Fernandez renders obvious claims 32 and 34. Decision, pp. 29-30.
`
`
`
`Furthermore, PO’s assertion that it is “speculative” whether Fernandez discloses a
`
`dispatch generator is wrong. Fernandez unequivocally teaches a surveillance system
`
`(Figure 1) that includes a tool 166 (dispatch generator) in the controller 6. Fernandez;
`
`15:18-65; Figure 3. There is no speculation that the system “may” include such a tool as
`
`PO contents; it “does” include the tool, as at least Figure 3 and the related description
`
`establish. Petitioner notes that Fernandez states that dispatch generator tool 166 “may
`
`adaptively provide positional or directional functionality.” Fernandez, 15:42-44. Hence,
`
`Fernandez establishes that some functionality of the disclosed dispatch generator is
`
`optional – but this does not make the disclosure speculative. By describing that a dispatch
`
`generator may optionally be included in the described system, Fernandez sufficiently
`
`demonstrates that the use of such a dispatch generator in a surveillance system was well
`
`known in the art at the relevant time.
`

`
`13
`
`

`

`E.
`
`PO has Failed to Articulate a Rebuttal to Petitioner’s Expert Declaration
`
`
`
`With the exception of breaking a few long paragraphs into several shorter
`
`paragraphs, PO’s challenge to the sufficiency of Dr. Lavian’s Declaration is identical to the
`
`Preliminary Response (compare POR, pp. 16-19 to POPR, pp. 13-16). This is true despite
`
`the fact that the Board explicitly cited to Dr. Lavian’s Declaration at least three times
`
`(Decision, pp. 18 and 22-24) and has both implicitly and explicitly found Dr. Lavian’s
`
`positions credible and supported. Rather than providing evidence in the form of competing
`
`expert testimony and rather than providing specific rebuttals to Dr. Lavian’s positions, PO
`
`chose to simply repeat its previous rhetoric and unsubstantiated conclusions.
`
`
`
`The Petition and supporting Declaration upon which this proceeding was initiated
`
`fully meets the required standards. In a recent decision the Federal Circuit explained:
`
`At the time [of the decision in In re Lee], we required the PTO to identify
`
`record evidence of a teaching, suggestion, or motivation to combine
`
`references because “[o]mission of a relevant factor required by precedent is
`
`both legal error and arbitrary agency action.” However, this did not preclude
`
`examiners from employing common sense. More recently [in DyStar
`
`Textilfarben GmbH v. C.H. Patrick Co., 464 F.3d 1356, 1366 (Fed.Cir.2006)],
`
`we explained that use of common sense does not require a “specific hint or
`
`suggestion in a particular reference,” only reasoned explanation that avoids
`
`conclusory generalizations.
`
`14
`

`
`

`

`Perfect Web Technologies, Inc. v. InfoUSA, Inc., 587 F.3d 1324, 1329 (Fed. Cir.
`
`2009) (citations omitted).
`
`
`
`Petitioner’s positions and supporting evidence clearly meet and arguably well
`
`exceed the standard articulated by the Federal Circuit. As but one example, Dr.
`
`Lavian states “[b]oth Ely and Fernandez relate to a surveillance system for
`
`monitoring an area by using cameras and sensors” and “[i]t would have been
`
`obvious to a person skilled in the art at the time of the invention to modify the
`
`surveillance network as taught by Ely with the surveillance network as taught by
`
`Fernandez because both references teach using known networks in the same way
`
`yielding predictable results. Such a substitution is well known, based on common
`
`sense, or the result of routine experimentation.” Declaration, ¶¶ 39 and 40.
`
`Accordingly, Dr. Lavian provides evidence that the sensors and cameras of Ely and
`
`Fernandez provide predictable use of prior art elements according to their
`
`established functions. Other examples where Petitioner and Dr. Lavian provided
`
`bases for combining references were recognized by the Board. Decision, p. 24.
`
`
`
`Rather than re-hashing unsubstantiated attorney argument, PO could have
`
`deposed Dr. Lavian to reveal any shortcomings in his testimony. Alternatively, PO
`
`could have provided an expert to challenge the findings of Dr. Lavian. However, PO
`
`decided not to do so, and hence has offered no evidence with which to rebut Dr.
`
`Lavian’s testimony.
`

`
`15
`
`

`

`F.
`
`Hindsight
`
`
`
`Finally, PO contends that Petitioner provides no explanation of a reason to combine
`
`prior art references and therefore concludes that the combination of these references is
`
`based on improper hindsight. POR, p. 19. As discussed above, and as recognized by the
`
`Board, Dr. Lavian provides sufficient and proper rationale for the asserted combination.
`
`Accordingly, the conclusions of obviousness are not based on impermissible hindsight.
`
`G.
`
`PO’s Response Includes Numerous Moot Points
`
`
`
`PO raises several moot points that are irrelevant to the Board’s Decision. For
`
`instance, PO argues references on which the Inter Partes Review was not instituted,
`
`including Bonshihara and Heggie. POR, pp. 9 and 11; Decision, p. 34. Accordingly,
`
`Petitioner need not discuss these references. Further, PO argues the application of Kogane
`
`to claims 1 and 18. POR, pp. 10 and 11. However, Petitioner did not apply and the Inter
`
`Partes Review was not instituted applying Kogane to these claims. Accordingly, Petitioner
`
`will not discuss the application of Kogane to independent claims 1 and 18.
`
`CONCLUSION
`
`
`
`For at least the foregoing reasons, Mobotix respectfully requests that the Board
`
`maintain the preliminary positions reached in the Decision and issue a final decision
`
`cancelling claims 1-25 and 32-34 of the ‘183 patent.
`

`
`16
`
`

`

`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`SLATER & MATSIL, L.L.P.
`
`/Steven H. Slater/
`Steven H. Slater
`Reg. No. 35,361
`
`/Michael Kucher/
`Michael Kucher
`Reg. No. 69,114
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2014-03-28
`Date
`
`
`
`
`
`
`
`
`
`
`2014-03-28
`
`
`Date
`
`
`
`
`
`Slater & Matsil, L.L.P.
`17950 Preston Rd.
`Suite 1000
`Dallas, TX 75252
`972-732-1001
`972-732-9218 (fax)
`
`

`
`17
`
`

`

`CERTIFICATE OF SERVICE ON PATENT OWNER
`Pursuant to 37 C.F.R. § 42.6(e), the undersigned certifies that on March 28, 2013, a
`
`complete and entire copy of Petitioner’s Reply to Patent Owner’s Response was provided
`
`via electronic mail to the Patent Owner by serving the correspondence email address of
`
`record as follows:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Robert C. Curfiss
`19826 Sundance drive
`Houston, TX 77345
`
`Email: bob@curfiss.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`SLATER & MATSIL, L.L.P.
`
`/Michael Kucher/
`Michael Kucher
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2014-03-28
`Date
`
`
`
`
`
`
`Slater & Matsil, L.L.P.
`17950 Preston Rd.
`Suite 1000
`Dallas, TX 75252
`972-732-1001
`972-732-9218 (fax)
`
`

`
`18
`
`

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