Safecast Limited v. Google, LLC

• Court: District Court, N.D. California
• Decided: November 22, 2023
• Docket: 5:23-cv-03128
• Status: Unknown

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 SAFECAST LIMITED, Case No. 23-cv-03128-PCP

8 Plaintiff, ORDER DISMISSING COMPLAINT 9 v. WITH LEAVE TO AMEND

10 GOOGLE, LLC, Defendant. 11

12 13 In this patent case, plaintiff SafeCast Limited claims that defendant Google, LLC’s 14 advertising products infringe its patent for automating compliance with broadcasting authority 15 regulations governing the time at which certain ads may be shown. Google moves for dismissal on 16 two grounds: first, because the patent’s claims are directed to the abstract idea of “automating 17 compliance” and lack an inventive concept, and are thus ineligible for patenting under 35 U.S.C. 18 § 101; and second, because regardless of patent eligibility SafeCast fails to plausibly plead that 19 Google has infringed SafeCast’s patent. 20 Although the Court agrees that SafeCast’s patent is directed at an abstract idea, the Court 21 will not decide whether the patent must be invalidated as ineligible under Section 101 because 22 SafeCast has not plausibly pleaded infringement. The complaint will therefore be dismissed with 23 leave to amend and without prejudice to the renewal of Google’s Section 101 arguments should 24 SafeCast choose to file an amended complaint. 25 I. Background 26 SafeCast has patented a “system for automating compliance with local broadcasting 27 regulations laid down by a broadcasting authority and applicable to advertisements.” The 1 When viewers record programs to watch them later, “time-shifting … means that the recorded 2 program[s] may contain advertisements which are unsuitable for the actual time of viewing,” 3 especially since some jurisdictions regulate the time at which certain kinds of ads may be shown. 4 SafeCast’s patent first claims the following invention:

5 [1a] A system for automating compliance with local broadcasting regulations laid down by a broadcasting authority and applicable to 6 advertisements, said advertisements being provided during time- shifted viewing/listening comprises: 7 [1b] programme supply means to supply broadcast digital video/audio 8 programmes having therein periodic breaks for the insertion of advertisements; 9 [1c] advertisement supply means to supply advertisements within the 10 periodic breaks, each advertisement having associated therewith a header comprising a first field related to a local broadcasting time 11 regulation laid down by the broadcasting authority, which local broadcasting time regulation restricts the time of day at which said 12 advertisement may be shown, and a second field related to the number of times said advertisement has previously been shown during time- 13 shifted viewing;

14 [1d] rules database means containing rules relating to said local broadcasting time regulation; 15 [1e] clock means to supply a real-time clock signal; and control means 16 arranged to read said first field and said clock signal and said rules database and to apply said local broadcasting time regulation to each 17 advertisement before said advertisement is shown;

18 [1f] wherein the control means is further arranged to update the second field in the header of said advertisement when said 19 advertisement is again shown during time-shifted viewing. 20 U.S. Patent No. 9,392,302 (bracketed enumerations as indicated in SafeCast’s claim chart). This 21 claim is alleged as exemplary. 22 SafeCast accuses “Google-owned advertising products” as the infringing instrumentalities. 23 The claim chart included with SafeCast’s complaint mentions several specific Google products, 24 including YouTube TV, YouTube, and Google Ads. According to SafeCast, YouTube TV is a 25 program that lets viewers “watch live TV, on demand video, and cloud-based DVR from major 26 broadcast and popular cable networks,” and that is “available on a wide range of Set Top Boxes 27 (PVR machines).” Ads on YouTube TV are provided by the Google Ads program, which allows 1 “specify certain hours or days of the week” when they want their ads shown. Google Ads provides 2 advertisements that are “designed” to “abide by laws” and “comply with the local laws for any 3 area … ads target.” YouTube TV programs are supplied from “major broadcast and popular cable 4 networks,” and advertisements are supplied by Google Ads. SafeCast claims that “YouTube 5 enforces local regulations that it refers to as ‘Community Guidelines’” using a “combination of 6 people and technology.” SafeCast also claims that Google has a “control means” that “counts the 7 number of times an advertisement is viewed,” and speculates that “Google can provide a rules 8 database or equivalent thereof to track such rules for ensuring compliance.” SafeCast claims that 9 these accused products directly infringe one or more of the claims of its patent. 10 SafeCast filed this action in the Western District of Texas in June 2022 and amended its 11 complaint shortly thereafter. Google then moved to dismiss. In June 2023, before Google’s motion 12 was resolved, the case was transferred to this District and the motion terminated. Google then filed 13 the present motion to dismiss. This is the first time SafeCast’s claims have come before a court. 14 II. Legal Standards 15 Rule 12(b)(6) governs dismissal for “failure to state a claim upon which relief can be 16 granted.” A complaint must “plausibly suggest” that the plaintiff is entitled to relief, meaning “the 17 pleaded factual content allows the court to draw the reasonable inference that the defendant is 18 liable.” Ashcroft v. Iqbal, 556 U.S. 662, 678, 681 (2009). In patent cases, this means “allegations 19 that … articulate why it is plausible that the accused product infringes the patent claim.” Bot M8 20 LLC v. Sony Corp., 4 F.4th 1342, 1353 (Fed. Cir. 2021). The Court must “accept all factual 21 allegations in the complaint as true and construe the pleadings in the light most favorable to the 22 nonmoving party.” Rowe v. Educ. Credit Mgmt. Corp., 559 F.3d 1028, 1029–30 (9th Cir. 2009). 23 35 U.S.C. § 101 makes patentable “any new and useful process, machine, manufacture, or 24 composition of matter, or any new and useful improvement thereof.” This broad provision has an 25 important exception: “Laws of nature, natural phenomena, and abstract ideas are not patentable.” 26 Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 216 (2014). A patent is “not rendered 27 ineligible … simply because it involves an abstract concept.” Id. at 217. But it must apply that 1 Section 101, the first question is “whether the claims at issue are directed to one of those patent- 2 ineligible concepts.” Id. If so, the second question is whether the “additional elements” of the 3 claim “transform [its] nature … into a patent-eligible application.” Id. (cleaned up). This inquiry 4 involves “a search for an ‘inventive concept’ … sufficient to ensure that the patent in practice 5 amounts to significantly more than a patent upon the ineligible concept itself.” Id. (cleaned up). 6 Patents are “presumed valid.” 35 U.S.C. § 282(a). The “burden of establishing invalidity” 7 is on the party asserting it. Id. This requires “clear and convincing evidence.” Microsoft Corp. v. 8 i4i L.P., 564 U.S. 91, 95 (2011). Eligibility “is a question of law” with “underlying questions of 9 fact.” Simio, LLC v. FlexSim Software Prods., Inc., 983 F.3d 1353, 1358–59 (Fed. Cir. 2020). 10 III. SafeCast’s Patent Is Directed To an Abstract Concept. 11 Alice’s “first step … asks whether the focus of the claims is on the specific asserted 12 improvement in computer capabilities … or, instead, on a process that qualifies as an ‘abstract 13 idea’ for which computers are invoked merely as a tool.” Enfish, LLC v. Microsoft Corp., 822 F.3d 14 1327, 1335–36 (Fed. Cir. 2016). SafeCast’s patent here is directed to the abstract concept of 15 “automating compliance with … broadcast regulations.” The patent’s claims are not directed to 16 hardware or software changes that “improve the functioning of the computer”—or PVR—“itself.” 17 Cf. Alice, 573 U.S. at 225. Instead, they invoke “unspecified, generic computer[s]” as tools to 18 automate abstract processes that humans could theoretically (if less efficiently) also accomplish on 19 their own. See id. at 226; Intell. Ventures I LLC v. Symantec Corp., 838 F.3d 1307, 1318 (Fed. Cir. 20 2016) (“[N]othing in the claims … foreclose[s] them from being performed by a human.”). 21 Because the patent here is directed to an abstract idea, whether its claims are patent- 22 eligible under Section 101 turns on the second step of Alice: whether there are additional elements 23 that transform their nature into a patent-eligible invention. This is a closer legal question that may 24 turn on “underlying questions of fact.” See Simio, 983 F.3d at 1359. Because SafeCast has failed 25 to state a plausible infringement claim against Google and its existing complaint must be 26 dismissed, as discussed below, a full eligibility analysis would be premature at this point. The 27 Court will instead resolve that issue on the basis of the allegations in any amended complaint IV. SafeCast Fails To State a Plausible Patent Infringement Claim Against Google 1 Because It Does Not Identify An Applicable Broadcasting Authority or Regulation. 2 SafeCast contends that YouTube TV and other Google advertising products directly 3 infringe its patent. SafeCast’s patent claims, including claim one which is alleged as exemplary, 4 each revolve around “compliance with local broadcasting regulations laid down by a broadcasting 5 authority and applicable to advertisements.” According to the complaint and claim chart, Google 6 enforces its own “Community Guidelines” and “provides advertisements that ‘are designed’ to 7 ‘abide by laws’” and “will comply with the local laws for any area … ads target.” Dkt. No. 23-1, 8 at 1. Even assuming these allegations are true, however, they fail to “articulate why it is plausible 9 that the accused product infringes the patent claim.” See Bot M8, 4 F.4th at 1353. The reason is 10 simple: Regardless whether compliance is required, SafeCast does not identify a single 11 “broadcasting regulation laid down by a broadcasting authority” with which YouTube TV or any 12 other Google product complies. 13 First, it is questionable whether YouTube’s own “Community Guidelines” qualify as a 14 “local broadcasting regulation.” Merriam-Webster, for example, defines “regulation” as “an 15 authoritative rule dealing with details or procedure,” or “a rule or order issued by an executive 16 authority or regulatory agency of a government having the force of law.” It is doubtful that mere 17 “guidelines” meet this or any similar definition of regulation. But even assuming they do, the 18 Community Guidelines are clearly not “laid down by a broadcasting authority” as the patent’s 19 limitations require. They are instead laid down by Google itself. As the Google page that SafeCast 20 cites makes clear, these “Community Guidelines … set the rules of the road for what we don’t 21 allow on YouTube.” Dkt. No. 23-1, at 2 (citing the “YouTube Community Guidelines 22 Enforcement” webpage, available at perma.cc/93L2-53UD) (emphasis added).1 Accordingly, 23 Google’s Community Guidelines do not meet the first limitation of the claim. 24 The other potential “local broadcasting regulations” SafeCast identifies are the “laws” and 25 “local laws” with which Google purportedly claims to comply. But a close read of the Google 26 1 The Court concludes that Google’s policy webpages, which SafeCast selectively quotes in its 27 claim chart, are incorporated by reference into SafeCast’s complaint because Google’s purported 1 documents SafeCast incorporates by reference reveals that it is Google’s own advertising policies 2 || that are “designed to ... abide by applicable laws,” not the ads themselves. See Dkt. No. 23-1, at 2 3 (citing the “Google Ads policies” webpage, available at perma.cc/ELR6-FHSD). Similarly, 4 || Google’s policies say that advertisers, not ads, “must comply with the local laws and regulations 5 of any area their ads target,” which undercuts SafeCast’s assertion that Google itself automates 6 || local compliance. See id. (citing Google’s “Legal requirements” webpage, available at 7 perma.cc/3TDU-JJCU). In any case, these barebones assertions of generic legal compliance are far 8 too generalized to plausibly suggest infringement because they do not show that the “laws” in 9 question are broadcasting regulations, let alone that they are laid down by a broadcasting 10 authority, as required to state an infringement claim for this patent. See also SafeCast Ltd. v. 11 || AT&T Corp., Case No. 22-cv-00676 (W.D. Tex. Jun. 26, 2023) (dismissing infringement claims 12 || involving the same patent and a different streaming provider because “SafeCast fail[ed] to identify 5 13 a local broadcasting time regulation issued by a broadcasting authority, as required by the claim 14 || limitations”). 15 Without identifying a broadcasting regulation laid down by a local broadcasting authority a 16 || with which YouTube TV or another Google product complies, SafeCast’s infringement allegations 3 17 remain conclusory and fail to state a claim under Rule 12(b)(6). 18 Vv. Conclusion 19 For the foregoing reasons, SafeCast fails to state a plausible patent infringement claim 20 || against Google. Its complaint is therefore dismissed. SafeCast is granted leave to file an amended 21 complaint within 14 days of this order. If SafeCast does not file a new complaint within that 22 || period, the Clerk shall close the case. 23 24 IT IS SO ORDERED. 25 Dated: November 22, 2023 26

28 P. Casey Pitts United States District Judge