throbber
Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 1 of 16 PageID #: 7700
`
`INC., and UNILOC
`UNILOC USA,
`LUXEMBOURG, S.A.,
`
`
`
`v.
`
`ADP, LLC, and BIG FISH GAMES, INC.
`
`
`
`
`INC., and UNILOC
`UNILOC USA,
`LUXEMBOURG, S.A.,
`
`
`
`v.
`
`INC.,
`AVG TECHNOLOGIES USA,
`KASPERSKY LAB, INC., SQUARE ENIX,
`INC.,
`
`
`
`
`Plaintiffs,
`
`Defendant.
`
`Plaintiffs,
`
`Defendant.
`
`
`
`
`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
























`
`
`ORDER
`
`
`
`CIVIL ACTION NO. 2:16-CV-00741-RWS
`(LEAD CASE)
`
`
`
`CIVIL ACTION NO. 2:16-CV-00393-RWS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Before the Court are three motions: Plaintiffs Uniloc USA, Inc. and Uniloc Luxembourg,
`
`S.A.’s Motion for Discovery (Docket No. 3311), Defendant Big Fish Games’s Motion to Strike
`
`Plaintiffs’ Infringement Contentions (Docket No. 335) and Plaintiffs’ Motion to Reconsider a
`
`Portion of this Court’s Memorandum Opinion and Order Construing Certain Terms (Docket No.
`
`344). The Court heard argument on the motions on January 28, 2020.
`
`
`1 Citations are to the docket in the lead case, No. 2:16-cv-741.
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 2 of 16 PageID #: 7701
`
`For the reasons set forth below, Uniloc’s Motion for Discovery is DENIED, Big Fish’s
`
`Motion to Strike is GRANTED-IN-PART and DENIED-IN-PART, and Uniloc’s Motion to
`
`Reconsider is DENIED.
`
`BACKGROUND
`
`In April 2016, Uniloc2 filed a series of cases in this Court asserting U.S. Patent Nos.
`
`6,410,466 and 6,728,766 against several defendants. Those cases were consolidated under Uniloc
`
`USA, Inc. v. AVG Technologies USA, Inc., Case No. 2:12-cv-393 (E.D. Tex.). Shortly thereafter,
`
`Uniloc filed another series of cases against multiple defendants, including Big Fish, asserting
`
`different combinations of the ʼ466 and ʼ766 patents as well as U.S. Patent Nos. 6,324,578 and
`
`7,069,293. See Uniloc USA, Inc. v. Big Fish Games, Inc., Case No. 2:16-cv-858 (E.D. Tex.). This
`
`second round of cases was consolidated under the above-captioned lead case. Defendants ADP
`
`and Big Fish each filed motions to dismiss Uniloc’s complaint for failure to state a claim. Docket
`
`Nos. 17, 80. The Court held a joint Markman hearing on August 10, 2017 (Docket No. 225),
`
`entered its claim construction order on August 16, 2017 (Docket No. 233), and on September 28,
`
`2017, granted the motions to dismiss (Docket No. 267). The Court found that the asserted claims
`
`of all four patents-in-suit were drawn to patent-ineligible subject matter. Docket No. 267 at 3.
`
`Uniloc appealed. Docket No. 271. The Federal Circuit affirmed the Court’s determination
`
`that the asserted claims of the ’466 and ’766 patents were drawn to patent-ineligible subject matter
`
`but reversed as to the ’578 and ’293 patents and remanded. Docket No. 317 at 3. The parties’
`
`motions seek to define how the case will proceed.
`
`
`2 “Uniloc” refers collectively to Plaintiffs Uniloc USA, Inc. and Uniloc Luxembourg, S.A. During
`the appeal to the Federal Circuit, a third entity, Uniloc 2017, acquired an interest in the patents-
`in-suit. See Docket No. 232 at 3–4. The Federal Circuit substituted Uniloc 2017 as a party, id.,
`but as of the date of this order, Uniloc 2017 has not been added to this lawsuit.
`
`Page 2 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 3 of 16 PageID #: 7702
`
`I.
`
`Uniloc’s Motion for Discovery (Docket No. 331)
`
`DISCUSSION
`
`Uniloc seeks to reopen fact discovery for 90 days, with renewed expert discovery deadlines
`
`to follow thereafter. See Docket No. 331 at 2. Uniloc contends that reopening discovery without
`
`limitation is appropriate because, first, circumstances have changed since the Court dismissed the
`
`case more than two years ago, and second, the parties were unable to agree on any boundaries to
`
`post-remand discovery. Id. at 3–6. In Uniloc’s view, the following changed circumstances render
`
`unfettered fact discovery appropriate: (1) Uniloc 2017’s acquisition of the patents-in-suit and
`
`Aristocrat Technologies’ 2018 acquisition of Big Fish; (2) the Federal Circuit’s characterization
`
`of the subject matter of the patents and the expiration of the ’578 patent; and (3) possible changes
`
`to the accused systems during the pendency of the appeal. Id. at 3–4. Uniloc further contends that
`
`neither party found the other’s discovery proposal workable, so the Court should reopen discovery
`
`and allow the parties to explore topics as they see fit. Id. at 4–7.
`
`Big Fish opposes Uniloc’s request and characterizes it as an attempt to obtain a “do-over”
`
`of fact discovery. Docket No. 332 at 1. Big Fish argues that Uniloc’s request contravenes this
`
`Court’s instructions that the parties meet and confer on specific areas of discovery agreement and
`
`that Uniloc file a motion seeking discovery that the parties could not agree on. Id. at 1–3. Big
`
`Fish contends that Uniloc has not only failed to establish good cause for reopening discovery but
`
`that it also did not even acknowledge the correct governing standard. Id. at 3–4. And in Big Fish’s
`
`view, Uniloc’s “changed circumstances” do not justify reopening discovery. Big Fish argues that
`
`(1) the parties have not changed in a manner that would justify unfettered discovery because
`
`Aristocrat Technologies is not a party to the case; (2) the situation of the patents has not changed
`
`and the expiration of the ’578 patent simplifies the case; and (3) any changes to the accused system
`
`do not justify unrestricted discovery. Id. at 5–6. Finally, Big Fish contends that Uniloc
`
`Page 3 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 4 of 16 PageID #: 7703
`
`misrepresents the parties’ discussions leading up to Uniloc’s motion and that Uniloc in fact
`
`demonstrated an unwillingness to negotiate. Id. at 6–7.
`
`A.
`
`Applicable Law
`
`A party seeking leave to amend a court’s scheduling order or, as here, reopen fact discovery
`
`must show “good cause.” FED. R. CIV. P. 16(b); S & W Enters., L.L.C. v. Southtrust Bank of
`
`Alabama, NA, 315 F.3d 533, 535 (5th Cir. 2003). The “good cause standard requires the party
`
`seeking relief to show that the deadlines cannot reasonably be met despite the diligence of the
`
`party needing the extension.” S & W Enters., L.L.C., 315 F.3d at 535 (internal quotations omitted).
`
`Trial courts have broad discretion to allow scheduling order modifications and should consider
`
`four elements when determining whether to allow a modification: (1) the explanation for the failure
`
`to meet the deadline; (2) the importance of the thing that would be excluded; (3) potential prejudice
`
`in allowing the thing that would be excluded; and (4) the availability of a continuance to cure such
`
`prejudice. Id. at 535–36. Under the first element, a party's failure to meet a deadline due to mere
`
`inadvertence “is tantamount to no explanation at all.” Id. at 536.
`
`B.
`
`Analysis
`
`Uniloc has not shown that good cause exists to reopen discovery. In fact, Uniloc has not
`
`applied the above factors to its request. See generally Docket Nos. 331, 333. This is not to say
`
`that the case should proceed without any discovery. Though neither party acknowledged it in their
`
`briefing, both parties are obligated to supplement written discovery and document productions
`
`throughout the case. See FED. R. CIV. P. 26(e) (applying to written discovery); Docket No. 106 at
`
`¶ 8 (extending duty to supplement to document production). The discovery order requires the
`
`parties to produce materials “relevant to the pleaded claims or defenses involved in this action” or
`
`that are the basis for any computation of damages. Docket No. 106 at ¶¶ 3(b), (c). The correct
`
`analysis, therefore, is to examine whether Uniloc has shown good cause for discovery beyond
`
`Page 4 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 5 of 16 PageID #: 7704
`
`supplementation of past discovery. It has not. Aristocrat Technologies is not a party to this case,
`
`but if its acquisition of Big Fish in 2018 produced material relevant to damages, Big Fish must
`
`produce that information. Claim construction is closed, and Uniloc does not explain how the
`
`Federal Circuit’s characterization of the patents is relevant to this action. Further, the expiration
`
`of the ’578 patent only affects the damages period. Finally, material detailing changes to the
`
`accused systems would also fall under Big Fish’s duty to supplement.
`
`In its reply, Uniloc proposed an alternative approach to discovery focused on discrete
`
`topics. See Docket No. 333 at 4. While the Court does not ordinarily consider arguments raised
`
`for the first time in a reply brief, Intellectual Ventures II LLC v. Sprint Spectrum, L.P., No. 2:17-
`
`cv-00662, 2019 WL 2959568, at *3 (E.D. Tex. Apr. 18, 2019), the Court notes that, if the topics
`
`Uniloc proposes are relevant to the pleaded claims or defenses or to damages computations, they
`
`would fall under the parties’ duty to supplement.
`
`Ultimately, Uniloc has not shown good cause for discovery beyond supplementation.
`
`Uniloc’s request is therefore DENIED. The parties are ORDERED to supplement their document
`
`production and written discovery responses within 21 days of the date of this order. The parties
`
`must produce any material relevant to the action, regardless of date. To account for relevant
`
`changes in the accused products and/or damages computations, the parties are further ORDERED
`
`to supplement their opening expert reports 21 days after the deadline for discovery
`
`supplementation. The parties shall submit to the Court a proposed amended Docket Control Order
`
`within seven days of the date of this order, incorporating the dates set forth below.
`
`II.
`
`Big Fish’s Motion to Strike Infringement Contentions (Docket No. 335)
`
`Big Fish moves to strike the portions of Uniloc’s Supplemental Infringement Contentions
`
`(“SICs”) that are directed to means-plus-function claims and Uniloc’s Final Infringement
`
`Contentions (“FICs”) in their entirety. Big Fish contends that the SICs do not comply with Local
`
`Page 5 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 6 of 16 PageID #: 7705
`
`Patent Rule 3-1(c) because the charts do not include the algorithms disclosed in the patents’
`
`specifications for performing the claimed functions. Id. at 10–12. Absent this information, Big
`
`Fish argues, the SICs fail to put Big Fish on notice of Uniloc’s infringement theories. Id. at 12.
`
`Big Fish next contends that the FICs should be stricken because they are untimely, include new
`
`theories of infringement and Uniloc never sought leave to amend. Docket No. 335 at 16–17. Big
`
`Fish asserts that Uniloc cannot show good cause to amend because Uniloc had no basis for serving
`
`new contentions two months after reviewing Big Fish’s source code, striking the contentions
`
`would not be fatal to Uniloc’s case, Big Fish is prejudiced by being forced to defend against new
`
`theories and a continuance would not be appropriate. Id. at 17–18.
`
`In response, Uniloc argues that P.R. 3-1(c) only requires that the SICs identify structure in
`
`the Accused Instrumentalities. Docket No. 339 at 15. Uniloc points to the claim construction
`
`deadlines, which are later than those for infringement contentions, for support. Id. (citing P.R. 4-
`
`1(a) and 4-2). Uniloc further argues that its FICs were properly submitted pursuant to the
`
`discovery order because Big Fish’s delayed discovery rendered Uniloc unable to confirm how the
`
`source code operated until well after the 30-day window had closed. Docket No. 339 at 15–16.
`
`Uniloc also argues that, under P.R. 3-6(a), it had until September 15, 2017, to supplement its
`
`contentions and did so only seven days later. Id. at 16. Uniloc further contends that, because the
`
`FICs were “part and parcel” of Uniloc’s opening expert reports, they contained more detail than
`
`necessary. Id. at 17. Finally, Uniloc argues that the four good-cause factors favor Uniloc: Big
`
`Fish’s discovery behavior caused all of Uniloc’s delays; Uniloc provided the FICs out of an
`
`abundance of caution; Big Fish is not prejudiced because it has possessed the FICs for more than
`
`two years; and a continuance is available because this case is not on a schedule. Id. at 17–19.
`
`Page 6 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 7 of 16 PageID #: 7706
`
`A.
`
`Applicable Law
`
`This District’s Patent Rules require plaintiffs to serve infringement contentions at the outset
`
`of a case. See P.R. 3-1. The contentions must include “[a] chart identifying specifically where
`
`each element of each asserted claim is found within each Accused Instrumentality, including for
`
`each element that such party contends is governed by 35 U.S.C. § 112(6), the identity of the
`
`structure(s), act(s), or material(s) in the Accused Instrumentality that performs the claimed
`
`function.” P.R. 3-1(c). With narrow exceptions, the patent owner may amend its infringement
`
`contentions only by order of the Court upon a showing of “good cause.” P.R. 3-6(b); see also
`
`Keranos, LLC v. Silicon Storage Tech., Inc., 797 F.3d 1025, 1035 (Fed. Cir. 2015). The Court
`
`determines whether the plaintiff has shown good cause to amend by considering the four factors
`
`set forth above in Section I.A. See Harris Corp. v. Huawei Device USA, Inc., Civil Action No.
`
`2:18-cv-439, 2019 WL 4247067, at *1 (E.D. Tex. Sept. 6, 2019).
`
`B.
`
`Analysis
`
`1.
`
`The Supplemental Infringement Contentions Are Sufficient
`
`The SICs comply with the Patent Rules. When asserted claims include means-plus-
`
`function terms, infringement contentions must identify “the structure(s), act(s), or material(s) in
`
`the Accused Instrumentality that performs the claimed function.” P.R. 3-1(c) (emphasis added).
`
`The SICs do so. Nothing in P.R. 3-1(c)’s plain language requires Uniloc to tie the structure(s),
`
`act(s), or material(s) in the Accused Instrumentalities to the patent’s specification. See id. The
`
`SICs provide notice to Big Fish by identifying what aspect of the Big Fish products Uniloc
`
`contends infringe each claim element. Optis Wireless Tech., LLC v. Huawei Techs. Co. Ltd., Case
`
`No. 2:17-cv-123, 2018 WL 3375192, at *2 (E.D. Tex. July 11, 2018) (finding that the theory of
`
`infringement “must identify the part of the accused product that satisfies each claim element”).
`
`Page 7 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 8 of 16 PageID #: 7707
`
`Big Fish asserts that, because the scope of a means-plus-function claim term is limited to
`
`disclosed structures and algorithms and equivalents thereof, Uniloc’s contentions must describe
`
`what the claim element is to properly identify where it can be found in the accused products.
`
`Docket No. 348 at 3. Such a requirement, however, would conflate infringement contentions with
`
`preliminary constructions because claim scope is a question of claim construction. See Phillips v.
`
`AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005). Big Fish does not explain why means-plus-
`
`function claim terms require earlier disclosure of claim construction contentions than other types
`
`of claim terms. Taken to its logical extreme, Big Fish’s position would require a plaintiff to define
`
`the scope of all asserted claim terms in its infringement contentions. But the Patent Rules specify
`
`deadlines for claim construction later than those for infringement contentions. See P.R. 4-1, 4-2.
`
`The Court declines to read P.R. 3-1(c) in a way that would require patent owners to disclose their
`
`proposed constructions for any claim element in advance of the relevant deadlines.
`
`Big Fish also claims that the SICs cannot put it on notice of Uniloc’s infringement theories
`
`because “Uniloc indiscriminately cross-references” to steps of the method claims. Docket No. 335
`
`at 11. This too is unavailing. The SICs disclose structure and/or algorithms that perform each step
`
`of the claimed method. See, e.g., Docket No. 335-2 at 4, 38, 40, 56. And as counsel for Big Fish
`
`acknowledged at the claim construction stage, “[t]he means-plus-function claims . . . perform the
`
`exact method steps found in the method claims. There’s only minor differences in terminology. .
`
`. . That is, the systems claims are merely covering the same ground that the method claims have
`
`covered.” Markman Hrg Tr. at 88:19–25. The SICs therefore provide notice of Uniloc’s
`
`infringement theories to Big Fish.
`
`Big Fish’s motion to strike the supplemental infringement contentions is DENIED.
`
`Page 8 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 9 of 16 PageID #: 7708
`
`2.
`
`The Final Infringement Contentions Will Be Stricken
`
`Uniloc’s FICs are untimely. Uniloc does not dispute that it served the FICs after every
`
`relevant deadline had expired. See Docket No. 339 at 16 (admitting to serving the FICs seven days
`
`after the P.R. 3-6(a) deadline). Uniloc was therefore required to seek the Court’s leave to amend
`
`its contentions. It did not.
`
`To the extent Uniloc now seeks leave to amend, Uniloc has not shown good cause. Three
`
`of the four good-cause factors weigh against Uniloc. The reason for Uniloc’s delay—Big Fish’s
`
`discovery delays—is a matter of some dispute. While Big Fish appears to have been less than
`
`forthcoming in discovery, repeatedly amending its initial disclosures and delaying its document
`
`production, this does not excuse Uniloc’s two-month delay in serving the FICs after reviewing Big
`
`Fish’s source code. Uniloc claims that it needed to depose witnesses to understand how the source
`
`code worked. See Docket No. 339 at 16. But because Uniloc does not explain what aspects of the
`
`source code were unclear from its review or what it needed to confirm prior to revising its
`
`contentions, it fails to tie Big Fish’s discovery delays to Uniloc’s delays in preparing the FICs.
`
`The importance factor also weighs against Uniloc. Uniloc states that the FICs were
`
`“provided in an abundance of caution” and “are separately incorporated into the expert report on
`
`infringement.” Id. at 18. By downplaying the FICs’ effect, however, Uniloc has downplayed the
`
`FICs’ importance.
`
`By the same token, the prejudice to Uniloc is minimal. The Court has denied Big Fish’s
`
`motion to strike the SICs, so those contentions remain in the case. Big Fish, meanwhile, would
`
`suffer prejudice were Uniloc granted leave to amend in a form “that typically flows from allowing
`
`an opposing party to disregard pretrial timing requirements—the party’s loss of an opportunity to
`
`use discovery to explore the opposing party’s theories and the loss of time to develop responses to
`
`those theories.” Sycamore IP Holdings LLC v. AT&T Corp., Case No. 2:16-cv-588, 2017 WL
`
`Page 9 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 10 of 16 PageID #: 7709
`
`4517953, at *5 (E.D. Tex. Oct. 10, 2017). This is true even though Uniloc served the FICs more
`
`than two years ago—Big Fish received the FICs after the close of fact discovery, so it could not
`
`have conducted responsive discovery even if the case continued. More importantly, the Court
`
`dismissed the action shortly after Uniloc served the FICs, so Big Fish had no reason to consider
`
`them until the Federal Circuit remanded, at which point Big Fish promptly moved to strike.
`
`Finally, while the lack of a schedule in this case would allow for a continuance, reopening
`
`discovery would not be appropriate for the reasons set forth above. This single factor does not
`
`overcome Uniloc’s failure to show good cause.
`
`Big Fish’s motion to strike Uniloc’s Final Infringement Contentions is GRANTED.
`
`III. Uniloc’s Motion to Reconsider (Docket No. 344)
`
`Uniloc asks the Court to reconsider its constructions of two terms: “application launcher
`
`program” and “application program.” Docket No. 344 at 1. The Court construed “application
`
`launcher program” to mean “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.” Docket No. 233 at 27–
`
`31. 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.” Id. at 19–23.
`
`Uniloc asserts that, in reaching these constructions, the Court erred in three respects: first,
`
`in consulting the prosecution history of the ’466 patent to interpret the claims of the unrelated ’578
`
`and ’293 patents; second, in referring to statements in the prosecution history of the ’766 patent to
`
`construe the claims of the earlier-issued ’578 patent; and third, by not adopting constructions that
`
`reflect the ordinary meaning of “application launcher” or “application program.” See generally
`
`Docket No. 344. In support of this third argument, Uniloc submits the declaration of Dr. Michael
`
`Shamos, seven prior art references and an article.
`
`Page 10 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 11 of 16 PageID #: 7710
`
`Big Fish opposes Uniloc’s request. Docket No. 352. Big Fish first contends that Uniloc
`
`waived its right to reconsideration by not raising claim construction on appeal. Docket No. 352 at
`
`8. Big Fish next argues that Uniloc’s motion is improper because it reargues positions that Uniloc
`
`raised and lost at the claim construction stage. Id. at 8–9. Big Fish further objects to Uniloc’s
`
`expert declaration as untimely and improper. Id. at 9–11. Fourth, Big Fish contends that Uniloc
`
`failed to acknowledge the standard for reconsideration and did not articulate an argument that
`
`would satisfy it. Id. at 11–12. Finally, Big Fish argues that the Court properly considered the
`
`prosecution histories of the patents. Id. at 12–19.
`
`A.
`
`Applicable Law
`
`“Motions for reconsideration serve the narrow purpose of allowing a party to correct
`
`manifest errors of law or fact or to present newly discovered evidence.” Solid State Storage
`
`Solutions, Inc. v. STEC, Inc., 2:11-CV-391, 2012 WL 12904107, at *1 (E.D. Tex. Sept. 27, 2012)
`
`(citing Texas Instruments, Inc. v. Hyundai Elecs. Indus. Co. Ltd., 50 F. Supp. 2d 619, 621 (E.D.
`
`Tex. 1999)). “A motion for reconsideration should not be used to raise arguments ‘that could, and
`
`should, have been made before entry of judgment or to re-urge matters that have already been
`
`advanced by a party.’ ” De Leon v. Flavor & Fragrance Specialties, Inc., 6:12-CV-327, 2014 WL
`
`12601029, at *1 (E.D. Tex. Sept. 15, 2014). “[L]itigants are expected to present their strongest
`
`case when the matter is first considered. A motion to reconsider based on recycled arguments only
`
`serves to waste the resources of the court.” State of Louisiana v. Sprint Comms. Co., 899 F. Supp.
`
`282, 284 (M.D. La. 1995).
`
`B.
`
`Analysis
`
`The Court begins with the question of whether Uniloc may seek reconsideration of the
`
`Court’s claim construction. The law-of-the-case and waiver doctrines are distinct but related. See
`
`Med. Center Pharm. v. Holder, 634 F.3d 830, 834 (5th Cir. 2011). “The law-of-the-case doctrine
`
`Page 11 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 12 of 16 PageID #: 7711
`
`posits that when a court decides upon a rule of law, that decision should continue to govern the
`
`same issue in subsequent stages in the same case.” United States v. Castillo, 179 F.3d 321, 326
`
`(5th Cir. 1999) (quotations omitted). “Therefore, an issue of law decided on appeal may not be
`
`reexamined by the district court on remand or by the appellate court on a subsequent appeal.”
`
`Holder, 634 F.3d at 834. The waiver doctrine, meanwhile, “holds that an issue that could have
`
`been but was not raised on appeal is forfeited and may not be revisited by the district court on
`
`remand.” Id. (emphasis original).
`
`Neither the law-of-the-case nor the waiver doctrines apply here. The Federal Circuit did
`
`not rely on the Court’s constructions of “application program” or “application launcher program”
`
`to conclude that the ’578 and ’293 patents are directed to patent-eligible subject matter. See
`
`generally Docket No. 317. Accordingly, the constructions are not part of the law of the case.
`
`Holder, 634 F.3d at 834 (“[A]n issue that is not expressly or implicitly decided on appeal does not
`
`become part of the law of the case”). Nor has Uniloc committed waiver. The Federal Circuit
`
`“support[s] a district court’s discretion to permit parties to change their positions over the course
`
`of litigation.” WiLAN USA, Inc. v. Apple Inc., 830 F.3d 1374, 1385 (Fed. Cir. 2016). And district
`
`courts “may engage in rolling claim construction, in which the court revisits and alters its
`
`interpretation of the claim terms as its understanding of the technology evolves.” Guttman, Inc. v.
`
`Kopykake Enters., Inc., 302 F.3d 1352, 1361 (Fed. Cir. 2002). The Court does not discern a reason
`
`why an interim appeal of an unrelated issue should deprive a party of its right, or the Court of its
`
`ability, to ensure that claims are properly construed.
`
`Turning to the merits, the Court analyzes motions to reconsider under Federal Rule of Civil
`
`Procedure 59(e). Blue Spike, LLC v. Juniper Networks, Inc., Case No. 6:17-cv-16, 2018 WL
`
`4261316, at *1 (E.D. Tex. May 16, 2018). Under Rule 59(e), a court may reconsider a ruling due
`
`Page 12 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 13 of 16 PageID #: 7712
`
`to (1) an intervening change in controlling law; (2) the availability of new evidence not previously
`
`available; or (3) the need to correct a clear error of law or prevent manifest injustice. In re
`
`Benjamin Moore & Co., 318 F.3d 626, 629 (5th Cir. 2002). Uniloc does not argue that the law has
`
`changed. And the evidence Uniloc submits with its motion—the expert declaration of Dr. Shamos
`
`and the eight references attached to it—is not new. Uniloc does not explain why the evidence was
`
`previously unavailable. The Court will therefore not consider it. This leaves the third prong.
`
`Uniloc’s motion advances arguments that Uniloc previously presented to the Court. See,
`
`e.g., Docket No. 165 at 7–8 (“We can disregard the prosecution history of the ’466 patent because
`
`the claim construction issue is limited to claims of the ’578 and ’293 patents. . . . As all parties
`
`agree, the claims of the ’466 patent require execution at the client. But that requirement does not
`
`arise from a ‘definition’ of ‘application.’ . . . Defendants have a similar problem with statements
`
`from the ’766 prosecution history, because that prosecution also forms no part of the prosecution
`
`history of the ’578 or ’293 patents.”); Docket No. 210 at 3 n.5 (repeating position on ’466 patent
`
`claims); Docket No. 220 at 2 (characterizing as “the central issue” “whether a limitation, clearly
`
`expressed in specific language in the claims of the ‘466 patent (‘providing an instance of the
`
`…application…to the client for execution’), should be read into claims of other patents that omit
`
`that language.”); id. at 3 (clarifying that statements in unrelated prosecution histories may be
`
`considered only as extrinsic evidence). The Court has already considered and rejected these
`
`assertions. Docket No. 233 at 11–14. Uniloc’s attempt to relitigate prior issues, albeit with new
`
`arguments, is not a proper basis for the Court to reconsider its ruling. See De Leon, 2014 WL
`
`12601029, at *1 (“A motion for reconsideration should not be used to raise arguments that could,
`
`and should, have been made . . . or to re-urge matters that have already been advanced by a party”).
`
`Page 13 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 14 of 16 PageID #: 7713
`
`Uniloc’s reliance on Abbott Labs. v. Dey, L.P., 287 F.3d 1097 (Fed. Cir. 2002), is
`
`misplaced. Abbott deals with patents that are wholly unrelated. Abbott Labs., 287 F.3d at 1105.
`
`Here, the patents specifically state that they are related. See ’578 patent at 1:6–13; ’466 patent at
`
`1:6–12, 11:17–26. These representations led the Court to conclude that the prosecution histories
`
`were relevant. Docket No. 233 at 14. Uniloc does not address why that was clear error.
`
`One new argument that Uniloc advances is that the Court’s construction of “application
`
`program” does not read on a preferred embodiment disclosed in the ’578 patent. See Docket No.
`
`344 at 12. Specifically, Uniloc contends that the ’578 patent describes an embodiment 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
`HyperText Transfer Protocol (HTTP) communications or other
`suitable protocols.
`
`’578 patent at 8:7–20. This excerpt, however, only describes the user interface. Neither the
`
`disclosure nor Dr. Shamos’s declaration explain where the application is launched after the URL
`
`is requested. And Uniloc does not explain how the disclosure is inconsistent with the prosecution
`
`history statements previously relied upon by the Court which explain that “an instance of the
`
`application program is requested through the desktop but executes locally at the client as a
`
`separate application from the browser interface.” See Docket No. 233 at 20 (emphasis original).
`
`Uniloc’s arguments are not enough to show clear error in the Court’s construction or to disturb the
`
`Court’s prior order.
`
`Page 14 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 15 of 16 PageID #: 7714
`
`Uniloc has not demonstrated that the Court committed clear error or that its constructions
`
`would work manifest injustice. The Motion to Reconsider is DENIED.
`
`CONCLUSION
`
`For the reasons set forth above, the Court DENIES Uniloc’s Motion for Discovery (Docket
`
`No. 331). The Court GRANTS-IN-PART Defendant’s Motion to Strike Infringement
`
`Contentions (Docket No. 335) with respect to Uniloc’s Final Infringement Contentions and
`
`DENIES-IN-PART with respect to Uniloc’s Supplemental Infringement Contentions. Uniloc’s
`
`Motion for Reconsideration (Docket No. 344) is DENIED. The parties are
`
`ORDERED to supplement their document productions and written discovery responses
`
`within 21 days of the date of this order and to supplement their opening expert reports 21 days
`
`thereafter. The parties shall further prepare and submit a proposed docket control order within
`
`seven days of the date of this order. It is hereby
`
`ORDERED that the following schedule of deadlines shall be incorporated into the
`
`proposed docket control order:
`
`Jury Trial
`
`Jury Selection
`
`Pre-trial Conference
`
`Dispositive and Daubert
`Motion Hearing
`
`Dispositive and Daubert
`Motion Deadline
`
`
`
`
`*June 15, 2020, immediately following jury selection in Marshall,
`Texas
`
`*June 17, 2020, at 9:00 a.m. in Marshall, Texas
`
`*June 2, 2020, at 10:00 a.m. in Texarkana, Texas
`
`*May 28, 2020, at 10:00 a.m. in Texarkana, Texas
`
`*April 3, 2020
`
`Page 15 of 16
`
`

`

`Case 2:16-cv-00741-RWS Document 364 Filed 02/05/20 Page 16 of 16 PageID #: 7715
`
`
`
`Page 16 of 16
`
`.
`
`
`
`____________________________________
`ROBERT W. SCHROEDER III
`UNITED STATES DISTRICT JUDGE
`
`So ORDERED and SIGNED this 5th day of February, 2020.
`
`

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