throbber
Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 1 of 7 Page ID #:1034
`Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 1 of 7 Page ID #:1034
`
`
`
`
`
`
`
`
`EXHIBIT 4
`EXHIBIT 4
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 2 of 7 Page ID #:1035
`Case 2:16-cv-00741-RWS Document 344 Filed 11/05/19 Page 1 of 13 PageID #: 7216
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`
`
`
`
`UNILOC USA, INC., et al.,
`
`Plaintiffs,
`
`v.
`
`AVG TECHNOLOGIES USA, INC.,
`KASPERSKY LAB, INC.,
`SQUARE ENIX, INC.,
`
`Defendants.
`
`UNILOC USA, INC., et al.,
`
`Plaintiffs,
`
`v.
`
`ADP, LLC,
`BIG FISH GAMES, INC.,
`
`Defendants.
`
`
`Case No. 2:16-cv-00393-RWS
`
`LEAD CASE
`
`
`
`Case No. 2:16-cv-00871-RWS
`Case No. 2:16-cv-00872-RWS
`
`
`
`
`Case No. 2:16-cv-00741-RWS
`
`LEAD CASE
`
`
`
`Case No. 2:16-cv-00858-RWS
`
`PLAINTIFFS’ MOTION TO RECONSIDER A PORTION OF THIS COURT’S
`MEMORANDUM OPINION AND ORDER CONSTRUING CERTAIN TERMS
`
`This Court issued a claim construction order (“Opinion”), Dkt. No. 2331, on August 16,
`
`2017. Shortly thereafter, Plaintiffs (“Uniloc”) filed a Motion to Reconsider a Portion of that
`
`Opinion, Dkt. No. 266, but this Court’s decision on eligibility, Dkt. No. 267, mooted that motion
`
`before Defendants could file an opposition.
`
`Uniloc now renews the portions of that previously filed motion that relate to the ’578 and
`
`’293 patents. In this Motion, Uniloc requests the Court to modify, in part, the Court’s claim
`
`construction of “application launcher program” and “application program,” as it applies to those
`
`patents.
`
`
`
`
`
`
`1 All citations in this Motion are to the docket in 2:16-cv-00741-RWS.
`
`1
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 3 of 7 Page ID #:1036
`Case 2:16-cv-00741-RWS Document 344 Filed 11/05/19 Page 2 of 13 PageID #: 7217
`
`In support of this request, Uniloc submits the accompanying declaration of Dr. Michael
`
`Shamos.2
`
`Other actions
`
`After the Federal Circuit remanded this action with respect to ’578 and ’293 patents,
`
`Uniloc 20173, the current owner, filed actions on those patents against other entities. Because of
`
`venue restrictions imposed by TC Heartland LLC v. Kraft Foods Grp. Brands LLC, 137 S. Ct.
`
`1514 (2017), those actions had to be filed in districts other than this one. Currently, actions on
`
`these patents are thus pending before eight other District Court judges.
`
`The procedure in each of those districts is to proceed to claim construction during the
`
`earlier phases of the action. However, Uniloc expects that most, perhaps all, of those courts will
`
`delay their own decision on claim construction, to await this Court’s decision on this motion.
`
`The Court should modify its construction of “application launcher program,” as to
`the ’578 patent.
`
`I.
`
`
`
`This Court construed “application launcher program” across all three patents in which it
`
`then appeared – including the ’578 patent – as “a program distributed to a client to initially
`
`populate a user desktop and to request an instance of the application for execution at the client”
`
`(emphasis added). Opinion at 27-31. Uniloc now asks the Court, with respect to claims of the
`
`’578 patent, to modify the second half of that construction to read “to request execution of the
`
`application program.”
`
`
`
`
`
`
`2 If this Court holds a hearing on the motion, Dr. Shamos will testify.
`
`3 As the Federal Circuit added Uniloc 2017 to this action as a plaintiff, Legacy Plaintiffs will
`move to add that entity’s name to the case caption.
`
`2
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 4 of 7 Page ID #:1037
`Case 2:16-cv-00741-RWS Document 344 Filed 11/05/19 Page 10 of 13 PageID #: 7225
`
`refers to, or implies, “request[ing] an instance of the application program for execution at the
`
`client,” the requirement the existing construction adds.
`
`Dr. Shamos reviewed the specification of the ’578 patent, and testifies that nothing in the
`
`specification would cause a person of skill in the art to limit the ordinary meaning of the term
`
`(¶¶ 36-49). Further, he cites specific portions of the specification that would confirm the
`
`inventors intended the ordinary meaning to apply (¶¶ 42-49).
`
`He points out the advantage of the invention of the ’578 patent is that a centralized
`
`database containing stored user and administrator preferences can be queried and updated. As he
`
`testifies, because that advantage does not depend on the whether the applications are executed at
`
`the client or the server, a POSITA would thus not have expected the inventors to limit the
`
`invention to an embodiment that executes applications only on the client, and they did not (¶ 37).
`
`Although the specification of the ’578 patent describes an “alternative embodiment” that
`
`executes an instance of the application at the client, Dr. Shamos testifies that a POSITA reading
`
`the specification and claim 1 would not read such a limitation into the ordinary meaning of the
`
`broadest claim simply because that feature is described as part of an “alternative” embodiment
`
`(¶ 40).
`
`As reflected in his testimony and the documented examples, a construction requiring
`
`execution occur only at the client does not reflect the ordinary meaning of that term.
`
`II.
`
`
`
`
`The Court should modify its construction of “application program” as to the ’578
`and ’293 patents.
`
`The Court construed “application program” to mean “the code associated with the
`
`underlying program functions that is a separate application from a browser interface and does not
`
`execute within the browser window.” Uniloc requests the Court – with respect to the ’578 and
`
`’293 patents –to modify the construction by deleting the italicized phrase.
`
`10
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 5 of 7 Page ID #:1038
`Case 2:16-cv-00741-RWS Document 344 Filed 11/05/19 Page 11 of 13 PageID #: 7226
`
`An application is software written to perform a particular function for a user -- as
`
`opposed to system software, which is designed to operate the network. Nothing in the ordinary
`
`meaning of “application,” nor any other language in the asserted claims of the ’578 and ’293
`
`patents, if given its ordinary meaning, would rule out a program executed within the browser
`
`window.
`
`
`
`The Opinion’s construction, which included “does not execute within the browser
`
`window,” seemingly applies to all four patents the Court was then considering. Opinion at 19-
`
`23. The sole stated basis for adding that phrase to the construction was that the inventors of the
`
`’466 patent, during the prosecution history of the ’466 patent, argued “an instance of the
`
`application program … executes locally at the client as a separate application from the browser
`
`interface [and] would not execute within the browser window.” Opinion at 20.
`
`
`
`The statements on which the Court relied, made during the prosecution of the ’466 patent,
`
`were intended to describe the invention of the claims of that patent, which literally require
`
`“providing an instance of the … application… to the client for execution,” seemingly ruling out -
`
`for those claims - executing an application remotely within the browser window.
`
`But, for the reasons described earlier, under Abbott Laboratories, statements in the ’466
`
`prosecution history cannot be considered at all in construing the ’578 patent.
`
`
`
`Further, because the statements appear to be simply describing features mandated by the
`
`specific limitations of the claims in the ’466 patent prosecution history, a person of skill in the art
`
`would not understand the statements of the ’466 patent inventors as applying to inventions
`
`claimed in the ’578 and ’293 patents, which do not have the features the statements describe.
`
`Because the claims of the other patents omit any requirement of providing an instance of the
`
`application for execution locally at the client, the statements the Opinion relies upon would have
`
`11
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 6 of 7 Page ID #:1039
`Case 2:16-cv-00741-RWS Document 344 Filed 11/05/19 Page 12 of 13 PageID #: 7227
`
`been untrue if they had appeared in the prosecution history of the other patents.
`
`Dr. Shamos, in his declaration (¶¶ 50-53), testifies that no portion of the ’578 patent
`
`contains, or otherwise supports, a construction of claim 1 of the ’578 patent that would exclude
`
`an application that executes within the browser window. In fact, he cited a passage from the
`
`specification (8:7-20) of that patent that describes an exemplary situation in which the
`
`application is literally executed within the browser window:
`
`It is further to be understood that, in the JAVA™ environment, currently available
`web browser applications are known to those of skill in the art which provide a
`user interface and allow hardware independent communication such as that
`currently specified by Internet protocols. Thus, the application launcher programs
`may be applets which display the icon which are associated with a web browser
`Universal Resource Locator (URL) which points to the location of the applet to be
`executed. Upon selection of the icon displayed by the application launcher, the
`selected application is “launched” by requesting the URL of the application from
`the on-demand server. Such requests may be made utilizing conventional Hyper-
`Text Transfer Protocol (HTTP) communications or other suitable protocols.
`
`Dr. Shamos further testifies:
`
`The above passage describes an exemplary situation in which the application is
`literally executed within the browser window. A Java applet is a hardware- and
`operating system-independent piece of code, written in a language known as Java
`bytecode, which is downloaded to a client and executed using software known as a
`“Java Virtual Machine” (JVM). All major browsers implemented a JVM;
`otherwise, they would not have been able to support webpages containing Java
`applets. Thus, the construction of claim 1 would not read on this embodiment.
`
`A construction that would result in no claim reading on a preferred embodiment is highly
`
`suspect. Rexnord Corp. v. Laitram Corp., 274 F.3d 1336, 1342-43 (Fed. Cir. 2001).
`
`
`
`As Dr. Shamos testifies, the claims of the ’578 patent do not exclude an application that
`
`executes within the browser window, and the specification of that patent includes an embodiment
`
`that literally executes within the browser window. Similarly, the claims of the ’293 patent7 do
`
`
`7 As to the ’293 patent, the statements, apart from being irrelevant to the invention of that patent,
`would not qualify under the Microsoft standard, dismissed earlier.
`
`12
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 62-5 Filed 11/06/20 Page 7 of 7 Page ID #:1040
`Case 2:16-cv-00741-RWS Document 344 Filed 11/05/19 Page 13 of 13 PageID #: 7228
`
`not relate at all to where or how applications are executed, but only to transmitting applications
`
`from a network management server to an intermediate server. There would have been no reason
`
`for the inventors to impose a limitation - or even to mention - a feature not in the claims, and
`
`thus irrelevant to the invention or to any art cited during the prosecution of those patents.
`
`
`
`Date: November 5, 2019
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`/s/ James J. Foster
`Paul J. Hayes
`Kevin Gannon
`James J. Foster
`Prince Lobel Tye LLP
`One International Place - Suite 3700
`Boston, MA 02110
`Tel: 617-456-8000
`Email: phayes@princelobel.com
`Email: kgannon@princelobel.com
`Email: jfoster@princelobel.com
`
`Edward R. Nelson III
`ed@nelbum.com
`Texas State Bar No. 00797142
`NELSON BUMGARDNER PC
`3131 West 7th Street, Suite 300
`Fort Worth, Texas 76107
`Phone: (817) 377-9111
`
`ATTORNEYS FOR THE PLAINTIFFS
`
`
`CERTIFICATE OF SERVICE
`
`
`
`I certify that all counsel of record who have consented to electronic service are being
`served with a copy of this document via the Court’s CM/ECF system per Local Rule CV-5(a)(3)
`on November 5, 2019.
`
`/s/ James J. Foster
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`13
`
`

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