Withrow Networks, Inc. v. Google, LLC

CourtDistrict Court, N.D. California
DecidedJanuary 21, 2025
Docket5:24-cv-03203
StatusUnknown

This text of Withrow Networks, Inc. v. Google, LLC (Withrow Networks, Inc. v. Google, LLC) is published on Counsel Stack Legal Research, covering District Court, N.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

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

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 WITHROW NETWORKS, INC., Case No. 5:24-cv-03203-PCP

8 Plaintiff, ORDER DENYING MOTION TO 9 v. DISMISS

10 GOOGLE, LLC, et al., Re: Dkt. No. 35 Defendants. 11

12 Plaintiff Withrow Networks, Inc. alleges that defendants Google, LLC and YouTube, LLC 13 infringe its patent, which relates to multimedia streaming. Defendants move to dismiss the 14 complaint, contending that the claims of the asserted patent are not patent eligible under 35 U.S.C. 15 § 101. For the following reasons, the Court denies the motion to dismiss. 16 BACKGROUND 17 Withrow owns U.S. Patent No. 10,771,849 (“the ’849 patent”). The underlying patent 18 application was filed in 2005, and the patent, titled “Multimedia System for Mobile Client 19 Platforms, was issued on September 8, 2020. The patent’s claims generally relate to the 20 transmission and playback of segmented multimedia on mobile devices over wireless networks. 21 Claim 1 of the ’849 patent recites: 22 1. A method comprising: 23 receiving audio and video segments encoded in a digital encoding format and with an encoding rate; wherein, said audio and video 24 segments are associated with object parameters and supplied host path identification to form multimedia objects; 25 requesting by a multimedia player, transmission of said multimedia 26 objects; wherein said multimedia objects are located using http and received by said multimedia player from servers using a wireless 27 connection; playing back received multimedia objects by the multimedia player, 1 wherein the multimedia player is configured to play multimedia objects in a sequence such that fluidity, video quality and audio 2 quality are maintained by selecting a plurality of said multimedia objects that reflect available network bandwidth, autonomously 3 adjusting said selection and playback according to the multimedia object parameters and supplied host path identification, and by 4 utilizing optimized decoding processes to maintain quality playback. 5 6 According to Withrow, the problem that the ’849 patent sought to solve was the poor, 7 inconsistent quality of mobile streaming caused by varying network conditions, differing hardware 8 capacities, and server-oriented architecture. At the time of the patent’s 2005 filing date, there were 9 significant problems with streaming on mobile devices.1 Users experienced suboptimal video 10 playback, including popping sounds, black screens, and other artifacts that diminished their 11 experience. These problems were the result of several factors. First, mobile internet networks 12 experienced fluctuations in available data capacity and wireless devices could not account for 13 these variations, leading to high latency. The available software at the time did not adapt the size 14 of streamed content based on the specific conditions of the particular player. Second, there were a 15 variety of different mobile devices with different technological needs and capacities. Because the 16 available streaming technology did not adapt to these individual client/player requirements, 17 streaming was forced to target the lowest common denominator, resulting in a single low-quality 18 stream. Third, streaming was centered on a server monitoring and controlling the streaming 19 process. This model, where the server pushed data to the client, required server management of the 20 selected data stream and resulted in a more complex, data intensive, and expensive architecture. 21 The invention purportedly enables more fluid, high-quality streaming by teaching what is 22 now known as adaptive multi bitrate (ABR) streaming. ABR streaming is a method for delivering 23 video content over the internet that adjusts the quality of the stream based on the viewer’s network 24 conditions and device capabilities. It does this by employing file-based protocols that enable the 25 use of client-driven (rather than server-driven) streaming solutions. According to Withrow, the 26 27 1 ’849 patent teaches a method whereby: (a) audio and video is received and sliced into segments at 2 a specified data rate, whereby each segment is associated with parameters describing the 3 characteristics and location of the segment with which it is associated, (b) thereby permitting the 4 use of file-based internet protocols, (c) so a client media player can select the most appropriate 5 stream segment, and (d) decode for playback in a manner that minimizes computational overhead. 6 Withrow filed this lawsuit against Google and YouTube in May 2024. Defendants now 7 move to dismiss pursuant to Rule 12(b)(6). 8 LEGAL STANDARDS 9 I. Rule 12(b)(6) 10 Federal Rule of Civil Procedure 8(a)(2) requires a complaint to include a “short and plain 11 statement of the claim showing that the pleader is entitled to relief.” If the complaint fails to state a 12 claim, the defendant may move for dismissal under Federal Rule of Civil Procedure 12(b)(6). 13 Dismissal is required if the plaintiff fails to allege facts allowing the Court to “draw the reasonable 14 inference that the defendant is liable for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 15 678 (2009). “Dismissal under Rule 12(b)(6) is appropriate only where the complaint lacks a 16 cognizable legal theory or sufficient facts to support a cognizable legal theory.” Mendiondo v. 17 Centinela Hosp. Med. Ctr., 521 F.3d 1097, 1104 (9th Cir. 2008). To survive a Rule 18 12(b)(6) motion, a plaintiff need only plead “enough facts to state a claim to relief that is plausible 19 on its face.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). 20 In considering a Rule 12(b)(6) motion, the Court must “accept all factual allegations in the 21 complaint as true and construe the pleadings in the light most favorable” to the non-moving 22 party. Rowe v. Educ. Credit Mgmt. Corp., 559 F.3d 1028, 1029–30 (9th Cir. 2009). While legal 23 conclusions “can provide the [complaint’s] framework,” the Court will not assume they are correct 24 unless adequately “supported by factual allegations.” Iqbal, 556 U.S. at 679. Courts do not “accept 25 as true allegations that are merely conclusory, unwarranted deductions of fact, or unreasonable 26 inferences.” In re Gilead Scis. Secs. Litig., 536 F.3d 1049, 1055 (9th Cir. 2008) (quoting Sprewell 27 v. Golden State Warriors, 266 F.3d 979, 988 (9th Cir. 2001)). II. Patent eligibility under 35 U.S.C. § 101 1 35 U.S.C. § 101 makes patentable “any new and useful process, machine, manufacture, or 2 composition of matter, or any new and useful improvement thereof.” This broad provision has an 3 important exception: “Laws of nature, natural phenomena, and abstract ideas are not patentable.” 4 Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 216 (2014). A patent is “not rendered 5 ineligible ... simply because it involves an abstract concept.” Id. at 217.

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

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Microsoft Corp. v. i4i Ltd. Partnership
131 S. Ct. 2238 (Supreme Court, 2011)
Mendiondo v. Centinela Hospital Medical Center
521 F.3d 1097 (Ninth Circuit, 2008)
Rowe v. Educational Credit Management Corp.
559 F.3d 1028 (Ninth Circuit, 2009)
In Re Gilead Sciences Securities Litigation
536 F.3d 1049 (Ninth Circuit, 2008)
Brown v. Marsh
713 F. Supp. 20 (District of Columbia, 1989)
Enfish, LLC v. Microsoft Corporation
822 F.3d 1327 (Federal Circuit, 2016)
Affinity Labs of Texas, LLC v. amazon.com Inc.
838 F.3d 1266 (Federal Circuit, 2016)
Recognicorp, LLC v. Nintendo Co., Ltd.
855 F.3d 1322 (Federal Circuit, 2017)
Aatrix Software, Inc. v. Green Shades Software, Inc.
882 F.3d 1121 (Federal Circuit, 2018)
Data Engine Technologies LLC v. Google LLC
906 F.3d 999 (Federal Circuit, 2018)
Sprewell v. Golden State Warriors
266 F.3d 979 (Ninth Circuit, 2001)

Cite This Page — Counsel Stack

Bluebook (online)
Withrow Networks, Inc. v. Google, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/withrow-networks-inc-v-google-llc-cand-2025.