Synopsys, Inc v. AzurEngine Technologies, Inc

[6] UNITED STATES DISTRICT COURT [7] SOUTHERN DISTRICT OF CALIFORNIA [8] 9 SYNOPSYS, INC., CASE NO. 19cv1443-LAB (AGS) 10 Plaintiff, ORDER GRANTING IN PART AND 11 vs. DENYING IN PART PLAINTIFF’S MOTION FOR TEMPORARY 12 AZURENGINE TECHNOLOGIES, INC., RESTRAINING ORDER, EXPEDITED et al., DISCOVERY, AND ORDER TO SHOW [13] Defendants. CAUSE [Dkt. 4] [15] 16 Currently before the Court is Plaintiff Synopsys, Inc.’s Motion for (1) a Temporary 17 Restraining Order; (2) an Order to Show Cause re: Preliminary Injunction; and (3) an 18 Order for Expedited Discovery. Dkt. 4. For the reasons below, that motion is GRANTED 19 IN PART and DENIED IN PART. 20 BACKGROUND 21 1. Synopsys’ EDA Software 22 Synopsys is one of the world’s leading producers of Electronic Design Automation 23 (“EDA”) software, which are tools used by microchip manufacturers to design, verify, and 24 simulate the performance of electronic circuits. Synopsys offers a suite of EDA tools that 25 are the result of “hundreds of millions of dollars of investment as well as years of 26 Synopsys’ time.” Dkt. 4 (“TRO”) at 3. 27 / / / [28] 1 Synopsys does not sell ownership, copyright, or other intellectual property rights 2 to its EDA software. Instead, the company permits access to its tools only through 3 customized licenses that grant the purchaser limited rights. Synopsys employs strict 4 controls that monitor and limit access in accordance with each licensee’s specific terms. 5 The central feature of these access-control measures is a license key system that 6 requires licensees to input an encrypted key code that can only be obtained from 7 Synopsys. The system monitors a licensee’s use of the software to ensure compliance 8 with the licensee’s specific contract terms. 9 2. AzurEngine’s Alleged Infringement 10 AzurEngine is a San Diego-based startup founded in 2016. The company’s stated 11 mission is to develop “a state-of-art reconfigurable processor for next generation deep 12 learning technologies.” Id. at 5. By all accounts, AzurEngine has moved quickly to meet 13 that goal. It developed its first prototype chip within one year of its founding, and has 14 since embarked on a “major multi-million dollar chipset design project” with an unnamed 15 Chinese business partner. Dkt. 7 (“Opp.”) at 2. 16 Beginning in June 2019, Synopsys’ monitoring programs detected “call-home 17 data” indicating that individuals associated with AzurEngine—a company with no current 18 license from Synopsys—had impermissibly accessed its EDA software. According to 19 Synopsys, this call-home data indicates that AzurEngine has used counterfeit license 20 keys to circumvent Synopsys’ software protections more than 15,000 times. For its part, 21 AzurEngine says it believed it had permission to access Synopsys software because its 22 Chinese business partner “purported to provide AzurEngine with valid licensed access to 23 the Synopsys software.” Id. 24 ANALYSIS 25 Synopsys claims that AzurEngine’s unauthorized use of its software constitutes a 26 violation of the Digital Millennium Copyright Act (“DMCA”). It seeks a temporary 27 restraining order enjoining AzurEngine from further accessing its software. It also seeks [28] 1 expedited discovery and an order instructing AzurEngine to show cause why a preliminary 2 injunction shouldn’t be entered against it. 3 1. Temporary Restraining Order 4 The standard for obtaining a temporary restraining order is identical to the standard 5 for obtaining a preliminary injunction, with the primary difference being duration: 6 preliminary injunctions remain in force throughout the litigation, while TROs, which are 7 traditionally entered on an ex parte basis, are limited to 28 days. See Fed. R. Civ. Pro. 8 65(b)(2). To obtain either form of relief, Synopsys must establish “that [it] is likely to 9 succeed on the merits, that [it] is likely to suffer irreparable harm in the absence of 10 preliminary relief, that the balance of equities tips in [its] favor, and that an injunction is in 11 the public interest.” Stormans, Inc. v. Selecky, 586 F.3d 1109, 1127 (9th Cir. 2009) 12 (quoting Winter v. Nat. Res. Def. Council, Inc., 555 U.S. 7, 20 (2008)). Each of these 13 factors is met here. 14 a. Synopsys Is Likely to Succeed on the Merits. 15 To prevail on its claim for relief under the DMCA, Synopsys must prove that (1) its 16 software included a technological measure that effectively controls access, (2) 17 AzurEngine circumvented that technological measure, and (3) the Synopsys software that 18 AzurEngine accessed is a work protected under the Copyright Act. See 17 U.S.C. 19 § 1201(a)(1)(A); MDY Indus., LLC v. Blizzard Entm't, Inc., 629 F.3d 928, 952 (9th Cir. 20 2010) (Congress, in enacting § 1201(a)(1)(A), “created a distinct anti-circumvention right 21 . . . without an infringement nexus requirement.”). 22 i. Synopsys’ Software “Effectively Controls” Access. 23 First, Synopsys’ software “effectively controls” access to its suite of EDA software. 24 The software will not run without the licensee “checking out” a license key from a server 25 that is designed to only grant such keys to approved licensees. Every court to consider 26 the issue has found that similar methods of license-control satisfy the “effectively controls” 27 requirement of the DMCA, and this Court does too. See, e.g., Synopsys, Inc. v. [28] 1 InnoGrit, Corp., 2019 WL 2617091 , at *3 (N.D. Cal. 2019); Dish Network, L.L.C. v. Vicxon 2 Corp., 2013 WL 3894905 , at *6 (S.D. Cal. 2013). 3 ii. AzurEngine Likely Circumvented Synopsys’ Software Controls. 4 Synopsys has also plausibly demonstrated that AzurEngine circumvented its 5 controls through the use of counterfeit license keys. These counterfeit keys work by 6 effectively tricking the company’s license-control systems into thinking AzurEngine is a 7 licensed user. As discussed above, Synopsys’ “call-home data” indicates that individuals 8 associated with AzurEngine have circumvented its license-control system at least 15,000 9 times, which is 14,999 more times than would be necessary to find a violation of the 10 DMCA. See Synopsys, Inc. v. InnoGrit, Corp., 2019 WL 2617091 , at *3 (N.D. Cal. 2019) 11 (concluding that the use of counterfeit license keys, among other things, constituted 12 “circumvention” under the DMCA). 13 AzurEngine’s responses on this point are unavailing. It argues, for example, that 14 its use of Synopsys software was authorized because one of its business associates— 15 an unnamed “Chinese business partner”—had “purported to provide AzurEngine with 16 valid licensed access to the Synopsys software at issue in this case.” Opp. at 2. But 17 even if it were true that AzurEngine had a valid license, that would not allow the company 18 to use counterfeit keys to circumvent Synopsys’ software protections. Even “lawful 19 purchasers” must establish that they had specific “authorization to circumvent” in order to 20 avoid DMCA liability. Disney Enterprises, Inc. v. VidAngel, Inc., 869 F.3d 848, 863 (9th 21 Cir. 2017). Because Synopsys has shown that AzurEngine likely circumvented its 22 license-control systems, it is irrelevant that AzurEngine believed it had a license to use 23 the software. 24 iii. Synopsys Likely Has a Protectable Copyright Interest in Its 25 Software Code. 26 Finally, Synopsys likely owns the copyrights to its EDA software, including the 27 specific tools at issue in this case: Design Compiler, PrimeTime, VCS, Formality, IC 28 Compiler, StarRC, and Library Compiler. Much of Synopsys’ EDA software is protected 1 by a registered copyright, which is prima facie evidence of lawful ownership over the code. 2 See 17 U.S.C. § 410 (c). And if that weren’t enough, almost all novel software code 3 constitutes a creative, original work of authorship that is automatically protected under 4 the Copyright Act. See Sega Enters. Ltd. v. Accolade, Inc., 977 F.2d 1510, 1519 (9th Cir. 5 1992), as amended (Jan. 6, 1993) (“[T]he Copyright Act unambiguously extended 6 copyright protection to computer programs.”). 7 iv. Extraterritoriality is a Red Herring. 8 Based on the factors above, the Court concludes that Synopsys is likely to succeed 9 on the merits of its DMCA claim. Largely conceding this, AzurEngine’s opposition instead 10 focuses on the red herring of extraterritoriality. Specifically, it argues that although it is a 11 California-based company with engineers operating in the United States, the access to 12 Synopsys’ software occurred through its servers in China. Since the “access” technically 13 occurred abroad, AzurEngine argues that enjoining its behavior would violate the rule 14 against applying United States law extraterritorially. 15 But extraterritorial application of the DMCA is irrelevant here. As the Supreme 16 Court has noted, “[i]f the conduct relevant to the statute’s focus occurred in the United 17 States, then the case involves a permissible domestic application even if other conduct 18 occurred abroad.” RJR Nabisco, Inc. v. European Cmty., 136 S. Ct. 2090, 2101 (2016). 19 The “focus” of section 1201(a)(1) is to prevent circumvention of technological measures 20 to gain access to copyrighted works. See 17 U.S.C. § 1201 (a)(1); MDY Indus., 629 F.3d 21 at 944-45 . Using the Supreme Court’s rubric from RJR Nabisco, there is plainly no 22 extraterritoriality problem here. The conduct that is the focus of § 1201(a)(1)—gaining 23 access to copyrighted works by circumventing technological access controls—“occurred 24 in the United States,” and thus application of the DMCA to AzurEngine’s U.S.-based 25 circumventions “involves a permissible domestic application [of the DMCA] even if other 26 conduct occurred abroad.” RJR Nabisco, 136 S. Ct. at 2101 . 27 AzurEngine’s argument has also been flatly rejected by numerous courts. Were 28 its argument correct, “large-scale criminal copyright pirates could avoid United States 1 copyright liability simply by locating their servers outside the United States.” Spanski 2 Enters., Inc. v. Telewizja Polska, S.A., 883 F.3d 904, 915 (D.C. Cir. 2018). But that’s not 3 the law. Because it’s undisputed that AzurEngine’s alleged DMCA violations occurred “at 4 least in part[] in the United States,” its extraterritoriality defense fails. Litecubes, LLC v. 5 N. Light Prods., Inc., 523 F.3d 1353, 1372 (Fed. Cir. 2008). 6 b. Synopsys Will Suffer Irreparable Harm in the Absence of an Injunction, 7 and the Balance of Equities Tip in Its Favor. 8 A party seeking an injunction must establish that it “is likely to suffer irreparable 9 harm in the absence of preliminary relief [and] that the balance of equities tips in [its] 10 favor.” Winter, 555 U.S. at 20 . 11 In the DMCA context, irreparable harm may be established by evidence that 12 circumvention is undermining the copyright owner’s negotiating position, damaging 13 goodwill with licensees, threatening the copyright owner’s business model, risking the 14 copyright owner’s market share, causing reputational harm to the copyright owner or its 15 works, and/or enabling third parties to infringe the owner’s copyrights. VidAngel, 869 F.3d 16 at 865 (examples 1-3); Apple Inc. v. Psystar Corp., 673 F. Supp. 2d 943, 946 (N.D. Cal. 17 2009), aff'd, 658 F.3d 1150 (9th Cir. 2011) (examples 4-6). The evidence submitted by 18 Synopsys shows that AzurEngine’s conduct results in at least some of these harms. 19 The declaration submitted by Norman F. Kelly, Synopsys’ Director of License 20 Compliance, for example, supports a finding that circumvention like AzurEngine’s 21 undermines Synopsys’ negotiating position with other licensees and threatens its 22 business model. He notes in that declaration that customers have asked him “why [they] 23 should pay for Synopsys software if [they] can get the software for free elsewhere?” Dkt. 24 11-1 (“Suppl. Kelly Decl.”) at ¶ 16. In his estimation, this mentality causes the company 25 to “lose hundreds of millions of dollars to piracy every year.” Id. Circumvention also 26 causes a loss of goodwill between paying customers and Synopsys. The companies that 27 choose to pay for Synopsys software find themselves at a price disadvantage relative to 28 competitors that choose to circumvent the company’s controls and receive the software 1 for free. Id. at ¶ 15. According to Synopsys, this dynamic leads to an “uneven playing 2 field” and, ultimately, loss of goodwill. The dynamic also creates downward pricing 3 pressure, as the company’s paying customers insist on lower prices to compete with non4 paying pirates. See Synopsys, Inc. v. InnoGrit, Corp., 2019 WL 2617091 , at *3 (N.D. Cal. 5 2019). Such losses are difficult—if not impossible—to quantify, and thus constitute 6 irreparable harm. 7 The balance of the equities also tips in Synopsys’ favor. On one side of the ledger 8 is the irreparable harm to Synopsys and the strong public interest in enforcing the DMCA 9 and federal copyright law generally. On the other side of the ledger is the, frankly, 10 audacious claim by AzurEngine that an injunction could “be devastating” because 11 “AzurEngine has been using the Synopsys software as a necessary and critical tool in a 12 major circuit design project that is currently underway.” Opp. at 3. Even a two-week 13 suspension, it claims, “could cause major delays, missed milestones, and significant costs 14 to AzurEngine.” Id. As Synopsys correctly points out, this argument carries no weight. 15 Any benefit AzurEngine has received from impermissibly accessing Synopsys’ software 16 was ill-gotten. That it may prefer to continue using the software doesn’t mean it is entitled 17 as a matter of law to do so. It may well be the case that AzurEngine believed its business 18 partner had provided it with a valid license, but it is incumbent on parties to ensure they 19 are not violating the law, not on the Court to rescue them when they’ve done so, and 20 nothing prevents AzurEngine from now lawfully acquiring a license from Synopsys by 21 paying for it. 22 In short, Synopsys has demonstrated irreparable harm and that the balance of 23 equities tip in its favor. 24 c. An Injunction Is in the Public Interest 25 The public interest is also served by an injunction here. “[T]he public has an 26 interest in the enforcement of . . . statutes,” Dish Network, L.L.C. v. SatFTA, 2011 WL 27 856268, at *8 (N.D. Cal. 2011) (citing Coxcom, Inc. v. Chaffee, 536 F.3d 101, 112 (1st 28 Cir. 2008)), and copyright statutes are no exception. In cases related to the DMCA, courts 1 ordinarily presume that an injunction will serve the public interest if the copyright holder 2 shows a likelihood of success on the merits. See, e.g., Lilith Games (Shanghai) Co. v. 3 UCool, Inc., 2015 WL 5591612 , at *13 (N.D. Cal. 2015) (“If evidence of infringement is 4 strong, then the public interest favors its abatement given that the public has an interest 5 in seeing the copyright laws enforced.”). Because the Court has already concluded that 6 Synopsys is likely to prevail on the merits, it likewise finds that the public interest would 7 be served by entering the injunction. 8 d. TRO versus Preliminary Injunction 9 Having concluded that Synopsys is entitled to some form of an injunction, the Court 10 now turns to the specifics of the remedy. As discussed above, the standards for a TRO 11 and preliminary injunction differ only in timing—preliminary injunctions last throughout the 12 case, while TROs may generally last no longer than 28 days. Although Synopsys 13 requested entry of an ex parte TRO, the normal framework for a TRO doesn’t apply here 14 because AzurEngine is aware of the action and has had chance to submit briefing in 15 opposition. Cf. Granny Goose Foods, Inc. v. Teamsters, 415 U.S. 423, 438-39 (1974) 16 (“The stringent restrictions imposed . . . by Rule 65 on the availability of ex parte 17 temporary restraining orders reflect the fact that our entire jurisprudence runs counter to 18 the notion of court action taken before reasonable notice and an opportunity to be heard 19 has been granted both sides of a dispute.”). Given this opportunity for briefing, the Court 20 will instead construe Synopsys’ request for a TRO as a motion for preliminary injunction. 21 See, e.g., VanLeeuwen v. Farm Credit Admin., 577 F. Supp. 264, 278 (D. Or. 1983) (“The 22 application for a temporary restraining order will be treated as one for a preliminary 23 injunction where, as here, defendants have been able to present their opposition.”) (citing 24 Levas and Levas v. Village of Antioch, Ill., 684 F.2d 446, 448 (7th Cir. 1982)). This has 25 the primary advantage of allowing the parties additional time for discovery. Were the 26 Court to follow Synopsys’ suggestion—that is, enter a TRO and issue an order to show 27 cause directing AzurEngine to demonstrate why that shouldn’t be converted to a 28 preliminary injunction—the parties would be required to conduct discovery and fully brief 1 the order to show cause within 28 days, a tight window to say the least. Instead, the 2 Court will enter a preliminary injunction and give AzurEngine the opportunity, at some 3 later date, to dissolve the injunction. It may seem like a matter of semantics, but it’s the 4 right course of action here. 5 Synopsys’ Ex Parte Motion for a TRO, construed as a Motion for Preliminary 6 Injunction, is GRANTED.1 If discovery reveals information showing that this decision is 7 in error, AzurEngine may move to dissolve the injunction at some later date. Synopsys’ 8 Motion for an Order to Show Cause is DENIED AS MOOT. 9 2. Expedited Discovery 10 Federal Rule of Civil Procedure 26(d) allows for discovery prior to a Rule 26(f) 11 conference. “In the Ninth Circuit, courts use the ‘good cause’ standard to determine 12 whether discovery should be allowed to proceed prior to a Rule 26(f) conference.” Rovio 13 Entm't Ltd. v. Royal Plush Toys, Inc., 907 F. Supp. 2d 1086, 1099 (N.D. Cal. 2012). “Good 14 cause may be found where the need for expedited discovery, in consideration of the 15 administration of justice, outweighs the prejudice to the responding party.” Semitool, Inc. 16 v. Tokyo Electron Am., Inc., 208 F.R.D. 273, 276 (N.D. Cal. 2002). “It should be noted 17 that courts have recognized that good cause is frequently found in cases involving claims 18 of infringement . . . .” Id. “Factors commonly considered in determining the 19 reasonableness of expedited discovery include, but are not limited to: ‘(1) whether a 20 preliminary injunction is pending; (2) the breadth of the discovery requests; (3) the 21 purpose for requesting the expedited discovery; (4) the burden on the defendants to 22 comply with the requests; and (5) how far in advance of the typical discovery process the 23 request was made.’” Am. LegalNet, Inc. v. Davis, 673 F. Supp. 2d 1063, 1067 (C.D. Cal. 24 2009) (quoting Disability Rights Council of Greater Wash. v. Wash. Metro. Area Transit [26] 1 The Court declines to require Synopsys to post a $1,000,000 bond. The bond 27 requirement in Fed. R. Civ. Pro. 65(c) is discretionary, especially where the plaintiff is likely to succeed on the merits and the injunction is in the public interest. See Johnson 28 v. Couturier, 572 F.3d 1067, 1086 (9th Cir. 2009). Further, AzurEngine has submitted no 1 Auth., 234 F.R.D. 4, 6 (D.D.C. 2006)). Taken as a whole, these factors cut against 2 permitting expedited discovery here. 3 (i) Whether a preliminary injunction is pending. Given that the Court has 4 already determined that a preliminary injunction should issue, this factor cuts against 5 granting expedited discovery. Further, as AzurEngine is now subject to an injunction, the 6 company has every incentive to move to ordinary discovery quickly so that they can then 7 move to dissolve the injunction, if appropriate. 8 (ii) The breadth of the discovery requests. Synopsys seeks to forensically 9 image and then analyze the devices on which AzurEngine is accessing and using 10 Synopsys software. According to Synopsys, “[t]his information is resident only on 11 AzurEngine’s computers and gathering it is easily accomplished by a forensic expert who 12 can image the devices.” TRO at 18 (emphasis in original). AzurEngine argues that some 13 of the desired information may be on Chinese servers that may be difficult to access, but 14 Synopsys correctly points out that even if some of the subject servers are in China, the 15 U.S.-based computers used to remotely access those Chinese servers nonetheless 16 contain valuable forensic evidence. The request for discovery is not especially broad, so 17 this factor cuts in favor of permitting expedited discovery. 18 (iii) The purpose of requesting the discovery. The purpose of Synopsys’ 19 request for expedited discovery is “to ensure that electronic evidence that is material to 20 this litigation is not altered, deleted, destroyed or otherwise lost in the ordinary course of 21 AzurEngine’s business.” Id. But AzurEngine has implemented a litigation hold, see Dkt. 22 7-1 (“Li Decl.”) at ¶ 7, and there is no evidence that the data is otherwise at risk of 23 spoliation.2 See Midwest Sign & Screen Printing Supply Co. v. Dalpe, 2019 WL 2067867 , 24 at *13 (D. Minn. 2019) (denying expedited discovery where “[t]he Parties have already 25 implemented litigation holds” and “[t]here is no evidence suggesting a risk of spoliation.”). 26 This factor cuts against granting expedited discovery. [27] 2 Even though AzurEngine claims to have implemented a litigation hold, the Court 28 ORDERS the company to preserve any relevant evidence, as set out in the “Preliminary 1 (iv) The burden on defendant. Synopsys argues that the burden on AzurEngine 2 || is minimal because the forensic imaging can be conducted during normal business hours 3 || and that AzurEngine would be required to provide this information in the normal course 4 || of discovery regardless. Other than challenging the efficacy of Synopsys’ proposed 5 || discovery methods and suggesting that the forensic imaging would be “highly disruptive,” 6 || AzurEngine does not demonstrate that the requested discovery would be especially 7 || burdensome. This factor cuts in favor of expedited discovery. 8 (v) How far in advance the discovery request was made. As discussed, now 9 || that a preliminary injunction has been entered, the parties can proceed to ordinary 10 || discovery in a timely fashion. AzurEngine has every incentive to cooperate and move 11 || quickly through discovery so that it can then move to dissolve the injunction. This factor 12 || cuts against granting expedited discovery. 13 In all, the factors above suggest that expedited discovery is not warranted here. 14 || AzurEngine has implemented a litigation hold, which reduces any risk of spoliation, and 15 || AzurEngine has an incentive to expedite discovery without the Court setting artificial 16 || deadlines. Synopsys’ request for expedited discovery is DENIED. All future discovery 17 || disputes will be heard by Magistrate Judge Andrew G. Schopler. 18 CONCLUSION 19 Construed as a Motion for Preliminary Injunction, Synopsys’ Motion for a 20 || Temporary Restraining Order is GRANTED. Dkt. 4. Given that the Court has entered a 21 || preliminary injunction, Synopsys’ request for an Order to Show Cause re: Preliminary 22 || Injunction is DENIED AS MOOT. Dkt. 4. Synopsys’ Motion for Expedited Discovery is 23 || DENIED. Dkt. 4. To the extent relevant, AzurEngine’s Ex Parte Motion to Supplement 24 || Its Opposition is GRANTED. Dkt. 9. 25 IT IS SO ORDERED. 26 || Dated: August 15, 2019 (tm / A (by WY 27 HONORABLE LARRY ALAN BURNS 38 Chief United States District Judge 1 PRELIMINARY INJUNCTION AND PRESERVATION ORDER 2 The Court, having considered Plaintiff Synopsys, Inc.’s (“Synopsys”) motion and 3 || the opposition thereto, and having found good cause to do so, GRANTS Synopsys’ 4 || motion as follows: 5 1. The Court finds that Synopsys is entitled to a preliminary injunction. 6 || Synopsys is likely to succeed on the merits of its claim that AzurEngine Technologies, 7 || Inc. “AzurEngine”) has violated the Digital Millennium Copyright Act (“DMCA”), 17 U.S.C. 8 || §§ 1201 et seq; 9 2. The Court further finds that unless an injunction is granted, irreparable harm 10 || will result to Synopsys; and 11 3. The Court further finds that that the balance of equities tip in Synopsys’ 12 || favor, and that an injunction is in the public interest. 13 IT IS HEREBY ORDERED that defendant AzurEngine, its representatives, 14 || officers, agents, directors, affiliates, servants, employees, and all persons acting in 15 || concert or participation with it, including employees and independent contractors, are 16 || enjoined from directly or indirectly accessing, using, transferring, or copying, in any way, 17 || any Synopsys software, including but not limited to Synopsys’ Design Compiler, 18 || PrimeTime, VCS, Formality, |C Compiler, StarRC Extraction, and Library Compiler 19 || applications, without authorization from Synopsys. 20 IT IS FURTHER ORDERED that defendant AzurEngine, its representatives, 21 || officers, agents, directors, affiliates, servants, employees, and all persons acting in 22 || concert or participation with it, including employees and independent contractors, shall 23 || immediately preserve all evidence that may relate to this matter, including all hard copy 24 || materials and all computer hard drives and other electronic devices in their possession, 25 || custody, or control. 26 IT IS SO ORDERED. 27 || Dated: August 15, 2019 (ym / A (by WY 28 Honorable Larry Alan Burns Chief United States District Judge