throbber
1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`UNITED STATES DISTRICT COURT
`EASTERN DISTRICT OF TEXAS
`SHERMAN DIVISION
`
`NO.
`
`
`
`COMPLAINT
`
`DEMAND FOR JURY TRIAL
`
`ANCORA TECHNOLOGIES, INC.,
`
`
`
`
`
`Plaintiff,
`
`v.
`
`TCL CORP.,
`TCL COMMUNICATION LTD., TCL
`COMMUNICATION HOLDINGS
`LTD. AND
`TCL COMMUNICATION
`TECHNOLOGY HOLDINGS LTD.
`
`
`
`Defendants.
`
`COMPLAINT - 1
`Case No.
`
`Roku EX1022
`U.S. Patent No. 6,411,941
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`1.
`
`Plaintiff, ANCORA TECHNOLOGIES, INC. (“Ancora”), for its Complaint
`
`against TCL Corp., TCL Communication Ltd., TCL Communication Technology Holdings
`
`Ltd., (collectively “TCL”) herein, states as follows:
`
`I.
`Plaintiff Ancora Technologies, Inc. is a corporation organized and existing
`
`THE PARTIES
`
`2.
`
`under the laws of the State of Delaware and having a place of business at 23977 S.E. 10th
`
`Street, Sammamish, Washington 98075.
`3.
`
`Upon information and belief, TCL Corp. is a corporation duly organized and
`
`existing under the laws of the People’s Republic of China, having an address of No. 26, the
`
`Third Road, Zhongkai Avenue, Huizhou City, Guangdong, P.R. China 516006.
`4.
`
`Upon information and belief, TCL Communication Ltd. is a corporation duly
`
`organized and existing under the laws of the People’s Republic of China, having an address of
`
`7/F, Block F4, TCL International E City Zhong Shan Yuan Road, Nanshan District, Shenzhen
`
`China.
`
`5.
`
`Upon information and belief, TCL Communication Holdings Ltd. is a
`
`corporation existing under the laws of China, with a principal place of business at TCL Tower,
`
`15th floor, Gaoxin Nan Yi Road, Nanshan District, Shenzhen, Guangong, 518057 P.R. China.
`6.
`
`Upon information and belief, TCL Communication Technology Holdings Ltd.
`
`(“TCT”) is a corporation duly organized and existing under the laws of the People’s Republic
`
`of China, having an address of Block F4, TCL Communication Technology Building, TCL
`
`International E City, Zhong Shan Yuan Road, Nanshan District, Shenzhen, Guangdong, P.R.
`
`China, 518052.
`7.
`
`Upon information and belief, TCT is licensed to make, use, and sell Alcatel-
`
`branded mobile devices in the United States.
`
`
`
`
`
`
`
`
`COMPLAINT - 2
`Case No.
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`
`
`http://www.tctusa.com/
`
`
`
`
`
`
`
`https://us.alcatelmobile.com/about-us/
`
`
`8.
`
`Upon information and belief, TCT is licensed to make, use, and sell Blackberry-
`
`branded mobile devices in the United States.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`COMPLAINT - 3
`Case No.
`
`
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`http://www.tctusa.com/
`
`
`
`
`
`
`
`
`
`https://blackberrymobile.com/us/about-us/
`9.
`The Defendants identified in paragraphs 2-5 above are an interrelated group of
`
`companies which together comprise a manufacturer and seller of Android mobile devices in the
`
`
`
`COMPLAINT - 4
`Case No.
`
`
`
`
`
`
`
`
`

`

`
`
`United States, including Android mobile devices that are sold under the Alcatel and Blackberry
`
`brands.
`
`II.
`This is an action for infringement of United States patents arising under 35
`
`JURISDICTION
`
`10.
`
`U.S.C. §§ 271, 281, and 284–85, among others. This Court has subject matter jurisdiction of
`
`the action under 28 U.S.C. § 1331 and § 1338(a).
`11.
`
`This Court has personal jurisdiction over Defendants pursuant to due process
`
`and/or the Texas Long Arm Statute because, inter alia, (i) Defendants have done and continue
`
`to do business in Texas and (ii) Defendants have committed and continue to commit acts of
`
`patent infringement in the State of Texas, including making, using, offering to sell, and/or
`
`selling accused products in Texas, and/or importing accused products into Texas, including by
`
`Internet sales and sales via retail and wholesale stores, inducing others to commit acts of patent
`
`infringement in Texas, and/or committing a least a portion of any other infringements alleged
`
`herein. In addition, or in the alternative, this Court has personal jurisdiction over Defendants
`
`pursuant to Fed. R. Civ. P. 4(k)(2).
`12.
`
`Venue is proper in this district pursuant to 28 U.S.C. §§ 1391(b), 1391(c), and
`
`1400(b) because (i) Defendants have done and continue to do business in this district; (ii)
`
`Defendants have committed and continue to commit acts of patent infringement in this district,
`
`including making, using, offering to sell, and/or selling accused products in this district, and/or
`
`importing accused products into this district, including by internet sales and sales via retail and
`
`wholesale stores, and/or inducing others to commit acts of patent infringement in this district;
`
`and (iii) Defendants are foreign entities.
`13.
`Venue is proper as to Defendants, which are organized under the laws of the
`
`People’s Republic of China, Hong Kong, and Canada. 28 U.S.C. § 1391(c)(3) provides that “a
`
`defendant not resident in the United States may be sued in any judicial district, and the joinder
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`COMPLAINT - 5
`Case No.
`
`
`
`
`
`
`
`
`

`

`
`
`of such a defendant shall be disregarded in determining where the action may be brought with
`
`respect to other defendants.”
`
`III. BACKGROUND
`On June 25, 2002, U.S. Patent No. 6,411,941 (“the ’941 patent”) entitled
`
`14.
`
`“Method Of Restricting Software Operation Within A License Limitation” was duly and legally
`
`issued. (See Exhibit A, U.S. Patent No. 6,411,941.) A reexamination certificate also issued to
`
`the ’941 Patent on June 1, 2010 where the patentability of all claims was confirmed by the
`
`United States Patent Office. (Exhibit B, Ex Parte Reexamination Certificate Issued Under 35
`
`U.S.C. § 307.)
`15.
`
`The ‘941 patent has been involved in litigation against Microsoft Corporation,
`
`Dell Incorporated, Hewlett Packard Incorporated, and Toshiba America Information Systems.
`
`(See 2009-cv-00270, Western District of Washington).
`16.
`
`The '941 patent has also been involved in litigation against Apple Incorporated.
`
`(See 2015-cv-03659, Northern District of California).
`17.
`
`The '941 patent is currently involved in litigation against HTC America, Inc. and
`
`HTC Corporation. (See 2016-cv-01919, Western District of Washington).
`18.
`
`The '941 patent is currently involved in litigation against Samsung Electronics
`
`America, Inc. and Samsung Electronics Co., Ltd. (See 2019-cv-00385, Western District of
`
`Texas).
`19.
`
` The '941 patent is currently involved in litigation against LG Electronics USA,
`
`Inc. and LG Electronics, Inc. (See 2019-cv-00384, Western District of Texas).
`20.
`The ‘941 patent was involved in a Covered Business Method proceeding before
`
`the U.S. Patent and Trademark Office (See PTAB-CBM2017-00054). The U.S. Patent and
`
`Trademark Office denied institution of the petition filed by HTC and found the ‘941 patent
`
`recites a “technological improvement to problems arising in prior art software and hardware
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`COMPLAINT - 6
`Case No.
`
`
`
`
`
`
`
`
`

`

`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`methods of restricting an unauthorized software program’s operation.” (See PTAB-CBM2017-
`
`00054, Paper No. 7 at pg. 9).
`
`21.
`
`The U.S. Court of Appeals for the Federal Circuit further issued an order on
`
`November 16, 2018 regarding the validity of the ‘941 patent. (See CAFC 18-1404, Dkt. # 39.)
`
`In this appeal, the U.S. Court of Appeals for the Federal Circuit held:
`[T]he claimed invention moves a software-verification structure to a BIOS
`
`location not previously used for this computer-security purpose and alters how the
`
`function is performed (in that the BIOS memory used for verification now
`
`interacts with distinct computer memory to perform a software-verification
`
`function), yielding a tangible technological benefit (by making the claimed system
`
`less susceptible to hacking).
`
`CAFC 18-1404, Dkt. # 39, pg. 13.
`
`22.
`
`The U.S. Court of Appeals for the Federal Circuit further issued an order on
`
`March 3, 2014 regarding claim construction and invalidity of the ‘941 Patent. (See CAFC 13-
`
`1378, Dkt. # 57).
`23.
`
`Ancora is the owner of all right, title and interest in the ’941 patent.
`
`IV. COUNT I – PATENT INFRINGEMENT
`Ancora realleges the preceding paragraphs as though set forth fully herein.
`
`TCL has infringed the ’941 patent in violation of 35 U.S.C. § 271(a) by, prior to
`
`24.
`25.
`
`the expiration of the ’941 patent, selling, and/or offering for sale in the United States, and/or
`
`importing into the United States, without authorization, products that are capable of performing
`
`at least Claim 1 of the ’941 patent literally or under the doctrine of equivalents and/or, without
`
`authorization, causing products to perform each step of at least Claim 1 of the ’941 patent.
`26.
`Accused Products include, but are not limited to, the Alcatel 3c/33x/3v/3L;
`
`Alcatel 1c/1x/1/1t7/1T10; Alcatel A3/A3XL/A7XL/A7/A2XL/A3A; Alcatel A5; Alcatel IDOL
`
`COMPLAINT - 7
`Case No.
`
`
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`4/4S/5; Alcatel POP 4/4S/4PLUS; Alcatel PIXI 4(4)/4(5)/4(6); Blackberry KeyONE; and
`
`Blackberry Key2 (“Accused Devices”).
`
`27.
`
`Upon information and belief, TCL began selling the accused Alcatel products
`
`between 2016 - 2018.
`28.
`
`Upon information and belief, TCL began selling the Blackberry KeyONE in
`
`2017.
`
`
`
`https://blackberrymobile.com/press-room/
`
`
`
`
`
`
`
`
`
`29.
`
`Upon information and belief, TCL began selling the Blackberry Key2 in 2018.
`
`COMPLAINT - 8
`Case No.
`
`
`
`
`
`
`

`

`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`https://blackberrymobile.com/press-room/
`
`
`
`30.
`
`At a minimum, the Accused Products include servers/software utilized by TCL
`
`to transmit an over-the-air (“OTA”) software update, as well as those smartphones and other
`
`devices and technology that received from TCL, or received at TCL’s direction, an OTA update
`
`that caused such device to perform the method recited in Claim 1 prior to the expiration of the
`
`’941 patent.
`31.
`
`Such Accused Products are configured by TCL such that they are capable of
`
`performing each step of Claim 1 of the ‘941 patent and to which TCL provided one or more
`
`OTA updates before the expiration of the ‘941 patent that would cause a TCL device to
`
`perform each step of Claim 1 in order to upgrade its operating system. (See e.g.,
`
`https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1231051?make
`
`=BlackBerry&model=BBB100&gsi=mpo8f8;
`
`https://support.sprint.com/support/pages/printTemplate.jsp?articleId=WServiceAdvisory_542_
`
`GKB92134-dvc9760001prd.)
`
`
`
`
`
`COMPLAINT - 9
`Case No.
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`32.
`
`For example, Claim 1 of the ’941 patent claims “a method of restricting software
`
`operation within a license for use with a computer including an erasable, non-volatile memory
`
`area of a BIOS of the computer, and a volatile memory area; the method comprising the steps
`
`of: [1] selecting a program residing in the volatile memory, [2] using an agent to set up a
`
`verification structure in the erasable, non-volatile memory of the BIOS, the verification
`
`structure accommodating data that includes at least one license record, [3] verifying the
`
`program using at least the verification structure from the erasable non-volatile memory of the
`
`BIOS, and [4] acting on the program according to the verification.”
`
`33. When TCL transmitted an OTA update, TCL performed and/or caused to be
`
`performed each of these elements as part of what is described as “verified boot”:
`
`
`
`
`
`https://source.android.com/security/verifiedboot
`
`
`
`34.
`
`In particular, each mobile device contains both erasable, non-volatile memory in
`
`the form of ROM and volatile memory in the form of RAM.
`35.
`
`Further, each mobile device was configured by TCL to perform the below
`
`described process (or one substantially like it) in order to install an OTA update:
`
`
`
`
`
`
`
`
`
`COMPLAINT - 10
`Case No.
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`
`
`
`
`https://source.android.com/devices/tech/ota/nonab
`
`
`
`36.
`
`For example, during this process, a program running on one or more OTA
`
`servers owned and/or controlled by TCL set up a verification structure in the erasable, non-
`
`volatile memory of the BIOS of the Accused Products by transmitting to the device an OTA
`
`update. The Accused Products are then configured by TCL to save to a partition (e.g., the
`
`“cache” or “A/B” partitions) of the erasable, non-volatile memory of its BIOS.
`37.
`
`The OTA update contains a verification structure that include data
`
`accommodating at least one license record. Examples of such a license record include a
`
`cryptographic signature or key:
`
`
`
`
`
`
`
`
`
`COMPLAINT - 11
`Case No.
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`
`
`https://source.android.com/devices/tech/ota/sign_builds
`
`
`
`38.
`
`Such license record also may comprise a cryptographic hash or hash tree:
`
`
`
`
`
`https://source.android.com/security/verifiedboot/verified-boot.
`
`
`
`
`39.
`
`Once the verification structure has been set up in the BIOS, the Accused
`
`Products are configured by TCL to reboot into recovery mode, load the OTA update into its
`
`volatile memory (e.g., RAM), and use the at least one license record from the BIOS to verify
`
`the OTA update.
`
`COMPLAINT - 12
`Case No.
`
`
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`40.
`
`If the OTA update is verified, the Accused Products are configured to load and
`
`execute the update.
`
`41.
`
`In sum, as described above, once TCL has set up the verification structure by
`
`transmitting to a device an OTA update, each Accused Product is configured to automatically
`
`perform each of the remaining Claim 1 steps.
`42.
`
`Further, on information and belief, when TCL provided OTA updates, TCL
`
`performed or caused to be performed each of the Claim 1 steps.
`43.
`
`Further, TCL conditions participation in the OTA update process and the receipt
`
`of the benefit of a software update on the performance of each of the above steps.
`44.
`
`Primarily, as described above, TCL pre-configures/programs each Accused
`
`Product to perform the above described steps upon receiving an OTA update from TCL.
`45.
`
`Further, TCL takes steps to ensure that each Accused Product cannot install an
`
`OTA update except by performing each of the above described steps.
`46.
`
`Further, TCL emphasizes the benefits associated with updating the software of
`
`its Accused Products.
`47.
`
`Further, TCL controlled the manner of the performance of such method. As set
`
`forth above, TCL configured each Accused Product such that, upon receiving an OTA update,
`
`it would automatically perform each remaining step of the claimed method.
`48.
`
`TCL also controlled the timing of the performance of such method by
`
`determining when to utilize its OTA servers/software to set up a verification structure in each
`
`Accused Product.
`49.
`
`TCL also had the right and ability to stop or limit infringement simply by not
`
`performing the initial step of using its OTA servers/software to set up a verification structure in
`
`each Accused Product. Absent this action by TCL, the infringement at issue would not have
`
`occurred.
`
`COMPLAINT - 13
`Case No.
`
`
`
`
`
`
`
`
`

`

`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`
`
`50.
`
`TCL’s infringement has caused damage to Ancora, and Ancora is entitled to
`
`recover from TCL those damages Ancora has sustained as a result of TCL’s infringement.
`
`V.
`
`DEMAND FOR RELIEF
`
`WHEREFORE, Plaintiff prays for judgment as follows:
`
`A.
`
`Declaring that TCL has infringed United States Patent No. 6,411,941 in violation
`
`of 35 U.S.C. § 271;
`
`B.
`
`Awarding damages to Ancora arising out of this infringement, including enhanced
`
`damages pursuant to 35 U.S.C. § 284 and prejudgment and post-judgment interest, in an amount
`
`according to proof;
`
`C.
`
`Awarding such other costs and relief the Court deems just and proper, including
`
`any relief that the Court may deem appropriate under 35 U.S.C. § 285.
`
`VI. DEMAND FOR JURY TRIAL
`Ancora respectfully demands a trial by jury of any and all issues triable of right by a
`
` SIEBMAN FORREST BURG
`
` & SMITH, LLP
`
` Federal Courthouse Square
`
` 300 N. Travis
`
` Sherman, TX 75090
`
` (903) 870-0070
`
` (903) 870-0066 Telefax
`
` Clyde M. Siebman
`
` Texas State Bar #18341600
`
` clydesiebman@siebman.com
`
` Elizabeth S. Forrest
`
` Texas State Bar #24086207
`
` elizabethforrest@siebman.com
`
`jury in the above-captioned action.
`
`DATED: August 27, 2019
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`COMPLAINT - 14
`Case No.
`
`
`
`
`
`
`
`
`
`
`
`
` By: /s/ Clyde M. Siebman
` Clyde M. Siebman
`
`
`
`
`
`
`

`

`
`
`
`
`
`
`BROOKS KUSHMAN P.C.
`John P. Rondini (pending admission pro hac vice)
`Mark A Cantor (pending admission pro hac vice)
`John S. LeRoy (pending admission pro hac vice)
`Marc Lorelli (pending admission pro hac vice)
`1000 Town Center, 22nd Floor
`Southfield, Michigan 48075-1238
`Tel.: (248) 358-4400
`Fax: (248) 358-3351
`Email: jrondini@brookskushman.com
`
` mcantor@brookskushman.com
`jleroy@brookskushman.com
`mlorelli@brookskushman.com
`
`
`Attorneys for Plaintiff Ancora Technologies, Inc.
`
`
`
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`COMPLAINT - 15
`Case No.
`
`
`
`
`
`
`
`
`

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