throbber
Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 1 of 14 PageID #: 1
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`UNILOC 2017 LLC
`
` Plaintiff,
`
`
`v.
`
`KASPERSKY LAB, INC.,
`
` Defendants.
`









`
`
`
`CIVIL ACTION NO. 2:19-cv-00219
`
`
`PATENT CASE
`
`
`JURY TRIAL DEMANDED
`
`ORIGINAL COMPLAINT FOR PATENT INFRINGEMENT
`
`
`
`1.
`
`Plaintiff Uniloc 2017 LLC (together “Uniloc”), as and for their complaint against
`
`defendants, Kaspersky Lab, Inc. (“Kaspersky”), allege as follows:
`
`2.
`
`Uniloc is a Delaware limited liability company having places of business at 620
`
`THE PARTIES
`
`Newport Center Drive, Newport Beach, California 92660 and 102 N. College Avenue, Suite 303,
`
`Tyler, Texas 75702.
`
`3.
`
`4.
`
`Uniloc holds all substantial rights, title and interest in and to the asserted patent.
`
`Upon information and belief, Kaspersky Lab is a Massachusetts corporation with
`
`its principal place of business at 500Unicorn Park, 3rd Floor, Woburn, MA 01801 and offers its
`
`products and/or services, including those accused herein of infringement, for purchase or download
`
`to customers and/or potential customers located in Texas and in the judicial Eastern District of
`
`Texas.
`
`
`
`JURISDICTION AND VENUE
`
`5.
`
`Uniloc brings this action for patent infringement under the patent laws of the United
`
`States, 35 U.S.C. § 271 et seq. This Court has subject matter jurisdiction pursuant to 28 U.S.C. §§
`
`
`
`1
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 2 of 14 PageID #: 2
`
`1331, 1338(a) and 1367.
`
`6.
`
`Venue is proper in this Court pursuant to 28 U.S.C. §§ 1391 and 1400(b). Kaspersky
`
`is registered to do business in Texas, has transacted business in this District, and has committed
`
`acts of direct and indirect infringement in this District.
`
`7.
`
`Kaspersky is subject to this Court’s jurisdiction pursuant to due process and/or the
`
`Texas Long Arm Statute due at least to its substantial business in this State and judicial district,
`
`including: (A) at least part of its past infringing activities, (B) regularly doing or soliciting business
`
`in Texas and/or (C) engaging in persistent conduct and/or deriving substantial revenue from goods
`
`and services provided to customers in Texas.
`
`COUNT I
`(INFRINGEMENT OF U.S. PATENT NO. 6,324,578)
`
`
`Uniloc incorporates by reference the preceding paragraphs.
`
`U.S. Patent No. 6,324,578 (“the ‘578 Patent”), entitled METHODS, SYSTEMS
`
`8.
`
`9.
`
`AND COMPUTER PROGRAM PRODUCTS FOR MANAGEMENT OF CONFIGURABLE
`
`APPLICATION PROGRAMS ON A NETWORK that issued on November 27, 2001. A true and
`
`correct copy of the ‘578 Patent is attached as Exhibit A hereto.
`
`10.
`
`Pursuant to 35 U.S.C. § 282, the ’578 Patent is presumed valid. The ’578 Patent
`
`describes inventive features that are not well-understood, routine, and conventional.
`
`11.
`
`The ‘578 Patent has been referenced by over one-hundred forty other patent
`
`applications/patents including patents applications/patents by IBM, Microsoft, Lucent, Netscape,
`
`General Electric, Hewlett Packard, Cisco, SAP, and Siemens.
`
`12.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`
`
`2
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 3 of 14 PageID #: 3
`
`Source: https://my.kaspersky.com
`
`
`
`
`
`13.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`
`Source: https://blog.kaspersky.com/my-kaspersky-tip-of-the-week/7131/
`
`
`
`
`
`3
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 4 of 14 PageID #: 4
`
`
`
`14.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`15.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`
`
`
`
`4
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 5 of 14 PageID #: 5
`
`Source: https://youtu.be/HuJDh7gauQI
`
`
`
`
`
`16.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`
`
`5
`
`
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 6 of 14 PageID #: 6
`
`17.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`18.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`
`
`
`
`6
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 7 of 14 PageID #: 7
`
`Source: https://my.kaspersky.com/mac/forms
`
`
`
`
`
`19.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`20.
`
`Upon information and belief, the following describes, at least in part, how certain
`
`aspects of a representative sample of Kaspersky’s software licensing and delivery system work:
`
`
`
`7
`
`
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 8 of 14 PageID #: 8
`
`21.
`
`Kaspersky has directly infringed, and continues to directly infringe one or more
`
`
`
`claims of the ‘578 Patent, including at least claim 1, in this judicial district and elsewhere in Texas,
`
`literally and/or under the doctrine of equivalents, by or through making, using, importing, offering
`
`for sale and/or selling its software licensing and delivery system during the pendency of the ‘578
`
`Patent which software and associated backend server architecture inter alia allows for installing
`
`application programs having a plurality of configurable preferences and authorized users on a
`
`network, distributing an application launcher program to a user, the user obtaining a set of
`
`configurable preferences, obtaining an administrator set of configurable preferences and executing
`
`the application program using the user and administrator sets of configurable preferences
`
`responsive to a request from a user.
`
`22.
`
`In addition, should Kaspersky’s software licensing and delivery system be found to
`
`not literally infringe one or more claims of the ‘578 Patent, Kaspersky’s products would
`
`nevertheless infringe one or more claims of the ‘578 Patent under the doctrine of equivalents. More
`
`specifically, the accused software/system performs substantially the same function (making
`
`computer games available for digital download/management), in substantially the same way (via a
`
`client/server environment), to yield substantially the same result (distributing application programs
`
`to a target on-demand server on a network). Kaspersky would thus be liable for direct infringement
`
`under the doctrine of equivalents.
`
`23.
`
`Kaspersky has indirectly infringed and continues to indirectly infringe one or more
`
`claims of the ‘578 Patent, including at least Claim 1, in this judicial district and elsewhere in Texas,
`
`by actively inducing the using, offering for sale, or selling of the Kaspersky software licensing and
`
`delivery system. Kaspersky’s customers and/or agents who operate on behalf of Kaspersky and
`
`who use the Kaspersky software licensing and delivery system in accordance with Kaspersky’s
`
`
`
`8
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 9 of 14 PageID #: 9
`
`instructions directly infringe the foregoing claims of the ‘578 Patent, in violation of 35 U.S.C. §
`
`271. Kaspersky intentionally instructs its customers and/or agents to infringe through training
`
`videos, demonstrations, brochures, and installation and user guides for the software and system.
`
`24.
`
`Kaspersky is thereby liable for infringement of the ‘578 Patent under 35 U.S.C. §
`
`271(b).
`
`25.
`
`Kaspersky has indirectly infringed and continues to indirectly infringe one or more
`
`claims of the ‘578 Patent, including at least Claim 1, in this judicial district and elsewhere in Texas,
`
`by, among other things, contributing to the direct infringement by others including customers
`
`and/or agents using the Kaspersky software licensing and delivery system, by making, offering to
`
`sell, and selling a component of a patented machine, manufacture, or combination, or an apparatus
`
`for use in practicing a patented process, constituting a material part of the invention, knowing the
`
`same to be especially made or especially adapted for use in infringing the ‘578 Patent and not a
`
`staple article or commodity of commerce suitable for substantial non-infringing use.
`
`26.
`
`For example, the Kaspersky software is a component of a patented machine,
`
`manufacture, or combination, or an apparatus for use in practicing a patented process. Furthermore,
`
`the Kaspersky software licensing and delivery system is a material part of the claimed inventions
`
`and is not a staple article or commodity of commerce suitable for substantial non-infringing use.
`
`Kaspersky is, therefore, liable for infringement under 35 U.S.C. § 271(c).
`
`27.
`
`Kaspersky will have been on notice of the ‘578 Patent since, at the latest, the service
`
`of the complaint upon it in Uniloc USA, Inc. et al v. Kaspersky America, Inc., Case No. 2:16-cv-
`
`871 in the Eastern District of Texas. By the time of trial, Kaspersky will have known and intended
`
`(since receiving such notice) that its continued actions would actively induce, and contribute to,
`
`the infringement of one or more claims of the ‘578 Patent.
`
`
`
`9
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 10 of 14 PageID #: 10
`
`28.
`
`Kaspersky may have infringed the ‘578 Patent through other software utilizing the
`
`same or reasonably similar functionality, including other versions of its software licensing and
`
`delivery system. Uniloc reserves the right to discover and pursue all such additional infringing
`
`software.
`
`
`
`COUNT II
`(INFRINGEMENT OF U.S. PATENT NO. 7,069,293)
`
`29.
`
`Uniloc incorporates the paragraphs above by reference.
`
`30.
`
`U.S. Patent No. 7,069,293 (“the ‘293 Patent”), entitled METHODS, SYSTEMS
`
`AND COMPUTER PROGRAM PRODUCTS FOR DISTRIBUTION OF APPLICATION
`
`PROGRAMS TO A TARGET STATION ON A NETWORK that issued on June 27, 2006. A true
`
`and correct copy of the ‘293 Patent is attached as Exhibit B hereto.
`
`31.
`
`Pursuant to 35 U.S.C. § 282, the ’293 Patent is presumed valid. The ’293 Patent
`
`describes inventive features that are not well-understood, routine, and conventional.
`
`32.
`
`The ‘293 Patent has been referenced by over eighty other patent applications/patents
`
`including patents applications/patents by Cisco, AT&T, Microsoft, AOL, SAP, and Samsung.
`
`33.
`
`Kaspersky has directly infringed, and continues to directly infringe one or more
`
`claims of the ‘293 Patent, including at least Claim 1, in this judicial district and elsewhere in Texas,
`
`literally and/or under the doctrine of equivalents, by or through making, using, importing, offering
`
`for sale and/or selling its software licensing and delivery system during the pendency of the ‘293
`
`Patent which software and associated backend server architecture inter alia allow for providing an
`
`application program for distribution to a network server, specifying source and target directories
`
`for the program to be distributed, preparing a file packet associated with the program including a
`
`segment configured to initiate registration and distributing the file packet to the target on-demand
`
`
`
`10
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 11 of 14 PageID #: 11
`
`server to make the program available for use by a client user.
`
`34.
`
`In addition, should Kaspersky’s software licensing and delivery system be found to
`
`not literally infringe one or more claims of the ‘293 Patent, Kaspersky would nevertheless infringe
`
`one or more claims of the ‘293 Patent under the doctrine of equivalents. More specifically, the
`
`accused software licensing and delivery system performs substantially the same function
`
`(distributing application programs to a target on-demand server on a network), in substantially the
`
`same way (via a client/server environment to target on-demand users), to yield substantially the
`
`same result (making application programs available for use by target on-demand users). Kaspersky
`
`would thus be liable for direct infringement under the doctrine of equivalents.
`
`35.
`
`Kaspersky has indirectly infringed and continues to indirectly infringe one or more
`
`claims of the ‘293 Patent, including at least Claim 1, in this judicial district and elsewhere in Texas,
`
`by actively inducing the using, offering for sale, or selling of the Kaspersky software licensing and
`
`delivery system. Kaspersky’s customers and/or agents who operate on behalf of Kaspersky who
`
`use the Kaspersky software licensing and delivery system in accordance with Kaspersky’s
`
`instructions directly infringe the foregoing claims of the ‘293 Patent, in violation of 35 U.S.C. §
`
`271. Kaspersky intentionally instructs its customers and/or agents to infringe through training
`
`videos, demonstrations, brochures, and installation and user guides for the software and system.
`
`36.
`
`Kaspersky is thereby liable for infringement of the ‘293 Patent under 35 U.S.C. §
`
`271(b).
`
`37.
`
`Kaspersky has indirectly infringed and continues to indirectly infringe one or more
`
`claims of the ‘293 Patent, including at least Claim 1, in this judicial district and elsewhere in Texas,
`
`by, among other things, contributing to the direct infringement by others including customers
`
`and/or agents using the Kaspersky software licensing and delivery system, by making, offering to
`
`
`
`11
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 12 of 14 PageID #: 12
`
`sell, and selling a component of a patented machine, manufacture, or combination, or an apparatus
`
`for use in practicing a patented process, constituting a material part of the invention, knowing the
`
`same to be especially made or especially adapted for use in infringing the ‘293 Patent and not a
`
`staple article or commodity of commerce suitable for substantial non-infringing use.
`
`38.
`
`For example, the Kaspersky software is a component of a patented machine,
`
`manufacture, or combination, or an apparatus for use in practicing a patented process. Furthermore,
`
`the Kaspersky software licensing and delivery system is a material part of the claimed inventions
`
`and is not a staple article or commodity of commerce suitable for substantial non-infringing use.
`
`Kaspersky is, therefore, liable for infringement under 35 U.S.C. § 271(c).
`
`39.
`
`Kaspersky will have been on notice of the ‘293 Patent since, at the latest, the service
`
`of the complaint upon it in Uniloc USA, Inc. et al v. Kaspersky Lab, Inc., Case No. 2:16-cv-871 in
`
`the Eastern District of Texas. By the time of trial, Kaspersky will have known and intended (since
`
`receiving such notice) that its continued actions would actively induce, and contribute to, the
`
`infringement of one or more claims of the ‘293 Patent.
`
`40.
`
`Kaspersky may have infringed the ‘293 Patent through other software utilizing the
`
`same or reasonably similar functionality, including other versions of its software licensing and
`
`delivery system. Uniloc reserves the right to discover and pursue all such additional infringing
`
`software.
`
`
`
`
`PRAYER FOR RELIEF
`
`Uniloc requests that the Court enter judgment against Kaspersky as follows:
`
`(A)
`
`that Kaspersky has infringed the ‘578 Patent and the ‘293 Patent;
`
`(B)
`
`awarding Uniloc its damages suffered as a result of Kaspersky’ infringement of
`
`the ‘578 Patent and the ‘293 Patent pursuant to 35 U.S.C. § 284;
`
`
`
`12
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 13 of 14 PageID #: 13
`
`(C)
`
`enjoining Kaspersky, its officers, directors, agents, servants, affiliates, employees,
`
`divisions, branches, subsidiaries and parents, and all others acting in concert or privity with it
`
`from infringing the ‘578 Patent and the ‘293 Patent pursuant to 35 U.S.C. § 283;
`
`awarding Uniloc its costs, attorneys’ fees, expenses, and interest, and
`
`granting Uniloc such other and further relief as the Court may deem just and
`
`(D)
`
`(E)
`
`proper.
`
`
`
`
`
`
`
`
`DEMAND FOR JURY TRIAL
`
`
`
`Uniloc hereby demands trial by jury on all issues so triable pursuant to Fed. R. Civ. P.
`
`38.
`
`
`
`13
`
`

`

`Case 2:19-cv-00219-JRG Document 1 Filed 06/12/19 Page 14 of 14 PageID #: 14
`
`Dated:
`
`June 12, 2019
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`/s/ James L. Etheridge
`
`James L. Etheridge
`Texas State Bar No. 24059147
`Ryan S. Loveless
`Texas State Bar No. 24036997
`Brett A. Mangrum
`Texas State Bar No. 24065671
`Travis L. Richins
`Texas State Bar No. 24061296
`Jeff Huang
`
`ETHERIDGE LAW GROUP, PLLC
`2600 E. Southlake Blvd., Suite 120 / 324
`Southlake, Texas 76092
`Telephone: (817) 470-7249
`Facsimile: (817) 887-5950
`Jim@EtheridgeLaw.com
`Ryan@EtheridgeLaw.com
`Brett@EtheridgeLaw.com
`Travis@EtheridgeLaw.com
`Jeff@EtheridgeLaw.com
`
`Counsel for Plaintiff Uniloc 2017 LLC
`
`14
`
`
`

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