Withrow Networks, Inc. v. Google, LLC

District Court, N.D. California·Decided August 21, 2025·No. 5:24-cv-03203·Unknown

Opinion

WITHROW NETWORKS, INC., Case No. 24-cv-03203-PCP (VKD)

Plaintiff, ORDER GRANTING IN PART AND v. DENYING IN PART DEFENDANTS' MOTION TO STRIKE PLAINTIFF'S GOOGLE, LLC, et al., INFRINGEMENT CONTENTIONS Defendants. Re: Dkt. No. 80

In this action, plaintiff Withrow Networks, Inc. (“Withrow”) alleges that Google, LLC and YouTube, LLC (collectively, “Defendants”) infringe U.S. Patent No. 10,771,849 (“the ’849 patent”). The asserted patent is generally directed to technology for adaptive bitrate streaming for multimedia. See Dkt. No. 1 ¶ 8. Defendants now move for an order striking, in part, Withrow’s infringement contentions for failure to comply with Patent Local Rule 3-1. Dkt. No. 80. Withrow opposes the motion. Dkt. No. 85. Upon consideration of the moving and responding papers, as well as the arguments presented at the July 29, 2025 hearing, the Court orders Withrow to serve amended infringement contentions that comply with the Court’s direction below. On March 8, 2025, Withrow served its Patent Local Rule 3-1 disclosures, including infringement contentions regarding five accused instrumentalities, as follows: Accused Instrumentality Claims Entity 1 The YouTube system and service with HLS, 1, 2, 3, 4, 6, 7, and 8 Defendants through any multimedia player provided by Defendants MPEG-DASH, through any multimedia player provided by Defendants 3 The Google Transcoder API system and 1, 2, 6, 7, and 8 Google service with HLS, through any multimedia player provided by Defendants 4 The Google Transcoder API system and 1, 2, 6, 7, and 8 Google service with MPEG-DASH, through any multimedia player provided by Defendants 5 The Google Live Stream API system and 1, 2, 3, 6, and 7 Google service with HLS, through any multimedia player provided by Defendants Dkt. No. 80 at 5. Asserted claims 1, 2, 3, 4, and 8 are method claims; asserted claim 6 is an apparatus claim; and asserted claim 7 is a system claim. According to Withrow, for the two accused instrumentalities involving the “YouTube system and service,” a “YouTube player” “requests and receives audio segments” from a “YouTube server.” Dkt. No. 85 at 3. For the YouTube player, Withrow specifically identifies three player “types”: (1) an iOS application, (2) an Android application, and (3) a web-based player. Id. at 3. For the two accused instrumentalities involving Google’s “Transcoder API system and service,” Withrow explains that the API allows users to convert multimedia content into various output formats, and the resulting media can be played on at least two multimedia players: (1) Shaka Player and (2) ExoPlayer. Id. For the one accused instrumentality involving Google’s “Live Stream API system and service,” Withrow explains that the API allows users to convert live video content into different output format, and the resulting media can be played on at least Shaka Player. Id. at 3, 4. For the most part, defendants do not challenge the adequacy of Withrow’s infringement contentions for the YouTube system and service instrumentalities. However, they contend that Withrow’s infringement contentions for the other three accused instrumentalities, involving Transcoder API and Live Stream API, do not adequately disclose how Google, as the purported direct infringer, meets every limitation of the asserted claims. Among other things, Patent Local Rule 3-1 requires “a party claiming patent infringement” to identify for each asserted claim “each accused apparatus, product, device, process, method, act, or other instrumentality . . . of which the party is aware.” Patent L.R. 3-1(b). This identification must be “as specific as possible,” including “by name or model number, if known.” Id. “[A]ll courts agree that the degree of specificity under [Patent] Local Rule 3-1 must be sufficient to provide reasonable notice to the defendant why the plaintiff believes it has a ‘reasonable chance of proving infringement.’” Shared Memory Graphics LLC v. Apple, Inc., 812 F. Supp. 2d 1022, 1025 (N.D. Cal. 2010) (quoting View Eng’g, Inc. v. Robotic Vision Sys., Inc., 208 F.3d 981, 986 (Fed. Cir. 2000)). The Patent Local Rules do not “require the disclosure of specific evidence nor do they require a plaintiff to prove its infringement case,” but “a patentee must nevertheless disclose what in each accused instrumentality it contends practices each and every limitation of each asserted claim to the extent appropriate information is reasonably available to it.” DCG Sys. v. Checkpoint Techs., LLC, No. 11-cv-03792-PSG, 2012 WL 1309161, at *2 (N.D. Cal. Apr. 16, 2012) (internal quotations and citation omitted). “Striking a patentee’s infringement contentions is a severe sanction that should be used sparingly and only for good cause.” Avago Techs., Inc. v. IPtronics Inc., No. 10-cv-02863-EJD, 2015 WL 4647923, at *2 (N.D. Cal. Aug. 5, 2015) (citation omitted). As a result, “motions to strike initial infringement [contentions] are frequently treated as motions to compel amendment of the infringement contentions.” Geovector Corp. v. Samsung Elecs. Co., No. 16-cv-02463-WHO, 2017 WL 76950, at *7 (N.D. Cal. Jan. 9, 2017). Defendants move to strike Withrow’s infringement contentions on several grounds. The Court addresses the parties’ arguments with respect to each ground. A. Whether the Contentions Disclose Where and How the Accused Instrumentalities Meet Each Limitation of the Asserted Claims Defendants’ principal argument is that Withrow’s infringement contentions for Transcoder API and Live Stream API rely on a “muddled hash of elements that mixes and matches functionalities form different products, services and standards,” without explaining or describing how the accused instrumentalities infringe and where each limitation is found. Dkt. No. 80 at 3, 7, 9-16. Withrow responds that its contentions provide sufficient notice of its infringement theories because its charts for Transcode API and Live Stream API contain screenshots and “raw data” showing Withrow “actually practiced the ’849 Patent claim elements using Google’s systems.” Dkt. No. 85 at 5. In other words, Withrow argues that it has adequately disclosed its infringement contentions by showing how Withrow, using a Google demo video, practiced all the steps of the claimed methods using, for example, Shaka Player, a multimedia player developed by Google that complies with a specific standard, to play back multimedia converted using Google’s Transcoder API, and by showing how those components comprise the apparatus and system claimed. Id. at 5- 7; Dkt. No. 80-5 (chart 3). The Court has carefully reviewed Withrow’s contentions for Transcoder API and Live Stream API (in combination with other components), as well as Withrow’s explanations of its contentions provided in its opposition. The Court agrees with Defendants that Withrow’s infringement contentions do not provide reasonable notice of “where and how” each limitation of each asserted claim is found because Withrow has not explicitly disclosed what its contentions are, as required by Patent Local Rule 3-1(c). Instead, Withrow relies on screenshots and snippets of text or data, with little explanation, from which it expects Defendants and the Court to infer what its contentions must be. However, it is not always self-evident from Withrow’s current disclosures how the accused instrumentalities practice each limitation of each claimed method or constitute a device or system that meets each limitation of each claimed apparatus or system. See, e.g., AbCellera Biologics Inc. v. Bruker Cellular Analysis, Inc., No. 20-cv-08624-JST (VKD), 2024 WL 1182929, at *3 (N.D. Cal. Mar. 18, 2024) (explaining the disclosure required). Withrow’s opposition, and the explanations offered at the oral argument, indicate that it can do b

Free access — add to your briefcase to read the full text and ask questions with AI

Withrow Networks, Inc. v. Google, LLC, (N.D. Cal. 2025).

Withrow Networks, Inc. v. Google, LLC (Withrow Networks, Inc. v. Google, LLC) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Shared Memory Graphics LLC v. Apple, Inc.
812 F. Supp. 2d 1022 (N.D. California, 2010)