throbber
Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 1 of 26
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`HYUNDAI MOTOR AMERICA,
`
`
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`MAZDA MOTOR OF AMERICA, INC.,
`
`
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`SUBARU OF AMERICA, INC.
`
`
`
`STRATOSAUDIO INC.,
`
`Plaintiff,
`
`
`v.
`VOLVO CARS USA, LLC,
`
`
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`VOLKSWAGEN GROUP OF
`AMERICA, INC.,
`
`
`
`
`
`Plaintiff,
`
`
`Defendant.
`
`DEFENDANTS’ REPLY CLAIM CONSTRUCTION BRIEF
`
`Plaintiff,
`
`
`Defendant.
`
`Plaintiff,
`
`
`Defendant.
`
`Plaintiff,
`
`
`Defendant.
`
`Defendant.
`
`Case No. 6:20-CV-01125-ADA
`
`Case No. 6:20-cv-1126-ADA
`
`Case No. 6:20-cv-1128-ADA
`
`Case No. 6:20-cv-1129-ADA
`
`Case No. 6:20-CV-01131-ADA
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 2 of 26
`
`TABLE OF CONTENTS
`
`Page
`
`I.
`II.
`
`III.
`
`“associated”/“associating”/“association” terms .............................................................. - 1 -
`“associating each . . . ” (’307 claim 11 and ’028 claim 11) ............................................ - 2 -
`A.
`The printed matter doctrine prevents Stratos’s interpretation. ............................ - 3 -
`B.
`Stratos’s Section 101 Analysis is Wrong ............................................................ - 5 -
`’028 Patent, Claim 14 ..................................................................................................... - 5 -
`A.
`Claim 14’s four “operations” are indefinite ........................................................ - 5 -
`B.
`The “accessible by” language renders Claim 14 indefinite ................................ - 7 -
`C.
`Dr. Houh’s declaration should not be stricken.................................................... - 7 -
`“interactive media receiver” (’833 patent claims 1, 3, 5-7, and 9) ................................. - 8 -
`IV.
`“responder identifier” (’833 patent claims 1, 3, 5-7, and 9) ......................................... - 10 -
`V.
`“third party” (’806 claim 5, ’843 claim 10) .................................................................. - 11 -
`VI.
`“third party encoded data”; “encoded third party data” ................................................ - 13 -
`VII.
`VIII. The three “module” terms are indefinite ....................................................................... - 13 -
`A.
`The “module” terms are means-plus-function .................................................. - 13 -
`B.
`The patents do not contain structure corresponding to the functions ............... - 16 -
`“correlating” (’806 claim 5) .......................................................................................... - 17 -
`
`IX.
`
`
`
`
`i
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 3 of 26
`
`
`
`Cases
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`Advanced Ground Inf. Sys., Inc. v. Life360, Inc.,
`830 F.3d 1341 (Fed. Cir. 2016)....................................................................................13, 14, 16
`
`Advanced Ground Inf. Sys. v. Life 360,
`No. 14-80651, 2014 WL 12652322 (S.D. Fl. Nov. 21, 2014) .................................................16
`
`Alice Corp. Pty. Ltd. v. CLS Bank Int’l,
`573 U.S. 208 (2014) ...................................................................................................................5
`
`C R Bard Inc. v. Angiodynamics, Inc.,
`979 F.3d 1372 (Fed. Cir. 2020)..................................................................................................3
`
`Cannon Rubber Ltd. v. The First Years, Inc.,
`2004 WL 2095669 (N.D. Ill. Sept. 17, 2004) ......................................................................2, 14
`
`Digital Retail Apps, Inc. v. H-E-B, LP,
`No. 6-19-CV-00167-ADA, 2020 WL 376664 (W.D. Tex. Jan. 23, 2020) ..........................4, 15
`
`Egenera, Inc. v. Cisco Sys., Inc.,
`972 F.3d 1367 (Fed. Cir. 2019)................................................................................................15
`
`Engel Indus., Inc. v. Lockformer Co.,
`96 F.3d 1398 (Fed. Cir. 1996)....................................................................................................6
`
`Media Rights Techs., Inc. v. Capital One Fin. Corp.,
`800 F.3d 1366 (Fed. Cir. 2015)..................................................................................................2
`
`Microprocessor Enhancement Corp. v. Tex. Instr’s Inc.,
`520 F.3d 1367 (Fed. Cir. 2008)..................................................................................................9
`
`Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co. Ltd.,
`868 F.3d 1013 (Fed. Cir. 2017)................................................................................................15
`
`Noah Sys., Inc. v. Intuit Inc.,
`675 F.3d 1302 (Fed. Cir. 2012)................................................................................................17
`
`Praxair Distr., Inc. v. Mallinckrodt Hosp. Prod. IP Ltd.,
`890 F.3d 1024 (Fed. Cir. 2018)..................................................................................................3
`
`RideApp Inc. v. Lyft, Inc.,
`845 F. App’x 959 (Fed. Cir. 2021) ..........................................................................................16
`
`ii
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 4 of 26
`
`SimpleAir, Inc. v. Sony Ericsson Mobile Communs. AB,
`820 F.3d 419 (Fed. Cir. 2016)....................................................................................................6
`
`Team Worldwide Corp. v. Intex Recreation Corp.,
`__ F. App’x __, 2021 WL 4130634 (Fed. Cir. Sept. 9, 2021) .................................................15
`
`Uniloc USA, Inc. v. Samsung Elecs. Am., Inc.,
`2020 WL 1685557 (Fed. Cir. 2020).........................................................................................16
`
`Visual Memory LLC v. NVIDIA Corp.,
`867 F.3d 1253 (Fed. Cir. 2017)................................................................................................10
`
`Williamson v. Citrix Online, LLC,
`792 F.3d 1339 (Fed. Cir. 2015) (en banc) .........................................................................13, 14
`
`Statutes
`
`35 U.S.C. § 112 ..............................................................................................................................10
`
`iii
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 5 of 26
`
`Stratos’s claim construction arguments (Dkt. 55)1 are unsupported by the evidence,
`
`violate basic tenets of claim construction, and should be rejected. See Dkt. 51.
`
`I.
`
`“ASSOCIATED”/“ASSOCIATING”/“ASSOCIATION” TERMS
`
`Stratos’s brief illustrates why the claims are indefinite. According to Stratos, “the claims
`
`merely require an association (i.e., a connection or relationship) between two things.” Dkt. 55, 6
`
`This allegedly means that the two associated things may be sent together or sent separately
`
`(Compare id., 6 (“may be sent together”) with Claim 15 of the ’028 Patent). “Associating”
`
`allegedly may be active (“to bring two things into relationship with each other”) or passive (“to
`
`describe an existing relationship between two things”). Id., 6. It also allegedly means that two
`
`things may already be associated, but require correlating to create a new association. Id., 33.
`
`Under plain English grammar (which the parties all agree should apply here, so expert testimony
`
`is not required), the terms mean nothing under Stratos’s analysis, because “associating” can have
`
`directly opposite meanings. Neither the intrinsic evidence nor Stratos’s brief give a POSITA any
`
`guidance or limits on what it means to “associate,” be “associated,” or conduct “associating.”
`
`Stratos’s expert, Dr. Mangione-Smith, confirmed these terms have no bounds because
`
`whether things are associated depends on arbitrary “sorts of associations of interest”:
`
`Q. How would I know [two streams that are broadcast separately from each other] are not
`associated?
`A: […] we would have to know what are the associations that are being looked for. And
`they are not associated, if they are not associated under any of the sorts of associations of
`interest. (Ex. B, 119:6-120:1)2
`
`By his example, any Beatles songs could be “associated” with any Taylor Swift song by media
`
`content identifying data elements of the letter “a” in the artist names, or by being released
`
`
`1 Herein, record cites are to Case No. 6:20-CV-01125-ADA, unless otherwise indicated.
`2 Herein, all emphasis is added, and all internal citations/quotations are omitted unless specified.
`
`
`
`- 1 -
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 6 of 26
`
`between 1921-2021, or because they are only “not associated if they are not associated under
`
`any of the sorts of associations of interest.” (id., 119:24–120:1). In fact, Stratos’s expert was
`
`unable to provide any limit for the scope of the “association” terms:
`
`Q. Do you agree that associating means any relationship or act of connecting or joining
`together?
`A. […] that is a good characterization of the plain and ordinary meaning of the term. (Id. at
`108:7-16)
`Q. So if I have one type of data embedded within a data stream, those are associated, right?
`A. [T]hey may not be an association that is useful or interesting to any particular party. But
`there is an association between them, sure. (Id. at 109:10-16)
`Q. Do you agree that associating can also mean to bring two things into a relationship with
`one another?
`A. [...], I would agree. (Id. at 109:17-110-3)
`Q. […][H]ow does a person skilled in the art identify what is not associated?
`A. In general, there is no good clear answer to that. In the context of the claims, one
`applies, one would apply how the term “associated” is used, and determine whether
`or not the claim seems to be practiced. […] (Id. at 116:21-117:5)
`Q. [H]ow does [a POSITA] identify a lack of association or a failure to associate within the
`meaning of this claim?
`A. One would have to look at what the associations are when the claim is practiced. And see
`if those associations are formed by the particular system […]. (Id. at 117:23-118:12)
`
`No claims identify any “relationship of interest,” so there is no practical limitation on
`
`
`
`claim scope. “A claim is indefinite if its language might mean several different things and no
`
`informed . . . choice is available . . . .” Media Rights Techs., Inc. v. Capital One Fin. Corp., 800
`
`F.3d 1366, 1371 (Fed. Cir. 2015). Stratos’s own expert argues that there is no practical
`
`limitation on claim scope, and that the language means different things depending on an
`
`undefined “relationship of interest.” The claims are indefinite.
`
`II.
`
`“ASSOCIATING EACH . . . ” (’307 CLAIM 11 AND ’028 CLAIM 11)
`
`Dr. Mangione-Smith’s testimony affirms Defendants’ positions that (1) the disputed term
`
`gives no notice as to the scope of the term with any certainty; and (2) it requires a step where two
`
`elements must be “associated” that are already “associated.” First, Stratos’s expert disavowed
`
`Stratos’s position that Claim 11 requires a new association. It might be a new association, or it
`
`
`
`- 2 -
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 7 of 26
`
`might not: “My response, as I sit here today, would be no. I think also, it may be forming a new
`
`association. . . . the associating step also covers the case of determining or discovering a previous
`
`or an existing association.” Ex. B, 106:3-106:10. “So it could be an existing association, or it
`
`could be a new association.” Id., 107:15-17. This testimony demonstrates that (1) the disputed
`
`term gives no guidance to Stratos’s expert (or a jury) as to the scope of the term, or (2) the term
`
`allows an impossible step where two elements must to be “associated” that are already
`
`“associated.” Either fact means the term is indefinite.
`
`Second, Stratos’s expert concedes “the associating step also covers the case of
`
`determining or discovering a previous or an existing association” between the media content
`
`identifying data element and at least one of a plurality of media content. Id., 106:6-10. Stratos
`
`thereby stretched the meaning of the term “associating” to cover “determining” or “discovering.”
`
`Stratos’s expert even testified that it could be synonymous with “correlating,” leaving another
`
`disputed term superfluous. Ex. B, 109:20-23. Again, this is indefinite.
`
`A.
`
`The printed matter doctrine prevents Stratos’s interpretation.
`
`“[C]laim limitations directed to the content of information and lacking a requisite
`
`functional relationship” merit no “patentable weight.” Praxair Distr., Inc. v. Mallinckrodt Hosp.
`
`Prod. IP Ltd., 890 F.3d 1024, 1032 (Fed. Cir. 2018). According to Stratos, “media content
`
`identifying data” is data allowing “a user to easily obtain and engage with information associated
`
`with media content.” Dkt. 55, 2. The “media content identifying data” is thus information
`
`communicated to or from a user about which songs to purchase, i.e. “information claimed for its
`
`communicative content.” C R Bard Inc. v. Angiodynamics, Inc., 979 F.3d 1372, 1381 (Fed. Cir.
`
`2020). It is entirely unrelated to the substrate, which would be computer memory or a disk drive.
`
`Stratos argues that “[t]he claim does not recite the value of the identifier ([i.e.] value
`
`12345), nor does it recite the content of the media ([i.e.] “Yellow Submarine” by the Beatles).”
`- 3 -
`
`
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 8 of 26
`
`Dkt. 55, 8. This misapplies the printed matter doctrine. The Court in Digital Retail found that a
`
`“list of goods and services” and a “list of goods and services purchased” are printed matter
`
`because both are “information displayed on some type of electronic device,” and printed matter
`
`is matter claimed for what it communicates. Digital Retail Apps, Inc. v. H-E-B, LP, No. 6-19-
`
`CV-00167-ADA, 2020 WL 376664, at *11 (W.D. Tex. Jan. 23, 2020). Neither term recited any
`
`specific good or service, e.g., “Yellow Submarine” or “milk.”
`
`Stratos’s argument that “there is no ‘displaying’ limitation in the claims” (Dkt. 55, 9), is
`
`irrelevant because the disputed claims in Digital Retail—which fell within the doctrine—did not
`
`have a “displaying” limitation either. Digital Retail, 2020 WL 376664 at *11. And in any event,
`
`the portions of the specification Stratos cites (3:35-38, 6:25-29, 7:39-61, 9:17-20) all indicate
`
`that “media content identifying data” is shown to a user to purchase a song. See also ’028, Claim
`
`11 (requiring that the “media content identifying data” is presented to a user).
`
`Stratos also argues that the content is related to the media substrate, and therefore outside
`
`the doctrine. Dkt. 55, 8-10. But neither Stratos’s brief nor its expert ever identifies the physical
`
`substrate in question or how “media content identifying data” is functionally and structurally
`
`related to it. Stratos’s expert was unable to provide any explanation on this point:
`
`Q. Is the substrate recited in this claim shown in any of the figures of the ’307 or ’028
`patents?
`A. […] I haven’t tried to answer that. I think in the context of the claim, the substrate is likely
`to be at least the system, as claimed with the various components in claim 11. (Ex. B,
`119:17-119:25)
`Q. Can you show me an example of [the substrate] in any of the figures?
`A. Maybe. […] I don’t know that any of the figures say here is a figure that is exemplar of
`claim 11. (Id. at 120:1-120:5)
`
`
`Plaintiff expert’s identification of the alleged substrate (Dkt. 55-31, ¶ 46) should be given
`
`no weight because he concedes (1) he has not performed a thorough analysis (Ex. B, 90:9-91:1),
`
`(2) he does not know how to identify a substrate (id.), and (3) “[it is not] clear to me it has to be
`
`
`
`- 4 -
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 9 of 26
`
`present in the written description.” (id. at 120:17-21). In sum, “media content identifying data”
`
`is not functionally or structurally related to the physical substrate, and has no patentable weight.
`
`B.
`
`Stratos’s Section 101 Analysis is Wrong
`
`Stratos argues that the disputed term cannot be directed to abstract ideas because “the use
`
`of ‘media content identifying data’ improves the functioning of a communications device, such
`
`as a radio receiver.” Dkt. 55, 10. This is not the test under Alice Corp. Pty. Ltd. v. CLS Bank
`
`Int’l, 573 U.S. 208 (2014). Limiting an abstract idea to a particular technological environment
`
`does not pass the § 101 hurdle. The disputed term here merely uses generic computing
`
`technology to apply the basic concepts employed by a person who compiles information that
`
`differentiates between a version of “Blackbird” sung by the Beatles or a cover of the same song
`
`by Sarah McLachlan. This is precisely Stratos’s plain and ordinary meaning of “associating each
`
`media content identifying data element with at least one of a plurality of media content.” It
`
`claims nothing inventive beyond the abstract idea of associating song information with a song.
`
`The concept has long been practiced with paper and pencil by at least record store owners who
`
`associate an album with its unique data for inventory and sales on a ledger, and is abstract.
`
`III.
`
`’028 PATENT, CLAIM 14
`
`A.
`
`Claim 14’s four “operations” are indefinite
`
`Plaintiff argues Claim 14’s “storing” operation refers to Claim 11’s entire “storing” step.
`
`Dkt. 55, 14. Plaintiff’s argument is conclusory. Neither the claims nor the specification clarify
`
`whether the “storing” operation is the entirety of step 11[d], or only a subpart of step 11[d] (such
`
`as only: “storing . . . at a minimum, media content identifying data elements,” or some other
`
`subpart). Plaintiff’s expert argues that Claim 14’s “aggregating” operation is a subpart of step
`
`11[d]: “storing . . . into identifying data aggregates.” Dkt. 55-31, ¶ 56. But Plaintiff already
`
`mapped this language to the “storing” operation, so its interpretation renders the “aggregating”
`
`
`
`- 5 -
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 10 of 26
`
`operation superfluous (deleting it would not change Claim 14’s scope). Plaintiff’s expert failed
`
`to consider this problem. See Ex. B, 210:19–22. Worse, there is no way to know whether the
`
`“aggregating” operation includes only the language Plaintiff proposes, or if it should additionally
`
`include other language, such as: “each identifying aggregate associated with . . . .” Nothing in
`
`the specification resolves this ambiguity. See Ex. B, 211:16–212:9.
`
`Plaintiff’s expert inconsistently argues that every word in Claim 11 is the “correlating”
`
`operation (Ex. B, 214:10–215:2), and that there are multiple “correlating” operations within
`
`Claim 11 (id., 227:20–228:3), such as the “associating” element in the “extracting” step (id.,
`
`215:3–10, 224:8–224:23), and the discussion of “correlating” in the preamble (Dkt. 55-31, ¶ 55).
`
`When asked if the “storing” or “providing” elements of Claim 11 would be “correlating,” the
`
`expert stated he had not “considered it.” Id., 215:11–17, 219:2–18, 221:20–25. There is no way
`
`to determine which alleged act of “correlating” in Claim 11 is the “operation” in Claim 14.
`
`Notably, the entire claim cannot be the “correlating” operation because then the other three
`
`“operations” in Claim 14 are rendered superfluous (they could be deleted without changing
`
`Claim 14’s scope). The specification does not resolve this ambiguity. See Ex. B, 221:12–222:7.
`
`Plaintiff argues the “associating” element in Claim 11 is the “correlating” operation. Dkt.
`
`55, 14; Ex. B, 223:10–226:18. And Plaintiff’s expert opined that “associating” means the same
`
`thing as “correlating.” Ex. B, 222:1–223:9. But Claims 11 and 14 claim both “correlating” and
`
`“associating,” and “[d]ifferent claim terms are presumed to have different meanings.” SimpleAir,
`
`Inc. v. Sony Ericsson Mobile Communs. AB, 820 F.3d 419, 431 (Fed. Cir. 2016) (quotes and cites
`
`omitted); Engel Indus., Inc. v. Lockformer Co., 96 F.3d 1398, 1405 (Fed. Cir. 1996). No
`
`lexicography or disavowal in the specification overcomes this presumption. See generally, ’028;
`
`Ex. B, 231:22–232:17. Further, Claim 11’s “associating” does not match the “correlating” in the
`
`
`
`- 6 -
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 11 of 26
`
`preamble—the preamble refers to correlating a “broadcast segment,” which is not referenced in
`
`the “associating” element. In essence, there is no defining where “correlating” starts and ends.
`
`Plaintiff cites two inapposite cases. Dkt. 55, 14. In both cases, the court turned to the
`
`specification to resolve the ambiguity in a claim term. Here, in contrast, nothing in the
`
`specification resolves the ambiguities, leaving Claim 14 indefinite.
`
`B.
`
`The “accessible by” language renders Claim 14 indefinite
`
`Claim 14 is further indefinite because it requires that its four ambiguous “operations” be
`
`“accessible by” various things such as “a third party database,” which is nonsensical. Dkt. 51,
`
`11–12. To overcome this problem, Plaintiff rewrites the claim. Plaintiff argues that Claim 14
`
`requires “a database system” that allegedly performs the accessing, a description Plaintiff’s
`
`expert agrees with. Dkt. 55, 15; Ex. B, 232:18–233:9. But the claim does not require a
`
`“database system”—it requires a “database” to do the accessing. The ’028 Patent distinguishes
`
`between the two concepts. For example, Claim 12 requires a “database system,” while Claim 14
`
`requires a “database.” And the specification frequently refers to either a “database” or a
`
`“database server” in reference to different concepts. Compare ’028, 5:29–31 (“the purchase
`
`database server 150 provides purchase and download authorization ”) with id., 6:3–4 (“a
`
`database 150 of audio available for purchase”). Thus, the specification clarifies that a database is
`
`simply a set of information, while a database “server” performs acts, such as providing “purchase
`
`and download authorization” for access to media. Id. Plaintiff’s arguments interpret Claim 14 to
`
`require a “database system” or a “database server,” not a “database,” and should be rejected.
`
`C.
`
`Dr. Houh’s declaration should not be stricken
`
`Avoiding the merits, Plaintiff requests Dr. Houh’s declaration be stricken because it
`
`“largely parrots Defendants’ opening brief.” Dkt. 55, 15. To the contrary, Defendants’ brief
`
`cites and relies on Dr. Houh’s expert analysis and input—not the other way around. Dkt. 51, 10–
`
`
`
`- 7 -
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 12 of 26
`
`12. There is nothing wrong with briefs incorporating expert analysis. Plaintiff also argues Dr.
`
`Houh’s testimony is conclusory, which it is not—Plaintiff’s table omits most of Dr. Houh’s
`
`analysis. See Dkt. 51-4, ¶¶ 43–46. Plaintiff argues he did not adequately answer questions at
`
`deposition because he could not provide constructions for terms “such as ‘broadcaster,’” and
`
`“numerous other terms” in Claim 14. Dkt. 55, 16–17. But he testified he had not crafted
`
`constructions for those terms and he could not do so in the middle of a deposition. Dkt. 55-25,
`
`44:14–22 (“It would take time to consider the specification and content and intrinsic evidence to
`
`come up with that . . . .”). Plaintiff’s expert gave the same answers during deposition. Ex. B.,
`
`22:10–21 (“I don’t believe I’ve taken a position regarding its construction. . . . I don’t think it
`
`would be prudent for me to come up with a definition on the spot.”). Further, construing those
`
`terms is unnecessary—even Plaintiff’s expert did not construe any terms for this dispute. See
`
`Dkt. 55-31, ¶¶ 52–60. Plaintiff cites Realtime Data, LLC v. Oracle Am., Inc. in support, which is
`
`inapposite because it involved an expert who would not answer questions such as “did you
`
`interview any focus groups in connection with . . . this report?” 2017 U.S. Dist. LEXIS 187717,
`
`at *22–24 (E.D. Tex. Mar. 22, 2017). The court struck testimony for failure to respond to “basic
`
`questions about his methodology,” not for not having an opinion on how terms should be
`
`construed, or not knowing what they would cover under an unknown construction. Id.
`
`IV.
`
`“INTERACTIVE MEDIA RECEIVER” (’833 PATENT CLAIMS 1, 3, 5-7, AND 9)
`
`Stratos’s arguments regarding the disputed term “interactive media receiver” prove
`
`VCUSA’s point—the term renders the ’833 claims indefinite because it does not define the bounds
`
`of the claims with reasonable certainty. Tellingly, in its arguments, Stratos never states what an
`
`“interactive media receiver” is. Rather, in other sections of its Response, Stratos claims that an
`
`“interactive media receiver” “can be a computer or a car radio” (Dkt. 55, 4), or it can be a “calendar
`
`communication device” (Id., 19). But Stratos also defines an “interactive media receiver” as a
`- 8 -
`
`
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 13 of 26
`
`“receiver that receives interactive media” (Id., 17). In other words, it can be anything that receives
`
`interactive media. Not only is Stratos’s definition circular, but it defines an interactive media
`
`receiver in terms of what it does, not what it is. The use of functional language in a claim may fail
`
`to provide a clear-cut indication of the scope of subject matter embraced by the claim and thus can
`
`be indefinite. See Microprocessor Enhancement Corp. v. Tex. Instr’s Inc., 520 F.3d 1367, 1375
`
`(Fed. Cir. 2008). Stratos’s expert even admitted that he had not considered the limits of what an
`
`“interactive media receiver” could be. Ex. B, 169:10-22.
`
`
`
`Neither Stratos nor its expert have any answer for the fact that the ’833 Patent’s detailed
`
`description uses the term “interactive media receiver” only once and expressly distinguishes it
`
`from a cell phone. ’833, 7:26-27 (“Beginning with the cell phone enabled with an interactive
`
`media receiver … .”). This disclosure is significant because the specification lists examples of
`
`devices other than a cell phone that can be enabled with an “interactive media receiver,” including
`
`a computer and a radio. Id., 7:20-25. Thus, an “interactive media receiver” is not a computer or
`
`a radio as Stratos claims. Even Stratos’s expert conceded that an “interactive media receiver” may
`
`not be a computer or a radio. Ex. B, 160:14-16, 162:5-7. It also is not a “calendar communication
`
`device” because a “calendar communication device” is a cell phone. ’833, 13:56-69.
`
`Stratos obscures the dispute by focusing its arguments on the interactivity of the media or
`
`the receiver. Dkt. No. 55, 17-19. But the indefiniteness of the term “interactive media receiver”
`
`extends far beyond which aspect of the term is interactive—the term as a whole is boundless.
`
`Tellingly, according to the Google Ngram Viewer, the term has never been used outside the ’883
`
`patent in any book before 2019. Ex. D. Stratos’s claim that a POSITA would know how to
`
`implement an interactive media receiver using hardware or software is irrelevant. Dkt. 55, 19
`
`(citing 55-31, ¶64). Not only did Stratos’s expert not know when something is configured to the
`
`
`
`- 9 -
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 14 of 26
`
`point where it would be considered an “interactive media receiver,” (Ex. B, 173:10-174:15) how
`
`an “interactive media receiver” is implemented is an enablement issue, not an indefiniteness issue.
`
`See Visual Memory LLC v. NVIDIA Corp., 867 F.3d 1253, 1261 (Fed. Cir. 2017) (“[W]hether a
`
`patent specification teaches an .... artisan how to implement the claimed invention presents an
`
`enablement issue under 35 U.S.C. § 112 … .”). What is relevant is that a POSITA reading the
`
`claims would not know what an “interactive media receiver” is—hardware, software, or something
`
`else—with reasonable certainty. Dkt. 51-2, ¶¶28, 20-31. Thus, the term is indefinite.
`
`V.
`
`“RESPONDER IDENTIFIER” (’833 PATENT CLAIMS 1, 3, 5-7, AND 9)
`
`Stratos argues that a “responder identifier” is “an identifier that identifies who or what is
`
`sending the [scheduling] request.” Dkt. 55, 20. But the ’833 claims fail to limit who or what the
`
`responder can be. Indeed, Stratos’s expert admits that the responder can be anything and the
`
`identifier can be anything. Dkt. 55-31, ¶66. Additionally, Stratos concedes that the ’833 claims
`
`do not even recite the step of providing a response. Dkt. 55, 20. Rather, Stratos claims that an
`
`interactive media receiver “acts as a ‘responder.’” Id. Even if that is true, the interactive media
`
`receiver acting as a responder does not add any certainty to the ’833 claims because the term
`
`“interactive media receiver” is indefinite.
`
`Stratos’s claim that VCUSA’s expert did not analyze Claim 3 is incorrect. Dr. Medoff
`
`analyzed all of the claims where the term “responder” appears, including Claim 3. See Dkt. 51-
`
`2, ¶¶53-54. Dr. Medoff also testified that his analysis of the other claims applies equally to
`
`claim 3. Ex. C, 30:20-32:7. Specifically, Dr. Medoff opines that the dependent claims, like
`
`Claim 3, recite the information that can be associated the “responder identifier,” not what the
`
`“responder identifier” is. Dkt. 51-2, ¶73. Further, Stratos’s expert could not explain how Claim
`
`3 describes what a “responder identifier” is as opposed to what it does and had not considered
`
`the limits of what a “responder identifier” could be. Ex. B, 193:6-17; 190:18-20. Not
`- 10 -
`
`
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 15 of 26
`
`surprisingly, the Google Ngram Viewer finds zero usage of “responder identifier.” Ex. E.
`
`“[R]esponder identifier” thus renders the scope of the ’833 claims indefinite.
`
`VI.
`
`“THIRD PARTY” (’806 CLAIM 5, ’843 CLAIM 10)
`
`Stratos argues that in the asserted claims, the term “third party” means “a person or group
`
`besides the two primarily involved in a situation.” Dkt. 55, 21. But immediately thereafter,
`
`Stratos argues that the first two parties are a “broadcast source” and a “broadcast receiver,” id.,
`
`instantly making it unclear whether Stratos is actually referring to a person or instead referring to
`
`a piece of equipment. Then, Stratos explains that the broadcast source could be a radio station
`
`and the broadcast receiver could be a radio receiver. Id. The radio receiver is clearly equipment,
`
`and the patents define “broadcaster” as “devices that transmit broadcast streams” (’806, 4:53), so
`
`perhaps a third party is a piece of equipment other than the transmitter or receiver. But Stratos
`
`also argues that a “record company” could be a third party. Dkt. 55, 22.
`
`Stratos’s expert only makes things more confusing. In his declaration, he refers to “an
`
`entity receiving data” as the receiver, and “an entity transmitting data” as the data source, thus
`
`putting himself into the “person or group” camp. Dkt. 51-1, ¶ 71. He goes on to refer to “a
`
`[radio] station” as a third party, without explaining whether the third party is the radio station
`
`equipment, or the individual or corporation that owns the equipment, or the individuals working
`
`at the radio station. Id., ¶ 72. He fails to explain whether two radio stations owned by the same
`
`corporation are two third parties, or one entity. (He also doesn’t know whether the “third party”
`
`in the specification is the same “third party” in the claims. Ex. B, 57:10–22.)
`
`Stratos’s expert was no clearer at deposition. He identified “components,” a radio
`
`“station,” “the literal antenna that’s 15 miles away from here,” “a particular individual,” “the
`
`physical hardware,” and a “corporate entity” all as examples of one party, that is, a broadcaster.
`
`Ex. B, 59:23–61:19. He similarly described both “the physical receiving device” and the person
`- 11 -
`
`
`
`

`

`Case 6:20-cv-01131-ADA Document 57 Filed 09/20/21 Page 16 of 26
`
`operating the device as “receivers.” Id., 63:3–63:23. He explained that in his declaration, he
`
`was referring to pieces of equipment (id., 61:20–62:7), but he then reverted to an “entity”
`
`definition: “You know if it’s third party data if you know it originates from a third party, which
`
`is to say an entity other than … the broadcaster of the strea

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket