throbber
Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 1 of 16 PageID #: 664
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`ESTECH SYSTEMS, INC.
`
`
`Plaintiff,
`
`v.
`
`TARGET CORPORATION
`
`
`
`Case No. 2:20-cv-00123-JRG
`LEAD CASE
`
`
`Case No. 2:20-cv-00122-JRG
`
`
`Case No. 2:20-cv-00126-JRG
`
`
`Case No. 2:20-cv-00127-JRG
`
`
`Case No. 2:20-cv-00128-JRG
`




















`
`DEFENDANTS WELLS FARGO & COMPANY AND WELLS FARGO BANK, N.A.’s,
`RESPONSE IN OPPOSITION TO ESTECH’S
`MOTION FOR LEAVE TO AMEND INFRINGEMENT CONTENTIONS
`
`
`PLAINSCAPITAL BANK
`
`BOKF, NATIONAL ASSOCIATION
`
`BBVA USA BANCSHARES, INC.
`
`WELLS FARGO & COMPANY, ET AL.
`
`
`Defendants.
`
`
`CISCO EXHIBIT 1022
`Page 1 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 2 of 16 PageID #: 665
`
`Estech Systems, Inc. (“Estech”) dropped the ’349 Patent from the case against Wells Fargo
`
`Bank, N.A. and Wells Fargo & Co. (collectively, “Wells Fargo”), and for two reasons, this Court
`
`should not allow Estech to add it back into the case. First, Estech’s amendment is futile because,
`
`as Wells Fargo detailed in its Motion to Dismiss, (a) Estech has not stated a claim for infringement
`
`of the expired ’349 Patent sufficient to survive a Rule 12(b)(6) motion; and (b) Estech’s
`
`infringement contentions do not satisfy the disclosure requirements under P.R. 3-1. See Dkt. 22.
`
`Second, Estech has not established good cause for the amendment under P.R. 3-6(b).
`
`STATEMENT OF FACTS
`
`
`
`On April 28, 2020, Estech filed its Complaint against Wells Fargo alleging infringement
`
`of four patents, including the ’349 Patent. See Compl. (Dkt. 1) ¶¶ 53–63. The ’349 Patent was
`
`filed on December 31, 1997, issued on May 23, 2000, and central to this case, expired on December
`
`31, 2017. On June 19, 2020, Wells Fargo filed its Motion to Dismiss under Rule 12(b)(6) on the
`
`grounds that Estech has not stated a claim for infringement of the ’349 Patent because, among
`
`other grounds, its allegations do not satisfy the notice requirements and because Estech did not—
`
`and cannot—allege that Wells Fargo knew about the ’349 Patent before the Complaint, and without
`
`such knowledge, Estech cannot show entitlement to damages. See Dkt. 22.
`
`
`
`On July 6, 2020, Estech served its court-mandated infringement contentions. In its eight-
`
`page cover pleading, Estech made the following disclosures as to its infringement allegations here
`
`none of which disclosed, identified, or referenced the expired ’349 Patent:
`
`• “P.R. 3-1(a): Identification of Infringed Claims,” identifying and defining the ’298,
`’684, and ’699 Patents as the “Asserted Patents,” identifying allegedly infringed
`claims of the the ’298, ’684, and ’699 Patents, and omitting any reference to the
`’349 Patent or claims of the ’349 Patent:
`
`1
`
`CISCO EXHIBIT 1022
`Page 2 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 3 of 16 PageID #: 666
`
`Dkt. 43-2, at ECF pg. 2.
`
`
`
`• “P.R. 3-1(b):
`identifying
`Instrumentalities,”
`of Accused
`Identification
`instrumentalities for the ’298,’684, and’699 Patents, and omitting any reference to
`the ’349 Patent or claims of the ’349 Patent. Dkt. 43-2, at ECF pg. 2–5.
`• “P.R. 3-1(c): Claim Charts,” stating that Estech was attaching claim charts
`“identifying specifically where each element of each asserted claim is found within
`the accused instrumentalities . . . attached hereto as Exhibit A (’298 Patent), Exhibit
`B (’684 Patent), and Exhibit C (’699 Patent). Dkt. 43-2, at ECF pg. 6.
`• “P.R. 3-1(d): Disclosure of Literal Infringement and Infringement under the
`Doctrine of Equivalents,” in which Estech cited Exhs. A–C (corresponding to charts
`for the’298,’684, and’699 Patents), to support its position that each claim limitation
`for each asserted claim is infringed literally and under the doctrine of equivalents.
`• “P.R. 3-1(e): Disclosure of Priority Claims,” identifying the priority date of the
`’298, ’684, and ’699 Patents, but omitting any reference to the ’349 Patent or its
`priority date.
`
`Dkt. 43-2, at ECF pg. 6.
`
`
`
`Along with providing no “single claim chart” for the ’349 Patent, Estech did not mention
`
`the ’349 Patent in any of the six sections of its eight-page disclosure identifying the asserted patents
`
`and related information required under the Local Patent Rules. Accordingly, Estech made clear in
`
`its infringement contentions it was no longer asserting the ’349 Patent, which was reasonable
`
`considering Wells Fargo’s position in its Motion to Dismiss that the expired ’349 Patent should
`
`not have been asserted in the first place.1
`
`
`1 Given Estech’s clear exclusion of the ’349 Patent from its infringement contentions, there was
`no “omission” to clarify with Estech. See Mot. at 1. Estech’s position it was no longer asserting
`
`2
`
`CISCO EXHIBIT 1022
`Page 3 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 4 of 16 PageID #: 667
`
`
`
`On July 14, 2020, Wells Fargo filed its Reply in support of its Motion to Dismiss, and in
`
`reliance on Estech’s infringement contentions devoid of any reference to the ’349 Patent, did not
`
`advance any further arguments.
`
`
`
`On July 15, 2020, Estech advised Wells Fargo it “inadvertently omitted” the ’349 Patent
`
`from its infringement contentions. Instead of serving its amended infringement contentions
`
`immediately, Estech elected to make service contingent on receipt of Wells Fargo’s position on
`
`Estech’s Motion for Leave to Amend. On July 16, 2020, Wells Fargo advised Estech of its position
`
`on Estech’s Motion for Leave to Amend, and made itself available on July 17, 2020 for a meet and
`
`confer.
`
`ARGUMENT
`
`I.
`
`Estech’s Motion Should be Denied Because the Proposed Amendment Cannot
`Survive Wells Fargo’s Motion to Dismiss and Does Not Satisfy the Local Patent Rules’
`Disclosure Requirements, and is, Therefore, Futile.
`
`Estech’s proposed amendment to add back the ’349 Patent to the case should be denied
`
`because it is futile. When addressing a motion for leave to amend, courts in this district consider
`
`whether the proposed amendment would be futile. E.g., IDB Ventures, LLC v. Charlotte Russe
`
`Holdings, Inc., 360 F. Supp. 3d 541, 554 (E.D. Tex. 2018) (considering whether amendments to
`
`the complaint and infringement contentions would be futile). If the proposed amendment would
`
`not survive a Rule 12(b)(6) motion, then the amendment is futile and the motion for leave should
`
`be denied. Raytheon Co. v. Indigo Sys. Corp., No. 4:07-CV-109, 2008 WL 3852715, at *3 (E.D.
`
`Tex. Aug. 14, 2008) (“[I]f the revision would not survive a motion made under Rule 12(b)(6), the
`
`motion for leave to amend should be denied.”).
`
`
`the ’349 Patent was so obvious from its infringement contentions, Wells Fargo was not “left
`wondering” why the ’349 Patent was not included at all in the contentions. See id. at 5.
`
`3
`
`CISCO EXHIBIT 1022
`Page 4 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 5 of 16 PageID #: 668
`
`Here, Estech’s Motion to add the ’349 Patent back into to this case is futile for two reasons.
`
`First, Estech’s proposed infringement contentions do not—and, indeed, cannot—cure the fatal
`
`deficiencies in the Estech’s Complaint as laid out in Wells Fargo’s Motion to Dismiss,
`
`incorporated by reference.2 Estech’s Complaint does not plausibly allege infringement of the ’349
`
`Patent because Estech fails to specify any particular accused instrumentalities, and fails to allege
`
`pre-suit knowledge or marking of the ’349 Patent.3 See Dkt. 22. at 4; Dkt. 43, at 2–3. Indeed,
`
`Estech failed to identify a single product or infringing act by Wells Fargo, and failed to allege any
`
`plausible basis for pre-suit knowledge of the ’349 Patent. This failure to allege any basis for pre-
`
`suit knowledge dooms Estech’s claims for recovery of any alleged indirect infringement or willful
`
`infringement of the ’349 Patent because it expired in December 2017, nearly three years before
`
`this lawsuit. Therefore, unlike the other three asserted patents, which have not expired, Estech
`
`cannot rely on the Complaint’s providing notice of the ’349 Patent to satisfy its pleading
`
`requirements. Since Estech’s amendment adding back the ’349 Patent will not survive a Rule
`
`12(b)(6) motion, the amendment is futile and Estech’s Motion should be denied.
`
`Second, Estech’s amendment is also futile because Estech’s proposed contentions for the
`
`’349 Patent do not satisfy the disclosure requirements in the Local Patent Rules. Patent Rule 3-1
`
`mandates that infringement contentions provide “‘particular theories of infringement with
`
`
`2 Estech’s July 6, 2020, Infringement Contentions are deficient as a whole. Wells Fargo identified
`many of the deficiencies in its Reply in support of its Motion to Dismiss (Dkt. 43), and after
`compliance with the Court’s meet-and-confer requirements, may seek the Court’s assistance with
`any remaining deficiencies.
`3 The ’349 Patent has both method and system claims. See Huawei Techs. Co. v. T-Mobile US,
`Inc., 2017 WL 4183103, at *2-3 (E.D. Tex. Sept. 4, 2017) (“Neither the term ‘patented’ nor the
`term ‘article’ necessarily implies that the marking statute is limited solely to the device or
`apparatus claim that the patentee is asserting in the ‘infringement action’ . . . . As a result, a logical
`interpretation of the statute is that a patentee must mark any product covered by any claim of the
`asserted patent.”).
`
`4
`
`CISCO EXHIBIT 1022
`Page 5 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 6 of 16 PageID #: 669
`
`sufficient specificity to provide defendants with notice of infringement beyond that which is
`
`provided by the mere language of the patent [claims] themselves.’” Davis-Lynch, Inc. v.
`
`Weatherford Int'l, Inc., No. CIV.A. 6:07-CV-559, 2009 WL 81874, at *2 (E.D. Tex. Jan. 12, 2009)
`
`(emphasis added) (alteration in original) (quoting STMicroelectronics, Inc. v. Motorola, Inc., 308
`
`F. Supp. 2d 754, 755 (E.D. Tex. 2004)). Most relevant here, Rule 3-1(b) requires Estech to
`
`identify, “[s]eparately for each asserted claim, each accused apparatus, product, device, process,
`
`method, act or other instrumentality . . . of [the] opposing party of which the party is aware,” and
`
`Rule 3-1(c) requires “[a] chart identifying specifically where each element of each asserted claim
`
`is found within each Accused Instrumentality.” P.R. 3-1(b) & (c). Crucially, Estech cannot “rely
`
`on vague, conclusory language or simply mimic the language of the claims” in its infringement
`
`contentions. Davis-Lynch, 2009 WL 81874, at *2 (emphasis added); see also Connectel, LLC v.
`
`Cisco Sys., Inc., 391 F. Supp. 2d 526, 528 (E.D. Tex. 2005) (“PICs providing vague, conclusory
`
`language or simply mimicking the language of the claims when identifying infringement fail to
`
`comply with Patent Rule 3-1.”).
`
`Similar to Estech’s deficient Complaint, the proposed amendment for the expired ’349
`
`Patent does not meet even the minimum specificity requirements under P.R. 3-1(c), justifying
`
`denial of Estech’s Motion. Estech used generic descriptors of equipment and systems used by
`
`virtually every commercial enterprise today. For example, Estech identifies (1) “[s]ervers and
`
`networking equipment (e.g., hubs, switches, routers and server) that provide VoIP services
`
`(including voice mail) to Wells Fargo’s VoIP telephony devices, including, but not limited to
`
`servers that provide VoIP services to Wells Fargo,” and (2) “VoIP telephony devices . . . including,
`
`but not limited to” a list of a dozen different business telephones. See Ex. 1, Estech’s Proposed
`
`Am. Disclosure of Asserted Claims & Infringement Contentions (“Proposed Infringement
`
`5
`
`CISCO EXHIBIT 1022
`Page 6 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 7 of 16 PageID #: 670
`
`Contentions”), at 5. Estech’s repeated use of “including, but not limited to” and Estech’s attempt
`
`to shoe-horn in “all related software for the hardware components identified” amplifies the
`
`boundless nature of these alleged instrumentalities. Id. This Court has previously recognized that
`
`the use of such “catch-all language,” which “puts the onus on [the accused infringer] to determine
`
`what devices infringe,” is contrary to the intent of the Patent Rules. Alacritech Inc. v. CenturyLink,
`
`Inc., No. 2:16-CV-00693-JRG-RSP, 2017 WL 3007464, at *3 (E.D. Tex. July 14, 2017). Without
`
`additional context and details, it is impossible for Wells Fargo to identify what systems or
`
`equipment Estech’s proposed contentions reference.
`
`Further, Estech’s proposed contentions do not satisfy P.R. 3-1(c) because they consist
`
`entirely of “vague, conclusory language [that] simply mimic[s] the language of the claims.” Davis-
`
`Lynch, 2009 WL 81874, at *2. In its proposed six-page claim chart for the ’349 Patent, Estech
`
`identifies six claims and eleven elements (not counting the preambles), but, for the disclosure of
`
`“Infringing Product/Structure/Act,” Estech does not provide even a single citation, reference,
`
`diagram, or picture, as demonstrated in Estech’s proposed disclosure for Claim 1:
`
`6
`
`CISCO EXHIBIT 1022
`Page 7 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 8 of 16 PageID #: 671
`
`
`
`
`
`See Ex. 2, Exhibit D to Estech’s Proposed Infringement Contentions (emphasis added).
`
`Instead of actually providing the requisite disclosure, Estech resorts to referencing vague
`
`instrumentalities and parroting the exact language used in the claims. See Ex. 2, Exhibit D to
`
`Estech’s Proposed Infringement Contentions. The highlighting in the above excerpt confirms this;
`
`Estech’s infringement contentions for Claim 1 largely recite the claim language word-for-word.
`
`While it is true infringement contentions “are not meant to provide a forum for litigation on the
`
`substantive issues,” they must at least be reasonably precise and detailed enough to put the
`
`defendant on notice as to the plaintiff’s theory of infringement. Realtime Data, LLC v. Packeteer,
`
`Inc., No. 6:08-cv-144, 2009 WL 2590101, at *5 (E.D. Tex. Aug. 18, 2009). Here, Estech’s
`
`proposed amendment fails to satisfy even the most minimal specificity requirements.
`
`7
`
`CISCO EXHIBIT 1022
`Page 8 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 9 of 16 PageID #: 672
`
`Rather than providing the requisite specificity, Estech instead relies extensively on this
`
`Court’s software limitation provisions in the Court’s Sample Discovery Order. Specifically, for
`
`ten of the eleven elements in the six asserted claims in the proposed amendment, Estech contends
`
`“Wells Fargo’s specific implementation is defined in its source code, so this is a software limitation
`
`under Section 3(a) of Chief Judge Gilstrap’s Sample Discovery Order for Patent Cases.” E.g.,
`
`Ex. 2, at 1. Instead of citing the Court’s Sample Discovery Order for a legitimate purpose—i.e.,
`
`as a placeholder for claim elements that truly are software—Estech uses the provision to delay
`
`disclosure to Wells Fargo or to mask its own deficient pre-suit investigation.4 Either way, after a
`
`supposedly sufficient pre-suit investigation and nearly three months into the case, Estech cannot
`
`satisfy its obligations under the Patent Rules with anything more than the claim language and a
`
`plan to supplement based on source code review. Indeed, Estech provides no explanation for why
`
`it needs source code review for asserted claim limitations directed to components of VoIP
`
`telephony networks and systems to comply with its disclosure requirements.
`
`Accordingly, because Estech’s proposed amendment lacks both specificity and
`
`particularity, it does not satisfy the requirements of P.R. 3-1. Estech’s Motion is therefore futile,
`
`and should be denied.
`
`
`4 Estech’s strategy of characterizing almost every element in its proposed amendment as a
`“software limitation” simply compounds the lack of specificity and notice to Wells Fargo
`regarding Estech’s theory of infringement. Section 3(a) of the Court’s Sample Discovery Order
`provides that a party need not comply with P.R. 3-1 for software limitations until 30 days after
`source code “for each Accused Instrumentality is produced by the opposing party.” As stated
`above and argued in Wells Fargo’s Motion to Dismiss, Estech’s Complaint and infringement
`contentions fail to give notice to Wells Fargo as to the actual identity of the products which Estech
`allege infringe, and thus by invoking the source code for each of these unidentified products,
`Estech simply exacerbates the deficient nature of its contentions and allegations.
`
`8
`
`CISCO EXHIBIT 1022
`Page 9 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 10 of 16 PageID #: 673
`
`II.
`
`Estech’s Motion Should Be Denied Because It Has Not Established Good Cause for
`Leave to Amend.
`
`Estech’s Motion should be denied because Estech has not established good cause to add
`
`the ’349 Patent back into the case. Because Estech seeks to amend for reasons unrelated to claim
`
`construction, Patent Rule 3-6(b) requires a showing of good cause, based on a four-factor analysis:
`
`“(1) the explanation for the party’s failure to meet the deadline, (2) the importance of what the
`
`court is excluding, (3) the potential prejudice if the court allows that thing that would be excluded,
`
`and (4) the availability of a continuance to cure such prejudice.” IDB Ventures, 360 F. Supp. 3d
`
`at 549. Here, based on this four-factor analysis, the Court should deny Estech’s Motion.
`
`a.
`
`Estech’s Explanation for Failure to Meet the Deadline Justifies Denial.
`
`Estech’s complete exclusion of the ’349 Patent from its infringement contentions could not
`
`have been inadvertent. Forgetting to attach a single claim chart, forgetting to list one patent among
`
`many, or forgetting to list one asserted claim might qualify as inadvertent, unintentional, or
`
`accidental. This situation is dramatically different. As shown here and in Wells Fargo’s Reply to
`
`its Motion to Dismiss, Estech completely dropped the ’349 Patent from its infringement
`
`contentions. See Dkt. 43, at 1 n.1. It cannot be the case that excluding from your infringement
`
`contentions 25% of the patents asserted is mere inadvertence.
`
`Indeed, the ’349 Patent is pointedly absent from the cover pleading and attachments Estech
`
`served on the infringement contentions deadline, which indicates exclusion, not oversight. See
`
`Dkt. 43-2. Furthermore, the cover pleading identifies Defendants Wells Fargo & Co. and Wells
`
`Fargo Bank. N.A. by name, suggesting that the contentions were not prepared en masse for all
`
`defendants in the now-consolidated cases, but specifically for Wells Fargo, and thus the ’349
`
`Patent was intentionally omitted from the contentions prepared for Wells Fargo. Accordingly,
`
`Estech’s exclusion of the ’349 Patent in its entirety could not have been inadvertent.
`
`9
`
`CISCO EXHIBIT 1022
`Page 10 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 11 of 16 PageID #: 674
`
`To the extent Estech’s “simple oversight and mistake” justification for omitting the ’349
`
`Patent boils down to an excuse that Estech confused its allegations against Wells Fargo with other
`
`cookie-cutter allegations it has brought against other defendants in which Estech did not assert the
`
`’349 Patent, that is the result of lack of preparedness rather than inadvertence, and yet another
`
`symptom of Estech’s bringing suit against Wells Fargo (and the other defendants) based on nothing
`
`more than conjecture and supposition. The Patent Rules impose a burden on patent plaintiffs to
`
`“formulate, test, and crystallize their infringement theories before stating their preliminary
`
`infringement contentions.” Connectel, 391 F. Supp. 2d at 527 (emphasis added); see Alacritech,
`
`2017 WL 3007464, at *1 (“The Patent Rules demonstrate high expectations as to plaintiffs’
`
`preparedness before bringing suit . . . .”). Here, where Estech’s contentions are so generic and
`
`unspecific so as to be interchangeable between alleged infringers—such that it is not immediately
`
`obvious to Estech it served the “wrong” contentions omitting an entire patent—Estech has not
`
`provided the requisite detail in its infringement theories as required by the Patent Rules. While
`
`inadvertent mistake can suffice as an explanation for why leave to amend could be required in
`
`some circumstances, the exigencies of the case at hand do not support Estech’s attempt to take
`
`cover behind a supposed oversight, and thus this factor weighs against amendment.
`
`b.
`
`Estech’s Amendment Is Not Important Because It Is Futile.
`
`As discussed, Estech’s proposed amendment is futile, and therefore, cannot be important.
`
`“[A] court, in assessing the importance of an amendment, must make a ‘pragmatic judgment on
`
`the likelihood that the newly asserted [claim] will succeed.’” IDB Ventures, 360 F. Supp. 3d at
`
`554 (quoting Allergan, Inc. v. Teva Pharm. USA, Inc., No. 2:15-cv-1455, 2017 WL 1512334, at
`
`*5 (E.D. Tex. Apr. 27, 2017)). Here, Estech’s infringement claims for the ’349 Patent will not
`
`succeed because (1) Estech has not stated a claim sufficient to survive a Rule 12(b)(6) motion; and
`
`10
`
`CISCO EXHIBIT 1022
`Page 11 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 12 of 16 PageID #: 675
`
`(2) Estech’s proposed contentions do not satisfy the disclosure requirements of P.R. 3-1.5 Given
`
`Estech’s election to file a deficient complaint and to serve deficient infringement contentions, the
`
`’349 Patent is not important, and this factor weighs in favor of denying Estech’s Motion.
`
`c.
`
`Permitting Amendment Prejudices Defendants.
`
`Allowing Estech to add back the ’349 Patent unfairly prejudices Wells Fargo in at least
`
`two ways. First, Estech’s continued failure to comply with the disclosure requirements prejudices
`
`Wells Fargo. Despite filing suit months ago, Estech has yet to comply with disclosure
`
`requirements for both its pleadings and infringement contentions, begging the question: at what
`
`point will Wells Fargo know Estech’s infringement allegations? The Patent Rules contemplate
`
`that infringement contentions result in a “clear path,” in which the contentions “focus[] discovery
`
`on building precise final infringement . . . contentions and narrow[] issues for Markman, summary
`
`judgment, trial, and beyond.” Davis-Lynch, 2009 WL 81874, at *2. Ideally, the parties should be
`
`well on their way to narrowing the case, but instead Estech’s proposed contentions for the ’349
`
`Patent herald the infliction of expansive and burdensome discovery obligations for Wells Fargo.
`
`As discussed, Estech’s amendment is not only unlimited—repeatedly using “including, but not
`
`limited to,” and shoe-horning in for each “instrumentality” “all related software for the hardware
`
`
`5 In addition, Estech argues that including the ’349 Patent in this case is important to the Court’s
`docket because Estech has also asserted it against Target Inc. and the Regus Group, other
`defendants in the consolidated case. However, both Target and the Regus Group have already
`moved to dismiss Estech’s infringement claims relating to the ’349 Patent for reasons similar to
`those expressed in Wells Fargo’s Motion to Dismiss. See Dkt. 35; Estech Systems, Inc. v. Regus
`Mgmt. Grp., LLC, No 2:20-cv-143-JRG-RSP, Dkt. 11 (E.D. Tex. June 22, 2020). Accordingly,
`Estech’s deficient claims regarding the ’349 Patent will not move forward against any defendant,
`justifying denial of Estech’s request to add it back into this case. Moreover, Estech’s contention
`that adding the ’349 Patent avoids the burden of parallel proceedings on the Court belies the fact
`that it is Estech’s disregard for the Court’s rules and deadlines regarding service of infringement
`contentions—as well as its failure to prepare adequately prior to suit and provide sufficient
`contentions—which has resulted in the instant motion practice.
`
`11
`
`CISCO EXHIBIT 1022
`Page 12 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 13 of 16 PageID #: 676
`
`components . . . and systems that employ those hardware components”—but also non-specific,
`
`with its vague references to generic “[s]ervers and networking equipment.” Estech’s amendment
`
`is no notice to Wells Fargo of what it is being accused of, and thus imposes an impossible and
`
`unfair burden on Wells Fargo. Permitting Estech’s claims on the ’349 Patent to proceed on such
`
`limitless contentions would condone an expansive fishing expedition at Wells Fargo’s expense.
`
`Accordingly, allowing Estech’s amendment prejudices Wells Fargo.
`
`Secondly, because Wells Fargo reasonably understood the lack of contentions for the ’349
`
`Patent to mean that Estech had abandoned the ’349 Patent, Wellss Fargo did not specifically
`
`address the ’349 Patent in its Reply to the Motion to Dismiss. See Dkt. 43, at 8 (“As an initial
`
`matter, since Estech did not serve infringement contentions for the ’349 patent, it is no longer
`
`asserting the ’349 patent against the Defendants, and thus at least effectively concedes that it is not
`
`entitled to any damages relating to alleged infringement of the ’349 patent.”). To the extent the
`
`’349 Patent is added back to the case, Wells Fargo should be permitted additional briefing to
`
`address it as it relates to the pending Motion to Dismiss.
`
`For at least these two reasons, this factor weighs in favor of denying Estech’s Motion.
`
`d.
`
`A Continuance Will Not Cure the Prejudice to Wells Fargo to Respond to
`Deficient Contentions.
`
`A continuance will not ameliorate the prejudice discussed above, namely that the ’349
`
`Patent—which never should have been asserted—will be added back to the case. This prejudice
`
`is not rooted in any sort of time constraint related to a set trial date, but instead stems from Estech’s
`
`extraordinarily unbounded and non-specific infringement contentions. Because the proposed
`
`infringement contentions for the ’349 Patent—like the Complaint—are not limited in any
`
`meaningful way, a continuance would do little, if anything, to address the prejudice their inclusion
`
`would create. As such, this factor weighs in favor of denying the motion.
`
`12
`
`CISCO EXHIBIT 1022
`Page 13 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 14 of 16 PageID #: 677
`
`Accordingly, because all four factors weigh against granting leave to amend, Estech has
`
`not shown good cause for amendment, and its Motion should be denied.
`
`III. CONCLUSION
`
`For the foregoing reasons, Wells Fargo respectfully requests the Court to deny Estech’s
`
`Motion for Leave to Serve Amended Infringement Contentions.
`
`
`
`
`
`
`
`13
`
`CISCO EXHIBIT 1022
`Page 14 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 15 of 16 PageID #: 678
`
`Dated: August 3, 2020
`
`
`
`
`
`Respectfully submitted, by:
`
`/s/ Danielle Williams
`
`E. Danielle T. Williams
`North Carolina Bar No. 23283
`dwilliams@winston.com
`WINSTON & STRAWN LLP
`300 S. Tryon Street, 16th Floor
`Charlotte, NC 28202
`Telephone: (704) 350-7790
`Facsimile: (704) 350-7800
`
`Dustin J. Edwards
`Texas Bar No. 24042335
`dedwards@winston.com
`WINSTON & STRAWN LLP
`1111 Louisiana Street, 25th Floor
`Houston, TX 77002
`Telephone: (713) 651-2600
`Facsimile: (713) 651-2700
`
`Thomas M. Melsheimer
`Texas Bar No. 1392250
`tmelsheimer@winston.com
`James T. Underwood
`Texas Bar No. 24102587
`tunderwood@winston.com
`Katherine A. Marcom
`Texas Bar No. 24102137
`kmarcom@winston.com
`WINSTON & STRAWN LLP
`2121 N. Pearl Street, Suite 900
`Dallas, TX 75201
`
`ATTORNEYS FOR DEFENDANTS,
`WELLS FARGO & COMPANY AND
`WELLS FARGO, N.A.
`
`
`
`
`
`
`
`CISCO EXHIBIT 1022
`Page 15 of 16
`
`

`

`Case 2:20-cv-00123-JRG-RSP Document 61 Filed 08/03/20 Page 16 of 16 PageID #: 679
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that a true and correct copy of the above and foregoing document has
`
`been served on all counsel of record via the Court’s ECF system on August 3, 2020.
`
`
`
`
`/s/ Danielle Williams
`Danielle Williams
`
`
`
`
`
`CISCO EXHIBIT 1022
`Page 16 of 16
`
`

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