BSD Crown, Ltd. v. Amazon.com, Inc. et al
Filing
89
ORDER DENYING 75 MOTION FOR JUDGMENT ON THE PLEADINGS by Judge William H. Orrick. (jmd, COURT STAFF) (Filed on 1/29/2024)
1
2
3
4
UNITED STATES DISTRICT COURT
5
NORTHERN DISTRICT OF CALIFORNIA
6
BSD CROWN, LTD.,
7
Plaintiff,
8
ORDER DENYING MOTION FOR
JUDGMENT ON THE PLEADINGS
v.
9
AMAZON.COM, INC., et al.,
10
Re: Dkt. No. 75
Defendants.
11
United States District Court
Northern District of California
Case No. 3:23-cv-00057-WHO
12
Plaintiff BSD Crown, Ltd. (“BSD”) filed this case against defendants Amazon.com,
13
14
Amazon Web Services, Inc., and Twitch Interactive, Inc. (collectively, “Amazon”) for alleged
15
infringement of its patent for a method for data transmission that allows for real-time broadcasting
16
of videos and audio. Amazon filed a motion for judgment on the pleadings, arguing that the
17
patent-in-suit and its claim are ineligible under 35 U.S.C. § 101 because the claim is directed to
18
the abstract idea of collecting, packaging, and conveying data in real time. For the following
19
reasons, the motion is DENIED.
BACKGROUND
20
21
22
I.
FACTUAL BACKGROUND
BSD alleges that the defendants infringed one of its patents through their use of real-time
23
video and audio streaming technology. Complaint (“Compl.”) [Dkt. No. 1]. BSD owns the rights
24
to the disputed patent, U.S. Patent No. 6,389,473, (the “’473 Patent” or the “patent-in-suit”),
25
which is entitled “Network Media Streaming.” [Dkt. No. 1-1].
26
The ’473 Patent teaches a process for real-time transmission of video and audio broadcasts
27
using network technology. BSD alleges that prior to the invention of the ’473 Patent, real-time
28
audio and video streaming “faced technical problems that negatively affected video quality unless
1
expensive, dedicated equipment was deployed.” Compl. ¶ 23. The prior art used expensive
2
hardware to compress and transmit data from a source computer to a recipient computer, requiring
3
a non-internet link between the source computer and the server as well as a “high-cost” encoder to
4
package data for the server. ’473 Patent 1:16-47. Ultimately that meant only computers with “a
5
suitable, dedicated encoder and broadcast server” could provide real-time broadcasting. Id. 1:34-
6
47.
United States District Court
Northern District of California
7
An overarching objective of the ’473 Patent is to provide a process for real time data
8
broadcasting that does not require expensive hardware and instead uses “common, existing server
9
and network infrastructure . . . without the need for a dedicated broadcast computer system.” Id.
10
1:50-58. In other words, the goal of the patent is to improve the prior art by achieving the same
11
result—real-time data broadcasting—but “using common, universally-supported Internet
12
communication protocols,” which reduces costs and allows personal computers to remotely
13
broadcast multimedia programs. Id. 1:58-67.
14
15
16
17
18
19
20
21
22
23
24
The only independent claim in the patent is Claim 1:
A method for real-time broadcasting from a transmitting computer to one or more
client computers over a network, comprising:
providing at the transmitting computer a data stream having a given data rate;
dividing the stream into a sequence of slices, each slice having a predetermined
data size associated therewith;
encoding the slices in a corresponding sequence of files, each file having a
respective index;
and uploading the sequence to a server at an upload rate generally equal to the
data rate of the stream, such that the one or more client computers can
download the sequence over the network from the server at a download rate
generally equal to the data rate.
Id. 14:18-32.
The four objects of the patent are: (1) “to provide substantially continuous, high-bandwidth
data streaming over a network using common, existing server and network infrastructure”; (2) “to
provide data broadcasting capability, particularly for multimedia data, without the need for a
25
dedicated broadcast computer system”; (3) “to provide apparatus and methods for data
26
broadcasting at reduced cost by comparison with systems known in the art”; and (4) “to enable a
27
personal computer to remotely broadcast a multimedia program through an Internet service
28
2
1
provider (ISP) using common, universally-support Internet communication protocols.” Id. 1:50-
2
67. Multimedia “refers to images or sound or to data representative of images or of sound or a
3
combination thereof,” including text. Id. 2:32-37.
4
The specifications teach that the data stream from the transmitting computer is compressed
5
and divided into “segments or slices” of data, “preferably time slices,” and preferably each slice is
6
“assigned a respective slice index.” Id. 2:2-7. The transmitting computer monitors the data stream
7
and compresses it to align with the available bandwidth on the link between the computer and
8
server. Id. 3:14-23, 9:32-48. The sequences of slices are then wirelessly uploaded to a server over
9
a network, preferably via the File Transfer Protocol (“FTP”) internet protocol, in real time. Id.
10
2:6-11, 14:18-29.
Then, the server sends data to the client computer via an internet protocol, preferably
United States District Court
Northern District of California
11
12
HTTP. See id. 2:1-28, 14:33-35. The server sends the data by transmitting data slices at different
13
quality levels, depending on available bandwidth of the client computer. Id. 3:5-13; see also id.
14
4:39-47, 11:9-22. Preferably the data stream is transmitted using the Hypertext Transfer Protocol
15
(“HTTP”), which is “known in the art.” Id. 2:11-21. The specifications indicate that each data
16
slice is preferably in its own separate file, though they can also be contained “in a single indexed
17
file,” as both are supported by HTTP. Id. 2:21-28.
BSD alleges that its patent “resolved” technical problems in the “delivery of audio and
18
19
video to client computers”—namely, it used “common” servers and infrastructure, such as HTTP,
20
rather than expensive and specific equipment for transmitting audio and video. Compl. ¶¶ 23-24.
21
The use of HTTP also allowed scaling by easily sending the audio and video to “simultaneous
22
viewers,” which was not possible with the prior art. Id. ¶ 24. The “contrarian” and “non-
23
conventional” use of these servers and data transmission techniques also improved video quality
24
while decreasing costs. Id.
25
II.
PROCEDURAL BACKGROUND
26
The defendants filed a motion to dismiss the case, which I granted in part and denied in
27
part. [Dkt. No. 51]. Amazon.com filed a motion to certify a question for interlocutory appeal,
28
which I denied. [Dkt. No. 71]. The plaintiffs did not amend their complaint and the case
3
1
2
The defendants then filed a motion for judgment on the pleadings. [Dkt. No. 75]. BSD
3
opposed. [Dkt. No. 76]. Amazon replied. [Dkt. No. 82]. I held a hearing at which counsel for
4
both parties appeared.
5
United States District Court
Northern District of California
proceeded.
LEGAL STANDARD
6
Federal Rule of Civil Procedure (“FRCP”) 12(c) provides that “[a]fter the pleadings are
7
closed—but early enough not to delay trial—a party may move for judgment on the pleadings.”
8
Fed. R. Civ. Proc. 12(c). “Dismissal under Rule 12(c) is warranted when, taking the allegations in
9
the complaint as true, the moving party is entitled to judgment as a matter of law.” Daewoo Elecs.
10
Am. Inc. v. Opta Corp., 875 F.3d 1241, 1246 (9th Cir. 2017) (citation omitted). “[M]otions for
11
judgment on the pleadings are functionally identical to Rule 12(b)(6) motions.” Webb v. Trader
12
Joe’s Co., 999 F.3d 1196, 1201 (9th Cir. 2021) (internal quotation marks omitted) (citing United
13
States ex rel. Cafasso v. Gen. Dynamics C4 Sys., Inc., 637 F.3d 1047, 1054 n.4 (9th Cir. 2011)).
14
“[U]nder both rules, ‘a court must determine whether the facts alleged in the complaint, taken as
15
true, entitle the plaintiff to a legal remedy.’” Chavez v. United States, 683 F.3d 1102, 1108 (9th
16
Cir. 2012) (citation omitted). For both motions, dismissal may be based on either the lack of a
17
cognizable legal theory or absence of sufficient facts alleged under a cognizable legal theory.
18
Robertson v. Dean Witter Reynolds, Inc., 749 F. 2d 530, 534 (9th. Cir. 1984) (citation omitted).
19
A plaintiff’s complaint must allege facts to state a claim for relief that is plausible on its
20
face. See Ashcroft v. Iqbal, 556 U.S. 662, 677 (2009). A claim has “facial plausibility” when the
21
party seeking relief “pleads factual content that allows the court to draw the reasonable inference
22
that the defendant is liable for the misconduct alleged.” Id. Although the Court must accept as
23
true the well-pled facts in a complaint, conclusory allegations of law and unwarranted inferences
24
will not defeat an otherwise proper Rule 12(b)(6) motion. See Sprewell v. Golden State Warriors,
25
266 F.3d 979, 988 (9th Cir. 2001). “[A] plaintiff’s obligation to provide the ‘grounds’ of his
26
‘entitle[ment] to relief’ requires more than labels and conclusions, and a formulaic recitation of the
27
elements of a cause of action will not do. Factual allegations must be enough to raise a right to
28
relief above the speculative level.” See Bell Atl. Corp. v. Twombly, 550 U.S. 544, 555 (2007)
4
1
(citations and footnote omitted).
DISCUSSION
2
3
4
Alice because it is directed to ineligible subject matter—the abstract idea of real-time data
5
transmission—and because the claims do not recite significantly more than this abstract idea. See
6
D. Mot.
7
United States District Court
Northern District of California
Amazon argues that the ’473 Patent is invalid as a matter of law under 35 U.S.C. § 101 and
Title 35 of the United States Code § 101 “defines the subject matter that may be patented
8
under the Patent Act.” Bilski v. Kappos, 561 U.S. 593, 601 (2010). Under § 101, patentable
9
subject matter includes “any new and useful process, machine, manufacture, or composition of
10
matter, or any new and useful improvement thereof.” 35 U.S.C. § 101. “These categories are
11
broad, but they are not limitless.” Twilio, Inc. v. Telesign Corp., 249 F. Supp. 3d 1123, 1136
12
(N.D. Cal. 2017). “Laws of nature, natural phenomena, and abstract ideas are not patentable.”
13
Alice Corp. Pty. v. CLS Bank Int’l, 573 U.S. 208, 216 (2014) (citation omitted). This is so because
14
“they are the basic tools of scientific and technological work,” which are “free to all [persons] and
15
reserved exclusively to none.” Mayo Collaborative Servs. v. Prometheus Lab’ys, Inc., 566 U.S.
16
66, 71 (2012) (citations omitted). Allowing patent claims for such purported inventions “might
17
tend to impede innovation more than it would tend to promote it.” Id. But courts must “tread
18
carefully in construing this exclusionary principle lest it swallow all of patent law.” Alice, 573
19
U.S. at 217 (citing Mayo, 566 U.S. at 70-71). “At some level, ‘all inventions . . . embody, use,
20
reflect, rest upon, or apply laws of nature, natural phenomena, or abstract ideas.” Id. (quoting
21
Mayo, 566 U.S. at 71). Accordingly, “applications of such concepts to a new and useful end . . .
22
remain eligible for patent protection.” Id. (cleaned up) (citation omitted).
23
The two-step Alice framework distinguishes “patents that claim laws of nature, natural
24
phenomena, and abstract ideas from those that claim patent-eligible applications of those
25
concepts.” Id. First, courts must “determine whether the claims at issue are directed to a patent-
26
ineligible concept.” Id. at 218. If so, courts then assess whether “the elements of each claim, both
27
individually and ‘as an ordered combination’ . . . ‘transform the nature of the claim’ into a patent-
28
eligible application.” Id. at 217 (citation omitted).
5
Although claim construction is sometimes necessary to resolve whether a patent claim is
United States District Court
Northern District of California
1
2
directed to unpatentable subject matter, the Federal Circuit has clarified that “claim construction is
3
not an inviolable prerequisite to a validity determination under § 101.” Bancorp Servs., L.L.C. v.
4
Sun Life Assur. Co. of Can. (U.S.), 687 F.3d 1266, 1273-74 (Fed. Cir. 2012). Where the court has
5
a “full understanding of the basic character of the claimed subject matter,” the question of patent
6
eligibility may properly be resolved on the pleadings. Content Extraction & Transmission LLC v.
7
Wells Fargo Bank, Nat. Ass’n, 776 F.3d 1343, 1349 (Fed. Cir. 2014). The parties do not contest
8
that no claim construction is required to resolve this motion.
9
For the following reasons, I find that the patent is not directed to an abstract idea, and even
10
if it were, it contains an inventive concept that transforms the nature of the claim. Fundamentally,
11
Claim 1 teaches a method for data transmission between computers that uses protocols and data
12
slicing and matching. Though the object of the claim is not necessarily apparent from the claim
13
language on its own, the specification explains that this method solves for a problem in the prior
14
art—the use of expensive hardware that limits who and what kinds of computers can perform real
15
time broadcasting. The claim as contextualized by the specification, then, is directed to the
16
improvement in data transmission technology that results from using network protocols and
17
specific data slicing and matching. It is not directed to the abstract idea of data transmission and
18
collection, as Amazon asserts. In prior cases that involved patents with similarly broad language
19
(“providing” data, “encoding,” “uploading,” etc.), the patents taught only the abstract idea; they
20
did not teach methods for improving the technology. Here, though, the claim teaches the method
21
that improves the technology; it teaches the use of network and protocols instead of hardware.
22
And even if the claim language is construed as directed to the abstract idea of real-time data
23
transmission, the inventive concept—teaching the use of the networks, protocols, and data slices
24
rather than expensive, physical hardware—transforms the nature of the claim into a patent eligible
25
application.
26
I.
27
28
ALICE STEP ONE
To determine whether claims are directed to a patent-ineligible concept, the court must
“articulate with specificity what the claims are directed to and ask whether the claims are directed
6
1
to an improvement to . . . functionality versus being directed to an abstract idea.” Visual Memory
2
LLC v. NVIDIA Corp., 867 F.3d 1253, 1258 (Fed. Cir. 2017) (internal quotation marks and
3
citations omitted); see also Synopsys, Inc. v. Siemens Indus. Software Inc., No. 20-CV-04151-
4
WHO, 2023 WL 5174291, at *4 (N.D. Cal. June 30, 2023) (subsequent history omitted) (same).
United States District Court
Northern District of California
5
Although “[t]he Supreme Court has not established a definitive rule” for defining “abstract
6
idea” under step one, the Federal Circuit and Supreme Court “have found it sufficient to compare
7
claims at issue to those claims already found to be directed to an abstract idea in previous cases.”
8
Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 1334-35 (Fed. Cir. 2016) (citation omitted). The
9
Federal Circuit also has instructed that this inquiry asks “what the patent asserts to be the focus of
10
the claimed advance over the prior art.” TecSec, Inc. v. Adobe Inc., 978 F.3d 1278, 1292 (Fed.
11
Cir. 2020) (internal quotation marks and citations omitted).
12
The first step of the Alice framework does not “simply ask whether the claims involve a
13
patent-ineligible concept” but rather “applies a stage-one filter to claims, considered in light of the
14
specification, based on whether ‘their character as a whole is directed to excluded subject matter.’”
15
Enfish, 822 F.3d at 1335 (citations omitted); Hawk Tech. Sys., LLC v. Castle Retail, LLC, 60 F.4th
16
1349, 1356 (Fed. Cir. 2023) (“[Courts] focus on the language of the asserted claims, considered in
17
light of the specification.” (citing Yu v. Apple, 1 F.4th 1040, 1043 (Fed. Cir. 2021)); Stormborn
18
Techs., LLC v. Topcon Positioning Sys., Inc., 444 F. Supp. 3d 1119, 1124 (N.D. Cal. 2020)
19
(“[T]he claims are to be read as a whole in light of the specification.”). In doing so, the court must
20
avoid “overgeneralizing” those claims or stating them at too “high [of a] level of abstraction.”
21
TecSec, Inc., 978 F.3d at 1293 (internal quotation marks and citations omitted); see also
22
RecogniCorp, LLC v. Nintendo Co., 855 F.3d 1322, 1326 (Fed. Cir. 2017) (noting the relevant
23
inquiry focuses “on the claim as a whole”).
24
Amazon makes three overlapping arguments for Alice step one. First it says that the
25
Federal Circuit found similar claims and patents were not abstract. Mot. 8:20-10:20. Those cases
26
are addressed throughout this analysis. Second it says that Claim 1 is ineligible because it uses
27
broad functional language and does not explain how to achieve the desired result. Id. 21-12:8.
28
But as explained below, the desired result is real-time video and audio broadcasting that uses less
7
1
expensive and more accessible technology, like internet protocols; the claim and specification
2
appropriately explain how to achieve this. Third, Amazon asserts Claim 1 fails to describe
3
improvement in computer functionality, id. 12:9-14:12, but this is exactly what the claimed
4
invention does: it improves existing computer functionality by teaching new ways of achieving
5
results.
6
United States District Court
Northern District of California
7
A.
The claims are not directed to an abstract idea, nor do they use merely
functional language.
8
The overarching theme of Amazon’s motion is that Claim 1 is directed to a patent-
9
ineligible concept because it is directed to collecting, packaging, and transmitting data. Amazon
10
says these are abstract ideas and that they use purely functional language, instead of language
11
directed to a specific method of achieving a goal.
12
The Federal Circuit has directed courts to “look to whether the claims in the patent focus
13
on a specific means or method, or are instead directed to a result or effect that itself is the abstract
14
idea and merely invokes generic processes and machinery.” Two-Way Media Ltd. v. Comcast
15
Cable Commc’ns, LLC, 874 F.3d 1329, 1337 (Fed. Cir. 2017) (citation omitted). “[A] claim must
16
have the specificity required to transform the claim from one claiming only a result to one
17
claiming a way of achieving it to avoid ineligibility.” Free Stream Media Corp. v. Alphonso Inc.,
18
996 F.3d 1355, 1363 (Fed. Cir. 2021) (cleaned up) (quoting SAP Am., Inc. v. InvestPic, LLC, 898
19
F.3d 1161, 1167-68 (Fed. Cir. 2018)). “[A] claim is ineligible if it fails to recite a practical way of
20
applying an underlying idea and instead is drafted in such a result-oriented way that it amounts to
21
encompassing the principle in the abstract no matter how implemented.” Id. (cleaned up) (quoting
22
Interval Licensing LLC v. AOL, Inc., 896 F.3d 1335, 1343 (Fed. Cir. 2018)).
23
But at the “eligibility phase,” “[a]ll that is required . . . is that the claim itself ‘must identify
24
“how” that functional result is achieved by limiting the claim scope to structures specified at some
25
level of concreteness . . . or to concrete action, in the case of a method claim.’” Id. (quoting Am.
26
Axle & Mfg., Inc. v. Neapco Holdings LLC, 967 F.3d 1285, 1302 (Fed. Cir. 2020)). “[I]t is
27
appropriate to ‘examine the claims in light of the written description’ in performing this analysis.”
28
Stormborn Techs., 444 F. Supp. 3d at 1124 n.2 (first quoting Amdocs (Israel) Ltd. v. Openet
8
United States District Court
Northern District of California
1
Telecom, Inc., 841 F.3d 1288, 1299 (Fed. Cir. 2016); then citing Enfish, 822 F.3d at 1335; and
2
then citing In re TLI Commc’ns LLC Patent Litig., 823 F.3d 607, 611-15 (Fed. Cir. 2016)).
3
As a preliminary note, I am unpersuaded by Amazon’s apparent attempts to isolate
4
individual steps of the claim and argue that each step is abstract, functional, or overbroad. See
5
Mot. 9:6-27; 11:16-26. I am equally unpersuaded by Amazon’s arguments that because the claim
6
language itself does not explain the objectives of the patent—such as reducing the need for
7
expensive hardware—then I cannot consider those objectives when assessing the claim. See Repl.
8
11:10-12:2. Amazon does not cite case law that says courts dissect claims in such a way; indeed,
9
to analyze eligibility, courts look to the claim as a whole as contextualized by the specification.
10
See Enfish, 822 F.3d at 1335; Hawk Tech. Sys., 60 F.4th at 1356; RecogniCorp, 855 F.3d at 1326;
11
Stormborn Techs., 444 F. Supp. 3d at 1124 & n.2.
12
Here, when read as a whole and in the context of the specification, Claim 1 focuses “on a
13
specific means or method” of real-time data broadcasting and is not directed to the abstract idea of
14
data transmission itself. See Two-Way Media, 874 F.3d at 1337. As described by the patent and
15
complaint, real-time data transmission generally involves a data source or transmitting computer, a
16
way of sending data from the source to a server, a server, a way of sending the data from the
17
server to the recipient computer, and a way to read or receive the data by the recipient computer.
18
See ’473 Patent 1:11-47; Figs. 1, 2. The prior art required an “encoder” connected directly to the
19
transmitting computer to send data from the computer to the server, and the encoder and the server
20
itself both had to be “high-cost dedicated” systems and hardware. Id. 1:23-47; see also id. Fig. 1.
21
The ’473 Patent teaches a similar process at a high level, but it specifies that instead of an
22
expensive hardware encoder with a direct link to the transmitting computer, the invention uses a
23
network protocol to send the data wirelessly from the transmitting computer to the server. Id. 2:1-
24
28; see also id. 14:18-29. The server then sends data to the client computer via a network
25
protocol, preferably HTTP. See id. 2:1-28, 14:33-35. In addition to transmitting the data to the
26
server in a different way from the prior art, the specification also teaches that the transmitting
27
computer monitors the data stream and compresses it to align with the available bandwidth on the
28
link between the computer and server. Id. 3:14-23, 9:32-48. The specification teaches a similar
9
1
process for transmitting data from the server to the client computer. Id. 3:5-13; see also id. 4:39-
2
47, 11:9-22. The claim itself teaches that the data stream has “a given data rate” at the
3
transmitting computer and it is divided into slices with “a predetermined size,” id. 14:18-25, and
4
the specification contextualizes that these data rates and sizes are determined based on the
5
available bandwidth of the server and recipient computers, see id. 11:9-22.
United States District Court
Northern District of California
6
Looking at the claim as a whole in light of the specification, the patent teaches and is
7
directed to the use of networks instead of hardware to transmit data, not the transmission of data
8
itself. See Free Stream Media Corp., 996 F.3d at 1363. It is true that the claim “involve[s] a
9
patent-ineligible concept,” Enfish, 822 F.3d at 1335—data transmission, collection, and
10
packaging—but the character of the claim as a whole is “directed to” using internet protocols and
11
data slicing to carry out that objective, id. at 1334 (emphasis added), thereby improving the prior
12
art by making real-time processing possible without the expensive hardware. And, it is limited in
13
scope to the act of transmitting data via this method—it does not purport to encompass all
14
methods of data transmission. See Free Stream Media Corp., 996 F.3d at 1363. This parallels the
15
claim in Stormborn Technologies that I found was not “merely result-oriented” in part because it
16
“explain[ed] how the claimed invention is an improvement from prior art . . . systems and
17
focus[ed] on the elements that provide benefits over prior art.” 444 F. Supp. 3d at 1125 (citing
18
Enfish, 822 F.3d at 1335). Here, the claim recites a practical way of achieving real-time data
19
broadcasting by teaching the use of internet protocols and data slicing in the above-described way.
20
It is sufficiently specific to teach a way of achieving that result, instead of teaching the result
21
itself. See Free Stream Media, 996 F.3d at 1363.
22
23
24
B.
Amazon’s cases demonstrate why the claim is directed to an improvement in
prior art computer functionality, not an abstract idea.
As noted, the Federal Circuit instructs courts to look at what the patent asserts as the
25
claimed advance over prior art. TecSec, 978 F.3d at 1292. Claims related to computer software
26
“satisfy Alice step one when they are ‘directed to a specific implementation of a solution to a
27
problem in the software arts,’ such as an improvement in the functioning of a computer.”
28
RecogniCorp, 855 F.3d at 1326 (quoting Enfish, 822 F.3d at 1338-39); see also Finjan, Inc. v.
10
1
Blue Coat Sys., Inc., 879 F.3d 1299, 1304 (Fed. Cir. 2018) (“[S]oftware-based innovations can
2
make ‘non-abstract improvements to computer technology’ and be deemed patent-eligible subject
3
matter at step 1.” (quoting Enfish, 822 F.3d at 1335-36)). But computer related patents will be
4
found abstract at step one if the focus of the claims is a “process that qualifies as an ‘abstract idea’
5
for which computers are invoked merely as a tool,” including if the claim involves “generalized
6
steps to be performed on a computer using conventional computer activity.” RecogniCorp, 855
7
F.3d at 1326-27 (citations omitted); see also Enfish, 822 F.3d at 1335-36.
8
United States District Court
Northern District of California
9
In Enfish, 822 F.3d at 1330, 1336, the claim taught a detailed way of storing and retrieving
data via a “self-referential” table instead of a more standard “relational” model. “[T]he self-
10
referential table recited in the claims . . . is a specific type of data structure designed to improve
11
the way a computer stores and retrieves data in memory.” Id. at 1339. The claim taught how the
12
self-referential table functioned, including how it self-referred to other parts of the computer’s data
13
table. See id. at 1330-31, 1336. Though the district court concluded that the claims were directed
14
to the abstract idea of storing, organizing, and retrieving memory in a logical table or organizing
15
information using tabular formats, the Federal Circuit reversed, holding that the claims were not
16
“directed to any form of storing tabular data” but rather to the specific storage that used the self-
17
referential table. Id. at 1337. The court noted that this conclusion was “bolstered” by the
18
specification, which taught the benefits of the self-referential table over the standard databases,
19
including flexibility, speed, and decreased memory requirements. Id. The claim therefore was
20
directed to improving computer functionality—using a self-referential database instead of a
21
relational database for storage and organization—not to the abstract concept of storing data, for
22
which the computer would be used in its ordinary capacity. See id. at 1336.
23
This reasoning is directly relevant here. Though Amazon asks me to conclude that BSD’s
24
patent is directed to any form of collecting, packaging, and transmitting data—or any form of real-
25
time broadcasting—the language of the claims confirm that the patent is directed to the specific
26
method of real-time broadcasting that “us[es] an Internet protocol” to transmit data at “a given
27
rate” from one computer to another. ’473 Patent 14:18-35; see also Recognicorp, 855 F.3d at
28
1327 (warning against defining a claim at too “high level of abstraction and untethered from the
11
United States District Court
Northern District of California
1
language of the claims”). Like the patent in Enfish, here too the claim is directed to improving
2
computer functionality—using a network protocol and data matching instead of expensive
3
hardware to transmit the data. And also as in Enfish, this conclusion is “bolstered” by the
4
specification, which teaches the benefits of using network protocols and data slices that can
5
conform to the requirements of the client computer, over the prior art’s use of expensive hardware
6
that requires linking to the server and so cannot be used by most computer users. See ’473 Patent
7
1:23-47. Accordingly, the claim is directed to the use of networks and data slicing to transmit
8
real-time data streams, not to the abstract concept of data transmission for which a computer may
9
be used in its ordinary capacity. Cf. Enfish, 822 F.2d at 1336. And because the claim is directed
10
to improving the computer capabilities in the prior art, rather than “an abstract idea that merely
11
invokes computers as a tool,” Amazon’s citation to Bridge & Post, Inc. v. Verizon
12
Communications, 778 F. App’x 882, 889 (Fed. Cir. 2019) (unpublished) (citation omitted), is not
13
persuasive.
14
That the claim and specification teach this specific method of data transmission, rather than
15
the abstract process of data transmission or packaging, is supported by the claimed advance over
16
prior art. See TecSec, 978 F.3d at 1292. The patent describes the prior art as requiring dedicated
17
hardware for the link between the transmitting computer and the server, as well as for the encoder
18
and servers themselves. See ’473 Patent 1:16-47. That hardware was expensive and also limited
19
access to real-time broadcasting abilities. See id. The ’473 Patent, though, teaches the use of
20
different technology to yield similar results with different means, thereby improving the prior art
21
by negating the need for hardware, decreasing cost, and reaching more computers. Cf. Finjan, 879
22
F.3d at 1304 (holding that the patent was eligible at Alice step one because it made a non-abstract
23
improvement to computer technology by “enabl[ing] more flexible and nuanced” performance of
24
the task). The claim is not directed to the real-time broadcasting itself but rather to the novel way
25
of improving performance of that broadcast.
26
Amazon’s cases do not dictate a different result. First, the disputed patent in Hawk
27
Technology, 60 F.4th at 1352-53, claimed a method for viewing multiple stored video images
28
simultaneously, including receiving, digitizing, displayed, converting, and storing the images;
12
1
providing an access link to the storage; receiving an access request, and transmitting and
2
displaying the video images. The patent allegedly provided solutions for the problem of many
3
users demanding higher quality video content in part by reducing the burden of data transmission.
4
Id. at 1354. The Federal Circuit found the patent ineligible at step one, holding that the claims
5
were directed to “general abstract ideas—displaying images, converting them into a format,
6
transmitting them, and so on.” Id. at 1356-57. It rejected the plaintiff’s argument that the claim
7
was directed to a solution to a technical problem in the existing technology because the claim itself
8
neither disclosed performing that solution nor explained how the goal was achieved. Id. at 1357.
9
Instead, the claim itself merely taught data conversion, which the court found was “an abstract
10
United States District Court
Northern District of California
11
idea.” Id. (citation omitted).
Here, despite its use of similar functional language, Claim 1 does not merely teach an
12
abstract idea: it is directed to a specific method of real-time data broadcasting which solves for
13
problems in the prior art. See RecogniCorp, 855 F.3d at 1326. As explained by the specification,
14
the problem the claim solves is having to use expensive hardware for real-time broadcasting;
15
network protocols like HTTP substitute for the hardware, and those protocols combine with the
16
data slicing and matching to transmit data to recipient computers. Because the claim teaches the
17
use of known internet protocols and data slices and indices to transmit data at different quality
18
levels in real time to client computers, the claim therefore discloses how to perform the solution to
19
the technical problems by providing the method for doing so. In this way, it differs from the claim
20
in Hawk Technology, where the claim itself did not teach a solution to the problem discussed in
21
the specification. Accordingly, this case does not support Amazon’s position.
22
For similar reasons, the analysis in Two-Way Media is not directly on point. There, the
23
disputed patent claimed a method for transmitting packets of data in real time to multiple
24
recipients. Two-Way Media, 874 F.3d at 1333-34. The representative claim recited a method to
25
transmit the packets by converting audio or video streams into multiple streams, routing those
26
streams to users, controlling the routing “in response to selection signals,” and monitoring receipt
27
by users. Id. at 1334-35. The Federal Circuit held that this “result-based functional language”
28
failed to describe how to achieve the results “in a non-abstract way.” Id. at 1337 (citation
13
United States District Court
Northern District of California
1
omitted). It cited to other cases with similar claims directed to abstract ideas. See id. at 1337-38
2
(collecting cases). But again, Two-Way Media differs from the present case because of what the
3
claim was directed to: there, it was to the abstract result of converting and routing data to multiple
4
recipients, but here it is to the specific method of real-time data transmission that uses internet
5
protocols like HTTP as well as data slicing and matching. The ’473 Patent is therefore directed to
6
“a specific implementation of a solution to a problem in the software arts,” RecogniCorp, 855 F.3d
7
at 1326, which, despite the patent’s use of similar functional language, differentiates it from the
8
patent in Two-Way Media. For similar reasons, the claim here differs from those in In re TLI
9
Communications LLC Patent Litigation, which were “directed to the abstract idea of classifying
10
and storing digital images,” rather than solving any “technological problem.” 823 F.3d 607, 613
11
(Fed. Cir. 2016) (citations omitted). These cases are not dispositive here.
12
Amazon also asserts that use of known technology in the claim renders the patent
13
ineligible, but that is not what its citations provide. For example, it cites an unpublished decision
14
where the Federal Circuit held that the claim failed to identify a particular technique for carrying
15
out the claimed objective—data compression—and instead accepted “as a given” that many
16
techniques were available. See Realtime Data LLC v. Array Networks Inc., No. 2021-2251, 2023
17
WL 4924814, at *8 (Fed. Cir. Aug. 2, 2023) (unpublished), cert. denied sub nom. Realtime Data
18
LLC v. Fortinet, Inc., No. 23-498, 2024 WL 72018 (U.S. Jan. 8, 2024). The court did not hold,
19
though, that using one of those known techniques would render the patent ineligible, which is
20
what Amazon seems to imply in its papers. And here, though one of the steps of Claim 1 is
21
similar to data compression because it involves “encoding” data into slices and indices with
22
particular sizes, the claimed objective is not data compression: it is real-time broadcasting using
23
more easily accessible and less expensive technology. As addressed, the claim teaches a technique
24
for that objective. See Free Stream Media Corp., 996 F.3d at 1363. That the claim also teaches
25
data compression as a step involved in broadcasting, without providing extensive detail as to how
26
to compress the data, does not mean the patent teaches only an abstract concept.
27
28
For similar reasons, Amazon’s argument that using “general components” in the claim
does not sufficiently limit the claim scope is also unpersuasive. Its cited case does not stand for
14
1
the proposition that general components cannot limit the claim scope or provide specificity, but
2
rather that the general components did not save that claim, which that was “entirely functional in
3
nature.” Affinity Labs of Tex., LLC v. DIRECTV, LLC, 838 F.3d 1253, 1258 (Fed. Cir. 2016).
4
Indeed the Federal Circuit noted that patent claimed a function of wireless regional
5
communication—which was abstract and overbroad—“not a particular way of performing that
6
function.” Id. Here though, as discussed, Claim 1 is directed to a particular way of performing
7
real-time broadcasting and is not entirely functional. Affinity Labs is not directly applicable.
8
For those reasons, I agree with BSD that its patent is directed to improving computer
United States District Court
Northern District of California
9
functionality rather than at an abstract idea. It is directed to patent-eligible software at Alice step
10
one and the defendant’s motion is DENIED on this basis.
11
II.
ALICE STEP TWO
12
Even if I accept Amazon’s broad characterization of BSD’s claim as directed to the
13
abstract concept of data collecting, packaging, and transmitting, there is an inventive concept that
14
transforms the claim under Alice step two because the patent teaches that the computers and
15
system perform something more than and different from what was previously known in the
16
industry.
17
At step two, I “consider the elements of each claim both individually and ‘as an ordered
18
combination’ to determine whether the additional elements ‘transform the nature of the claim’ into
19
a patent-eligible application.” Enfish, 822 F.3d at 1334 (quoting Alice, 573 U.S. at 217). In doing
20
so, I “search for an inventive concept—i.e., an element or combination of elements that is
21
sufficient to ensure that the patent in practice amounts to significantly more than a patent upon the
22
[ineligible concept] itself.” Alice, 572 U.S. at 217-18 (internal quotation marks and citation
23
omitted). The Federal Circuit has held that the inventive concept in step two must be contained in
24
the claim itself, “as opposed to something purportedly described in the specification.” Two-Way
25
Media, 874 F.3d at 1338 (citation omitted). However, it is appropriate to use the specifications to
26
“inform [the court’s] understanding of the claimed invention and the technological solution,” and
27
“how the elements in the claim functioned together.” Mentone Sols. LLC v. Digi Int’l Inc., No.
28
2021-1202, 2021 WL 5291802, at *5 (Fed. Cir. Nov. 15, 2021) (unpublished) (citing Packet
15
1
Intelligence LLC v. NetScout Sys., Inc., 965 F.3d 1299, 1309-10 (Fed. Cir. 2020)). “Accordingly,
2
the specification cannot save claims directed at an abstract idea but can inform my understanding
3
of whether the claimed invention provides a technological solution or inventive concept that
4
transforms the claim into a patent-eligible application.” Synopsys, 2023 WL 5174291, at *3.
United States District Court
Northern District of California
5
“In computer-implemented inventions, the computer must perform more than ‘well-
6
understood, routine, conventional activities previously known to the industry.’” CosmoKey Sols.
7
GmbH & Co. KG v. Duo Sec. LLC, 15 F.4th 1091, 1097 (Fed. Cir. 2021) (quoting Alice, 573 U.S.
8
at 223). “An inventive concept that transforms the abstract idea into a patent-eligible invention
9
must be significantly more than the abstract idea itself, and cannot simply be an instruction to
10
implement or apply the abstract idea on a computer.” BASCOM Glob. Internet Servs., Inc. v.
11
AT&T Mobility LLC, 827 F.3d 1341, 1349 (Fed. Cir. 2016) (citing Alice, 573 U.S. at 222-23).
12
However, “an inventive concept can be found in the non-conventional and non-generic
13
arrangement of known, conventional pieces.” Id. at 1350.
14
As plausibly alleged and stated in the patent itself, the claim and specifications teach an
15
inventive concept that “amounts to significantly more” than the abstract concept of collecting,
16
packaging, and transmitting data. See Alice, 572 U.S. at 217-18. As discussed, the patent teaches
17
a method of data transmission that allows for real-time broadcasting without dedicated hardware
18
servers. Claim 1 explains that the data is transmitted from one computer to another “over a
19
network” by uploading the data to a server and downloading it over that network. ’473 Patent
20
14:18-32. The complaint plausibly alleges that the previously known method in the industry for
21
doing this required hardware and physical servers. See Compl. ¶¶ 23-24. By teaching the method
22
of transmitting the data without the servers and so implementing a method new and different from
23
what was known in the industry, Claim 1 transforms the abstract idea of data transmission into a
24
patent-eligible invention. See CosmoKey, 15 F.4th at 1097; BASCOM Glob., 827 F.3d at 1349.
25
The inventive concept is therefore the use of network protocols and data slicing and matching
26
where previously only hardware was used; the inventive concept is not the abstract idea itself of
27
data transmission. See Mot. 15:10-11; Repl. 10:8-11:9.
28
Relatedly, I am not persuaded by Amazon’s argument that the patent is not inventive
16
United States District Court
Northern District of California
1
because it only uses known technology. See Mot. 15:3-16:12. The use of known technology—
2
including network and internet protocols—in a novel way to make the data transmission more
3
accessible and less expensive is the objective of the patent. Implementing known or conventional
4
technologies in a “non-conventional and non-generic” way can constitute an inventive concept.
5
BASCOM Glob., 827 F.3d at 1350; see also Diamond v. Diehr, 450 U.S. 175, 188 (1981) (“[A]
6
new combination of steps in a process may be patentable even though all the constituents of the
7
combination were well known and in common use before the combination was made.”). Even
8
assuming all pieces of the claim were known at the time, the combination of the pieces—including
9
the allegedly “contrarian” use of HTTP to convey data from the server to client computer, see
10
Compl. ¶ 24—provides the inventive concept here, as alleged. To the extent that Amazon argues
11
that the pieces and steps of the claims are not inventive because they fall “exactly where those
12
steps would logically occur in a transmission sequence,” Repl. 12:3-14; Mot. 16:6-12, in this case
13
and at this stage, that is a factual issue that I cannot resolve in Amazon’s favor.
14
Amazon also argues that the “contrarian” use of HTTP and the achievement of real-time
15
broadcasting without expensive hardware are not incorporated into the claims and so are not
16
relevant or dispositive. See Mot. 15:13-14; Repl. 11:10-25. But both are incorporated into the
17
specification, and the specifications inform my understanding of the claim and the technological
18
solution. See Mentone Sols., 2021 WL 5291802, at *5; Packet Intelligence, 965 F.3d at 1309-10.
19
The Federal Circuit regularly looks at the claims and specification to assess patent eligibility. For
20
example, in CosmoKey, 15 F.4th at 1098-99, the court reasoned that the claims and the
21
specifications “recite[d] a specific improvement” to the abstract idea, emphasizing that the
22
specification explained “the inventive nature” of the arrangement of steps in the claims, which
23
“provide[d] a technical improvement over conventional . . . methods” of performing the abstract
24
idea. Amazon’s selective citation to half a sentence from Cellspin is not to the contrary. There,
25
the Federal Circuit noted that district courts may look to allegations of inventiveness in a
26
complaint, even if they do not specifically cite the specification, so long as they are not “wholly
27
divorced from the claims or the specification.” Cellspin Soft, Inc. v. Fitbit, Inc., 927 F.3d 1306,
28
1317 (Fed. Cir. 2019) (citing Aatrix Software, Inc. v. Green Shades Software, Inc., 882 F.3d 1121,
17
1
1128 (Fed. Cir. 2018)). The court went on to explain that “[a]s long as what makes the claims
2
inventive is recited by the claims, the specification need not expressly list all the reasons why this
3
claimed structure is unconventional.” Id. Indeed, this case stands for the opposite proposition that
4
Amazon cited it to support, in that it shows that allegations of inventiveness in the complaint,
5
specification, and claim can all inform the decision on this motion.
6
Accordingly, even if the claim is directed to an abstract idea at Alice step one, the inventive
7
concept of using network protocols and data slicing and matching to perform the data transmission
8
sufficiently transforms the claim at Alice step two. The defendant’s motion is DENIED on this
9
basis.
CONCLUSION
United States District Court
Northern District of California
10
11
For those reasons, the motion is DENIED.
12
IT IS SO ORDERED.
13
Dated: January 29, 2024
14
15
William H. Orrick
United States District Judge
16
17
18
19
20
21
22
23
24
25
26
27
28
18
Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.
Why Is My Information Online?