throbber
Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 1 of 12
`
`UNITED STATES DISTRICT COURT
`SOUTHERN DISTRICT OF NEW YORK
`
`BROADSIGN INTERNATIONAL, LLC,
`
`Plaintiff,
`
`v.
`
`T-REX PROPERTY, AB,
`
`Defendant.
`
`Civil Action No.: 1:16-cv-04586 (LTS)
`
`DEFENDANT T-REX PROPERTY, AB’S MEMORANDUM OF LAW IN
`OPPOSITION TO PLAINTIFF BROADSIGN INTERNATIONAL, LLC’S
`MOTION FOR LEAVE TO AMEND
`
`
`
`
`
`
`Steven R. Daniels (admitted pro hac vice)
`FARNEY DANIELS PC
`800 S. Austin Ave., Suite 200
`Georgetown, Texas 78626
`Tel: (512) 582-2828
`Fax: (512) 582-2829
`sdaniels@farneydaniels.com
`
`
`
`
`
`
`
`Attorneys for Defendant
`T-Rex Property, AB
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 2 of 12
`
`TABLE OF CONTENTS
`
`I. 
`
`INTRODUCTION ................................................................................................................... 1 
`
`II.  STATEMENT OF FACTS ...................................................................................................... 1 
`
`III.  LEGAL STANDARD ............................................................................................................. 1 
`
`IV.  ARGUMENT........................................................................................................................... 2 
`
`A. 
`
`B. 
`
`Amendment Would Be Futile Because T-Rex’s Lawsuits Against Other Suppliers
`Do Not Establish A Case Or Controversy Between T-Rex and BroadSign. .......... 2 
`
`Amendment Would Be Futile Because T-Rex’s Lawsuits Against BroadSign’s
`Customers Do Not Establish A Case Or Controversy. ........................................... 4 
`
`1. 
`
`2. 
`
`BroadSign’s Proposed Second Amended Complaint Does Not Plead An
`Obligation To Indemnify Its Customers. .................................................... 4 
`
`BroadSign’s Proposed Second Amended Complaint Does Not Adequately
`Plead Allegations of Indirect Infringement................................................. 5 
`
`C. 
`
`Amendment Would Be Futile Because This Case is Moot ..................................... 7 
`
`V.  CONCLUSION ....................................................................................................................... 8 
`
`
`
`
`
`
`
`
`
`
`
`ii
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 3 of 12
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`Cases
`
`Arris Group v. British Telecomm,
`639 F.3d 1368 (Fed. Cir. 2011)..........................................................................................5, 6, 7
`
`Arrowhead Indus. Water, Inc. v. Ecolochem, Inc.,
`846 F. 2d 731 (Fed. Cir. 1988)...................................................................................................3
`
`Benitec Australia, Ltd. v. Nucleonics, Inc.,
`495 F. 3d 1340 (Fed. Cir. 2007).................................................................................................6
`
`Commil USA, LLC v. Cisco Systems, Inc.,
`135 S. Ct. 1920 (2015) ...............................................................................................................6
`
`Dougherty v. North Hempstead Zoning Bd. of Zoning Appeals,
`282 F.3d 83 (2nd Cir. 2002).......................................................................................................2
`
`Foman v. Davis,
`371 U.S. 178 (1962) ...................................................................................................................1
`
`Innovative Therapies, Inc. v. Kinetic Concepts, Inc.,
`599 F.3d 1377 (Fed Cir. 2010)...................................................................................................3
`
`Micron Technology, Inc. v. Mosaid Technologies, Inc.,
`518 F. 3d 897 (Fed. Cir. 2008)...............................................................................................3, 4
`
`Microsoft Corp. v. DataTern, Inc.,
`755 F.3d 899 (Fed. Cir. 2014)....................................................................................................5
`
`Statutes
`
`35 U.S.C. § 271(c) ...........................................................................................................................5
`
`Other Authorities
`
`Fed. R. Civ. P. 12(b) ........................................................................................................................2
`
`Fed. R. Evid. 201(b)(2) ....................................................................................................................7
`
`
`
`iii
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 4 of 12
`
`Declaratory Judgment Defendant T-Rex Property, AB (“T-Rex”) hereby submits this
`
`memorandum of law in opposition to Plaintiff BroadSign International, LLC’s Motion for Leave
`
`to Amend its Complaint (D.I. 42). A declaration of Steven R. Daniels accompanies this
`
`memorandum.
`
`I.
`
`INTRODUCTION
`
`This Court properly dismissed BroadSign’s prior complaint, finding that BroadSign had
`
`not pled facts establishing the existence of a “substantial controversy” between itself and T-Rex.
`
`D.I. 40 at 10. BroadSign’s motion for leave to amend should be denied as futile for two reasons:
`
`(1) it fails to adequately address the deficiencies the Court identified in its Order; and (2) any
`
`controversy is now clearly moot because all of T-Rex’s cases against BroadSign’s customers
`
`have been resolved.
`
`II.
`
`STATEMENT OF FACTS
`
`At the time that T-Rex’s motion to dismiss was being decided, by Defendant’s admission,
`
`all but two of T-Rex’s cases against BroadSign’s customers had been resolved. D.I. 23 ¶ 24
`
`(stating that “only the cases against Adaptive Micro Systems and ContextMedia Health are still
`
`pending”). BroadSign’s proposed second amended complaint does not plead any new lawsuits
`
`against BroadSign’s customers in the time since that motion was decided. D.I. 23 ¶ 24
`
`(identifying seven lawsuits); D.I. 44-1 ¶ 29 (identifying “seven (7) BroadSign customers”).
`
`Moreover, BroadSign fails to disclose that, since that time, T-Rex’s cases against those two
`
`remaining BroadSign customers have now concluded. Daniels Decl. Exhs. A, B.
`
`III. LEGAL STANDARD
`
`“[U]ndue delay, bad faith or dilatory motive on the part of the movant, repeated failure to
`
`cure deficiencies by amendments previously allowed, undue prejudice to the opposing party ...
`
`[or] futility of amendment” are grounds for denying leave to amend. Foman v. Davis, 371 U.S.
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 5 of 12
`
`178, 182 (1962). An amendment to a pleading will be futile if a proposed claim could not
`
`withstand a motion to dismiss pursuant to Rule 12(b). Dougherty v. North Hempstead Zoning
`
`Bd. of Zoning Appeals, 282 F.3d 83, 88 (2nd Cir. 2002).
`
`IV. ARGUMENT
`A.
`
`Amendment Would Be Futile Because T-Rex’s Lawsuits Against Other
`Suppliers Do Not Establish A Case Or Controversy Between T-Rex and
`BroadSign.
`
`BroadSign argues that its proposed second amended complaint establishes a case or
`
`controversy because T-Rex has allegedly “filed complaints alleging patent infringement of the
`
`Patents-in-Suit against suppliers similarly-situated to BroadSign.” Pl.’s Mem. at 3-4; D.I. 41-1
`
`¶¶ 13-28. However, BroadSign’s argument fails for two reasons: (1) the proposed second
`
`amended complaint fails to plead facts sufficient to establish that the other parties are actually
`
`“suppliers similarly-situated to BroadSign”; and (2) the mere fact that T-Rex has previously filed
`
`suits against some suppliers of unrelated products is insufficient to establish an “aggressive”
`
`litigation campaign that would create reasonable apprehension that BroadSign is next.
`
`First, BroadSign’s conclusory pleadings are insufficient to establish that T-Rex has
`
`engaged in a litigation campaign against others similarly situated to BroadSign. By BroadSign’s
`
`own admission, BroadSign is “in the business of providing digital out-of-home software and
`
`solutions for digital signage and displays,” and in particular, “hardware and software solutions”
`
`“built to order for its customers.” D.I. 44-1 ¶¶ 3, 46. By contrast, a vast majority of the alleged
`
`suppliers identified by BroadSign were accused of infringement by operating a digital signage
`
`network. D.I. 44-1 ¶¶ 14, 16-23, 25-26. But BroadSign does not allege, or point to any
`
`allegation by T-Rex, that BroadSign is operating a digital signage network. This difference
`
`strongly counsels against a finding of an immediate and real substantial controversy. As to the
`
`remaining alleged suppliers, BroadSign fails to provide any specific facts that those suppliers are
`
`
`
`2
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 6 of 12
`
`“similarly situated” other than allegations that they offer digital signage products accused of
`
`infringement by T-Rex Property. D.I. 44-1 ¶¶ 15, 24, 27-28. For example, BroadSign does not
`
`contain any allegations that T-Rex has filed suit against others who provide “built to order”
`
`digital signage solutions for customers. In short, BroadSign fails to allege facts that create the
`
`reasonable implication T-Rex has engaged in an “aggressive enforcement strategy” against those
`
`similarly situated to BroadSign.
`
`Second, even if the Court finds that BroadSign adequately plead facts showing the
`
`existence that T-Rex has previously filed suits against similarly situated suppliers of unrelated
`
`products, that is insufficient to establish an “aggressive” litigation campaign that would
`
`reasonably cause BroadSign to believe that it is next. Innovative Therapies, Inc. v. Kinetic
`
`Concepts, Inc., 599 F.3d 1377, 1382 (Fed Cir. 2010) (“[T]he fact that [a patentee] had filed
`
`infringement suits against other parties for other products does not, in the absence of any act
`
`directed toward [the declaratory judgment plaintiff], meet the minimum standard discussed in
`
`MedImmune.”). Indeed, in cases applying the “aggressive” litigation inquiry, the courts relied on
`
`facts much stronger than the mere fact of prior litigation against others similarly situated.
`
`Instead those cases involved overt conduct directed to the declaratory judgment plaintiff. For
`
`example, in Arrowhead, the Court relied on the patent owner’s “submission to the federal court
`
`in [another] case of a proposal that the court find [the declaratory judgment plaintiff] an
`
`infringer.” Arrowhead Indus. Water, Inc. v. Ecolochem, Inc., 846 F. 2d 731, 737 (Fed. Cir.
`
`1988). In Micron, the patent owner issued threatening letters to the declaratory judgment
`
`plaintiff, engaged in a litigation campaign by only suing memory suppliers, and had sued all of
`
`the major memory suppliers other than Micron, and had issued public statements that it planned
`
`on continuing its “aggressive licensing strategy.” Micron Technology, Inc. v. Mosaid
`
`
`
`3
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 7 of 12
`
`Technologies, Inc., 518 F. 3d 897, 899 (Fed. Cir. 2008). By contrast, BroadSign’s proposed
`
`second amended complaint does not identify any threatening statements or other conduct by T-
`
`Rex relating to BroadSign. Indeed, as distinguished from Micron, T-Rex’s decision to sue the
`
`operators of digital signage systems or networks, including those which use BroadSign
`
`technology, strongly demonstrates that T-Rex does not have imminent plans to assert its patents
`
`against BroadSign itself.
`
`B.
`
`Amendment Would Be Futile Because T-Rex’s Lawsuits Against
`BroadSign’s Customers Do Not Establish A Case Or Controversy.
`
`As this Court noted in its Order on T-Rex’s motion to dismiss, “[a] defendant’s suits
`
`against a plaintiff’s customers are insufficient by themselves to establish a case or controversy
`
`between the supplier-plaintiff and the patent holder-defendant.” D.I. 40 at 7 (citing Microsoft
`
`Corp. v. DataTern, Inc., 755 F.3d 899, 904 (Fed. Cir. 2014)). However, as this Court noted,
`
`there are two exceptions to this rule: “[s]uits against a supplier’s customers may support
`
`jurisdiction if either (a) the supplier is obligated to indemnify its customers from infringement
`
`liability, or (b) there is a controversy between the patentee and the supplier as to the supplier’s
`
`liability for induced contributory infringement based on the alleged acts of direct infringement
`
`by its customers.” Id. (citing Arris Group v. British Telecomm, 639 F.3d 1368, 1375 (Fed. Cir.
`
`2011)). Because BroadSign’s proposed second amended complaint fails to colorably plead
`
`claims establishing either of those exceptions, BroadSign’s motion to amend should be denied as
`
`futile.
`
`1.
`
`BroadSign’s Proposed Second Amended Complaint Does Not Plead
`An Obligation To Indemnify Its Customers.
`
`As this Court noted in its order on T-Rex’s motion to dismiss, “‘requests for
`
`indemnification,’ without an allegation of Plaintiff’s ‘obligation to indemnify, do not create
`
`jurisdiction.’” D.I. 40 at 9 (citing Microsoft Corp. v. DataTern, Inc., 755 F.3d 899, 904 (Fed.
`
`
`
`4
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 8 of 12
`
`Cir. 2014)). However, BroadSign’s proposed second amended complaint still does not concede
`
`that it has an obligation to indemnify its customers. Rather, BroadSign again merely alleges that
`
`its customers “have . . . demanded indemnification from BroadSign.” D.I. 44-1 ¶ 44; see also
`
`D.I. 23 (Beauchesne Decl.), Exh. D (“We write to inquire whether BroadSign intends to
`
`indemnify HMN in the T-Rex matter pursuant to the license agreement between BroadSign and
`
`HMN.”); Exh. I (“JCDecaux hereby provides notice that it seeks indemnification from
`
`BroadSign”); and Exh. J (providing “notice of a potential obligation to indemnify.”) (emphasis
`
`added). As this Court’s order and the caselaw make clear, a customer’s request for
`
`indemnification by itself does not create standing and therefore does not provide a basis for
`
`jurisdiction over BroadSign’s declaratory judgment action. Microsoft, 755 F.3d at 904.
`
`2.
`
`BroadSign’s Proposed Second Amended Complaint Does Not
`Adequately Plead Allegations of Indirect Infringement.
`
`In its order on the motion to dismiss, this Court found that BroadSign’s prior complaint
`
`failed to plead that BroadSign “knew its product was especially made or especially adapted for
`
`use in an infringement of the [Patents-in-Suit]” or that “the [software] is not a staple article or
`
`commodity of commerce suitable for substantial noninfringing use.” D.I. 40 at 10 (citing Arris
`
`Group v. British Telecomm, 639 F.3d 1368, 1376 (Fed. Cir. 2011)). BroadSign’s motion to
`
`amend is futile because its proposed second amended complaint fails to adequately address those
`
`deficiencies.
`
`As to whether BroadSign “knew its product was especially made or especially adapted
`
`for use in an infringement,” BroadSign misapplies the relevant legal standard, instead arguing
`
`that it has “alleged that it has knowledge that its products are especially made or especially
`
`adapted for use in providing the functionality that T-Rex accuses of infringement.” Pl.’s Mem.
`
`at 7 (emphasis added); D.I. 44-1 ¶ 42. But that is not the standard for contributory infringement
`
`
`
`5
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 9 of 12
`
`(35 U.S.C. § 271(c)), nor is it the standard set forth by the Federal Circuit in the Arris case.
`
`Rather, the standard is whether “the supplier knew its product was ‘especially made or especially
`
`adapted for use in an infringement’ of the patent.” Arris Group v. British Telecomm, 639 F.3d
`
`1368, 1376 (Fed. Cir. 2011). As a component of that knowledge requirement, at the time of the
`
`sale constituting contributory infringement, the contributory infringer must have “knowledge of
`
`the patent in suit and knowledge of patent infringement.” Commil USA, LLC v. Cisco Systems,
`
`Inc., 135 S. Ct. 1920, 1926 (2015).
`
`Although BroadSign’s proposed second amended complaint alleges that T-Rex has
`
`accused “functionalities implemented by BroadSign’s own software solutions” of infringement
`
`(Pl.’s Mem. at 6; D.I. 44-1 ¶¶ 32-41), BroadSign’s motion fails to meaningfully address the
`
`knowledge requirement. That is, BroadSign’s proposed second amended complaint fails to
`
`allege that, at the time that the alleged act of contributory infringement occurred, BroadSign
`
`knew of the patent or that its sale constituted patent infringement. Indeed, BroadSign cannot
`
`allege that T-Rex’s amended complaint in ContextMedia provided it with the requisite
`
`knowledge because it was filed after this case was filed. D.I. 44-1 ¶ 32 (referring to amended
`
`complaint in ContextMedia filed on July 11, 2016); D.I. 1 (original complaint in this case filed
`
`on June 16, 2016); Benitec Australia, Ltd. v. Nucleonics, Inc., 495 F. 3d 1340, 1344 (Fed. Cir.
`
`2007) (“The burden is on the party claiming declaratory judgment jurisdiction to establish that
`
`such jurisdiction existed at the time the claim for declaratory relief was filed and that it has
`
`continued since.”). Moreover, BroadSign certainly fails to allege that T-Rex’s allegations
`
`against BroadSign’s customers constituted an “implicit assertion” that BroadSign had sold
`
`products knowing of the Patents-In-Suit and the infringement thereof. See Arris Group, 639
`
`F.3d at 1375-76.
`
`
`
`6
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 10 of 12
`
`As to the requirement that “the [software] is not a staple article or commodity of
`
`commerce suitable for substantial noninfringing use,” BroadSign’s new complaint merely adds
`
`the cursory allegation that “BroadSign’s hardware and software solutions . . . are built to order
`
`for its customers.” Pl.’s Mem. at 7; D.I. 44-1 ¶ 46. But the Arris test requires that BroadSign
`
`plead facts showing that the patent owner’s allegations against customers are sufficient to
`
`constitute “an implicit assertion that the supplier has indirectly infringed the patent.” Arris
`
`Group, 639 F.3d at 1375-76. Thus, as demonstrated in Arris, the focus is on the statements made
`
`by the patent owner—and whether they constitute an “implicit assertion that the supplier has
`
`indirectly infringed the patent”—not facts which BroadSign can independently allege. See Arris
`
`Group, 639 F.3d at 1378 (finding element (d) satisfied because the patent owner had alleged
`
`“alleges that Arris' CMTSs and E-MTAs were designed specifically for use under the DOCSIS
`
`and PacketCable standards for VoIP”). Here, unlike Arris, BroadSign points to no statement by
`
`T-Rex alleging or implying that BroadSign’s products are not a staple article or commodity of
`
`commerce capable of substantial non-infringing use.
`
`Because BroadSign’s proposed second amended complaint fails to cure the deficiencies
`
`identified by the Court in its order on the motion to dismiss, leave to amend should be denied as
`
`futile.
`
`C.
`
`Amendment Would Be Futile Because This Case is Moot
`
`As noted above, an additional basis for denying leave to amend is the fact that,
`
`subsequent to the briefing on T-Rex’s motion to dismiss, all of T-Rex’s litigation against
`
`BroadSign’s customers has been resolved. Daniels Decl. Exhs. A, B1; D.I. 23 ¶ 24; D.I. 44-1 ¶
`
`29. Therefore, BroadSign cannot point to anymore ongoing or imminent conduct that is in
`
`1 Because these documents are publicly filed and available on PACER, this Court can take
`judicial notice of them. See Fed. R. Evid. 201(b)(2).
`
`
`
`7
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 11 of 12
`
`anyway related to BroadSign. Moreover, it is appropriate to consider these post-filing
`
`developments because BroadSign’s proposed second amended complaint itself relies on post-
`
`filing conduct. D.I. 44-1 ¶¶ 4, 16-21, 32 (citing to events in late June and July of 2016).
`
`Accordingly, because any potential controversy relating to litigation against BroadSign’s
`
`customers is now moot, amendment should be denied as futile.
`
`V.
`
`CONCLUSION
`
`BroadSign’s motion to amend should be denied as futile because BroadSign’s proposed
`
`second amended complaint still fails to establish a case or controversy between BroadSign and
`
`T-Rex, and, in any event, any alleged controversy is now moot because T-Rex’s cases against
`
`BroadSign’s customers have now concluded.
`
`Dated: February 14, 2018
`
`Respectfully submitted,
`
`
`
`/s/ Steven R. Daniels
`Steven R. Daniels (admitted pro hac vice)
`FARNEY DANIELS PC
`800 S. Austin Ave., Suite 200
`Georgetown, Texas 78626
`Tel: (512) 582-2828
`Fax: (512) 582-2829
`sdaniels@farneydaniels.com
`
`Attorneys for Defendant
`T-Rex Property, AB
`
`
`
`
`
`
`8
`
`

`

`Case 1:16-cv-04586-LTS Document 48 Filed 02/14/18 Page 12 of 12
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on February 14, 2018, I electronically filed the foregoing filing with
`
`the Clerk of Court using the CM/ECF system which will send notification of such filing via
`
`electronic mail to all counsel of record.
`
`
`
`
`
`/s/ Steven R. Daniels
`Steven R. Daniels
`
`
`
`9
`
`

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