`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`MAZDA MOTORS OF AMERICA, INC.,
`
`
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`SUBARU OF AMERICA, INC.
`
`
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`VOLVO CARS USA, LLC,
`
`
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`VOLKSWAGEN GROUP OF
`AMERICA, INC.,
`
`
`Defendant.
`
`
`
`
`
`)
`) Case No. 6:20-CV-01125-ADA
`)
`) JURY TRIAL DEMANDED
`)
`)
`)
`)
`)
`)
`) Case No. 6:20-cv-1126-ADA
`)
`) JURY TRIAL DEMANDED
`)
`)
`)
`)
`)
`)
`) Case No. 6:20-cv-1128-ADA
`)
`) JURY TRIAL DEMANDED
`)
`
`)
`)
`)
`)
`)
`) Case No. 6:20-cv-1129-ADA
`)
`) JURY TRIAL DEMANDED
`)
`
`)
`)
`)
`)
`)
`) Case No. 6:20-CV-01131-ADA
`)
`) JURY TRIAL DEMANDED
`)
`)
`)
`)
`)
`)
`
`
`
`
`
`
`
`
`
`Plaintiff,
`
`STRATOSAUDIO INC.,
`
`
`v.
`
`HYUNDAI MOTOR AMERICA,
`
`
`Defendant.
`
`Plaintiff,
`
`Defendant.
`
`Plaintiff,
`
`Defendant.
`
`Plaintiff,
`
`Defendant.
`
`Plaintiff,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 2 of 23
`
`PLAINTIFF’S SUR-REPLY CLAIM CONSTRUCTION BRIEF
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 3 of 23
`
`TABLE OF CONTENTS
`
`Page
`
`C.
`
`DISPUTED CLAIM TERMS .......................................................................................... 1
`A.
`Associated/Associating/Association (All Claims) .................................................. 1
`B.
`“Associating each media content identifying data element with at least one of
`a plurality of media content” (’307 Patent, Claim 11; ’028 Patent, Claim 11)....... 3
`1.
`The Challenged Limitation is Not Indefinite .............................................. 3
`2.
`The Printed Matter Doctrine Does Not Apply ............................................ 4
`3.
`Defendants Did Not Conduct a Section 101 Analysis ................................ 6
`Claim 14 of the ’028 Patent .................................................................................... 6
`The “storing,” “correlating” and “aggregating” limitations are not
`1.
`indefinite ..................................................................................................... 6
`“Accessible by” is not indefinite ................................................................. 7
`2.
`“Interactive Media Receiver” (’833 Patent, all claims) .......................................... 8
`“Responder Identifier” (’833 Patent, all claims) ..................................................... 9
`“Third Party Encoded Data” (’806 Patent claim 5) / “Encoded Third Party
`Data” (’843 Patent claim 10) ................................................................................ 10
`“stream scanner module” (’806 Patent, Claims 5 & 6) ......................................... 12
`1.
`The claim itself connotes sufficient structure ........................................... 12
`2.
`The specification also discloses sufficient structure ................................. 13
`“stream analysis module” (’806 Patent, Claim 5) ................................................. 14
`Correlating (’806 Patent, Claim 5)........................................................................ 15
`“Broadcast Scanning Module” (’843 Patent, Claim 10) ....................................... 16
`
`D.
`E.
`F.
`
`G.
`
`H.
`I.
`J.
`
`(i)
`
`
`
`
`
`
`
`I.
`
`
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 4 of 23
`
`
`
`TABLE OF AUTHORITIES
`
`FEDERAL CASES
`
` Page(s)
`
`3M Innovative Props. Co. v. Tredegar Corp.,
`725 F.3d 1315 (Fed. Cir. 2013)..................................................................................................9
`
`3rd Eye Surveillance, LLC v. City of Forth Worth,
`No. 6:14-cv-00725-JDL, Docket No. 120 (E.D. Tex. June 8, 2016) .........................................2
`
`Alfred E. Mann Found. for Sci. Research v. Cochlear Corp.,
`841 F.3d 1334 (Fed. Cir. 2016)................................................................................................14
`
`Apex Inc. v. Raritan Computer, Inc.,
`325 F.3d 1364 (Fed. Cir. 2003)................................................................................................12
`
`Bancorp Servs., L.L.C. v. Hartford Life Ins. Co.,
`359 F.3d 1367 (Fed. Cir. 2004)..................................................................................................4
`
`BASF Corp. v. Johnson Matthey Inc.,
`875 F.3d 1360 (Fed. Cir. 2017)............................................................................................1, 10
`
`Berkheimer v. HP Inc.,
`881 F.3d 1360 (Fed. Cir. 2018)..................................................................................................6
`
`Biosig Instruments, Inc. v. Nautilus, Inc.,
`783 F.3d 1374 (Fed. Cir. 2015)..................................................................................................7
`
`Ericsson, Inc. v. D-Link Sys.,
`773 F.3d 1201 (Fed. Cir. 2014)................................................................................................15
`
`Estech Sys. v. Burnco Tex. LLC,
`2021 U.S. Dist. LEXIS 114668 (E.D. Tex. June 18, 2021) .....................................................13
`
`Intelligent Automation Design, LLC v. Zimmer Biomet CMF,
`799 Fed. Appx. 847 (Fed. Cir. 2020) .......................................................................................13
`
`Microprocessor Enhancement Corp. v. Tex. Instr’s Inc.,
`520 F.3d 1367 (Fed. Cir. 2008)..................................................................................................8
`
`Noah Sys. Inc. v. Intuit Inc.,
`675 F.3d 1302 (Fed. Cir. 2012)................................................................................................14
`
`Power Integrations, Inc. v. Fairchild Semiconductor Int'l, Inc.,
`711 F.3d 1348 (Fed. Cir. 2013)..........................................................................................12, 14
`
`
`
`
`
`(ii)
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 5 of 23
`
`
`
`Skky, Inc. v. MindGeek s.a.r.l.,
`859 F.3d 1014 (Fed. Cir. 2017)................................................................................................13
`
`USB Bridge Sols., LLC v. Buffalo Inc.,
`2020 U.S. Dist. LEXIS 67678 (W.D. Tex. Apr. 17, 2020) ........................................................8
`
`Williamson v. Citrix Online, LLC,
`792 F.3d 1339 (Fed. Cir. 2015) (en banc)..........................................................................12, 13
`
`FEDERAL STATUTES
`
`35 U.S.C. § 101 ................................................................................................................................6
`
`
`
`
`
`
`
`(iii)
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 6 of 23
`
`
`
`I.
`
`DISPUTED CLAIM TERMS
`
`A.
`
`“Associated”/“Associating”/“Association” (All Claims)
`
`Defendants give no credible explanation for why the plain English words “associated,”
`
`“associating,” and “association” are indefinite.
`
`First, Defendants incorrectly claim that the plain and ordinary meaning of each word has
`
`two “directly opposite meanings.” [D.I. 611 (“Reply”) at 1.] This is false—each word has a
`
`clear meaning. As StratosAudio’s expert explained, the term “associating” refers to “the act of
`
`connecting or joining together.” [D.I. 55-31 (“W.M.S. Decl.”) ¶ 39.] An “association” is a
`
`relationship “created by” the act of “associating.” [Id.] Similarly, after performing the step of
`
`“associating,” two things become “associated.” [See ’307 Patent, claim 11 (“associating each
`
`media content identifying data element with at least one of a plurality of media content;” “each
`
`identifying data aggregate associated with at least one of the plurality of media content.”
`
`(emphasis added)).] That these related words can be used with different tenses or as different
`
`parts of speech (e.g., as a verb, an adjective, or a noun) does not make them indefinite—it simply
`
`tracks their plain English usage. [See D.I. 55-24 (listing definitions).]
`
`It is certainly true, as Defendants note, that two things can be “associated” in many
`
`different ways. For example, sending two data streams together may associate them. Sending
`
`them separately, with an identifier attached to both, may also associate them. That does not
`
`mean “associate” has two “directly opposite meanings,” it just shows how many ways two things
`
`can be “associated.” Yet as the Federal Circuit has repeatedly held, “breadth is not
`
`indefiniteness.” See BASF Corp. v. Johnson Matthey Inc., 875 F.3d 1360, 1367 (Fed. Cir. 2017).
`
`
`1 Docket citations are to Case No. 20-cv-1125.
`
`
`
`
`1
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 7 of 23
`
`
`
`In every instance where these terms are used, a POSITA would understand the scope of
`
`the association with reasonable certainty. For example, claim 11 of the ’307 patent discloses that
`
`a computer processor performs the step of “associating” a “media content identifying data
`
`element” with “at least one of a plurality of media content.” [’307 Patent, claim 11.] To perform
`
`this limitation, the processor must make a connection or relationship between the identifier and
`
`the media. The nature of that relationship (i.e., the “association of interest”) is thus made clear in
`
`the claim itself. It is irrelevant whether the identifier and the media were previously associated
`
`in some manner by someone or something else. The claim requires the processor to make an
`
`association. So long as it does, the claim is satisfied.
`
`Finally, Defendants rely on irrelevant excerpts from the testimony of Dr. Mangione-
`
`Smith where he was asked various questions about how to determine if two things are not
`
`associated. That question is impossible to answer in the abstract because there are many ways
`
`two things could be associated, but as Dr. Mangione-Smith went on to state, in the context of the
`
`claims the determination is straightforward. [See D.I. 61-2 at 116:25-117:5.] For example, the
`
`claims describe associating a song with its identifier. [’028 Patent, Claim 11.] There is nothing
`
`unclear about that, and a jury can easily analyze a system and its source code to determine if
`
`such an association is made or not.
`
`The case of 3rd Eye Surveillance, LLC v. City of Forth Worth, Case No. 6:14-cv-00725-
`
`JDL, Docket No. 120 (E.D. Tex. June 8, 2016) (attached hereto as Exhibit 29), is directly on
`
`point. There, the defendant argued the phrase “associated with” was indefinite because “the
`
`patent does not specify how the elements it has identified are associated.” Id. at 6. The court
`
`disagreed, noting that “nothing in the patent requires that the term ‘associated with’ specify how
`
`
`
`
`
`2
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 8 of 23
`
`
`
`elements are associated.” Id. at 7. The district court found the term not indefinite and declined
`
`to construe it. Id. This Court should do the same here.
`
`B.
`
` “Associating each media content identifying data element with at least one of
`a plurality of media content” (’307 Patent, Claim 11; ’028 Patent, Claim 11)
`
`1.
`
`The Challenged Limitation is Not Indefinite
`
`Defendants argue (in their Reply at 2) that StratosAudio’s expert “disavowed Stratos’s
`
`position that Claim 11 requires a new association.” This mischaracterizes the record.
`
`StratosAudio argued claim 11 of the ’307 and ’028 Patents describes creating an association that
`
`is new to the receiver. In other words, the receiver obtains a broadcast stream and a data stream.
`
`[’028 Patent, Claim 11.] The data stream is “associated” with the broadcast stream, but the claim
`
`does not say the receiver created this association. Next, the receiver extracts data from the data
`
`stream, then it performs an “associating” step—creating an association between a media content
`
`identifying data element in the data stream and an item of media content in the broadcast stream.
`
`[Id.] This new associating step must be performed by the receiver whether or not the broadcast
`
`and data streams are associated. As StratosAudio’s expert explained in his deposition, to satisfy
`
`this limitation the receiver could create some never-previously-recognized association between
`
`the song and its identifier, but more likely it is discovering an existing association—i.e., it is
`
`connecting the identifier with the song it identifies. [D.I. 61-2 at 106:11-107:17.] To satisfy this
`
`limitation, the receiver must take some step or have some logic that makes this connection. If
`
`the receiver does nothing, and simply passes the broadcast and data stream without extracting or
`
`associating anything, it has not performed the claim as written. Because there is nothing unclear
`
`or ambiguous about having the receiver associate two things, the limitation is not indefinite.
`
`Defendants also argue (in their Reply at 3) that StratosAudio “stretched the meaning of
`
`the term ‘associating’ to cover ‘determining’ or ‘discovering.’ StratosAudio’s expert even
`
`
`
`
`
`3
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 9 of 23
`
`
`
`testified that it could be synonymous with ‘correlating.’” StratosAudio did not “stretch”
`
`anything. Defendants acknowledged in their opening brief that the plain meaning of
`
`“associating” is “any relationship or act of connecting or joining together.” [D.I. 51 at 4
`
`(emphasis added).] “Any relationship” covers new or existing relationships. For example, one
`
`could “associate” two socks by reuniting them after a trip through the laundry. This would cover
`
`associating two things that already had some pre-existing relationship. Alternatively, one could
`
`form a new association, as the U.S. states did when they signed the Constitution. Both are acts
`
`of “associating.” Defendants also previously acknowledged “correlating” means “[t]o put or
`
`bring into causal, complementary, parallel, or reciprocal relation.” [Id. at 32.] If two things are
`
`“connected” or “joined together” they are both associated and correlated. Despite Defendants’
`
`suggestions to the contrary, there is nothing per se indefinite about using different words with
`
`similar or even identical meanings. See, e.g., Bancorp Servs., L.L.C. v. Hartford Life Ins. Co.,
`
`359 F.3d 1367, 1372-74 (Fed. Cir. 2004) (finding “surrender value protected investment credits”
`
`means the same thing as “stable value protected investment credits” and is not indefinite).
`
`2.
`
`The Printed Matter Doctrine Does Not Apply
`
`Defendants argue (at 3) that “media content identifying data” is “information claimed for
`
`its communicative content.” This is clearly wrong. Indeed, none of the citations Defendants
`
`give actually refers to displaying the media content identifying data. Instead, all of Defendants’
`
`citations describe sending the media content identifying data to an external device, such as a
`
`flash drive, to facilitate a purchase. [See Reply at 3 (citing the ‘028 Patent at 3:35-38, 6:25-29,
`
`7:39-61, 9:17-20).] Indeed, as StratosAudio noted in its responsive brief, it would make little
`
`sense to show the user a unique identifier since it could be, for example, a string of alphanumeric
`
`characters that uniquely identifies a particular broadcast. [See ’028 Patent at 6:1-2, 6:19-22 &
`
`Claim 16.] The user would not know what to make of this information. Defendants also argue
`
`
`
`
`4
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 10 of 23
`
`
`
`(at 4) that claim 11 requires presenting media content identifying data “to a user,” but as
`
`StratosAudio noted in its responsive brief, “presentation” in the claims is not so limited and
`
`could include (for example) sending the data to an external device. The word “user” does not
`
`appear in the claims. Defendants do not address any of these points in their reply.
`
`Even if a system did choose to display the “media content identifying data” to a user, that
`
`is not its only purpose. The “media content identifying data” is associated with a specific item of
`
`media content, allowing the system (not the user) to uniquely identify that content. [See id. at
`
`5:64-6:2 & Claim 16.] The media content identifying data is stored in an aggregate and can be
`
`sent to an external device such as a server. [Id., Claims 11 & 17.] Indeed, if the “media content
`
`identifying data” were only information displayed to a user, that would eliminate the entire point
`
`of StratosAudio’s patents. The patents note that prior art radios could display information about
`
`a song, but “the user must write down or remember the identifying information and then go to a
`
`store or online retailer to purchase the media.” [’028 Patent at 2:35-49.] This was
`
`disadvantageous because “the information provided by the radio station may not be enough to
`
`sufficiently identify the song.” [Id.] For example, the user may have the song title but not “other
`
`necessary identifying information,” such as information about when or where the song was
`
`played. [Id.] The patents solve this problem by creating a system that allows unique
`
`identification of broadcast segments at the time they are broadcast. The “media content
`
`identifying data” is what enables this unique identification.
`
`Because the “media content identifying data” is not just data for display, any disputes
`
`about what constitutes the “substrate” are irrelevant. In other words, the “media content
`
`identifying data” performs its function (identifying a media segment) regardless of whether the
`
`“substrate” is the processor, memory, disk drive, flash drive, or something else. Because the
`
`
`
`
`
`5
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 11 of 23
`
`
`
`“media content identifying data” improves the functioning of the system, the printed matter
`
`doctrine does not apply to it.
`
`3.
`
`Defendants Did Not Conduct a Section 101 Analysis
`
`Defendants’ opening brief mistakenly assumed that, if the printed matter doctrine
`
`applied, claim 11 must be invalid under 35 U.S.C. § 101. That is not accurate. As Defendants
`
`now concede (at 3), if the printed matter doctrine applies, the result is that the limitation is
`
`entitled to no patentable weight. Even in that circumstance, however, the Court would need to
`
`analyze whether what remains is valid under Section 101. Here, Defendants did not even
`
`perform that analysis. While Defendants criticize StratosAudio’s arguments, it is Defendants’
`
`burden to prove invalidity under Section 101, not StratosAudio’s burden to disprove it. See
`
`Berkheimer v. HP Inc., 881 F.3d 1360, 1368 (Fed. Cir. 2018). Because Defendants did not even
`
`attempt to meet their burden, the claim is not invalid even if the Court applies the printed matter
`
`doctrine.
`
`C.
`
`Claim 14 of the ’028 Patent
`
`1.
`
`The “storing,” “correlating” and “aggregating” limitations are not
`indefinite
`
`Defendants argue (at 5) that it is unclear whether the “storing” limitation in claim 14
`
`refers to the entire “storing” step in claim 11, or only a subpart thereof. The intrinsic evidence
`
`shows that it refers to the entire limitation. First, the “storing” limitation is discrete and self-
`
`contained. [See ’028 Patent, Claim 11.] Second, claim 14 also refers to the “aggregating”
`
`operation, which is a sub-part of the “storing” limitation. [Id., Claim 14.] Clearly, when the
`
`inventors wanted to refer to only a portion of the “storing” limitation, they knew how to do so.
`
`Defendants next argue (at 5-6) that the word “aggregating” in claim 14 is “superfluous”
`
`because it is duplicative of the phrase “storing.” This is clearly wrong. Claim 14 requires either
`
`
`
`
`
`6
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 12 of 23
`
`
`
`the entire “storing” limitation, or just the “aggregation” sub-portion of the “storing” limitation, to
`
`be accessible to various other systems. The two words (“storing” and “aggregating”) refer to two
`
`different things—either the entire limitation (“storing”) or a portion of it (“aggregating”), so they
`
`are not “superfluous” or redundant. Nor is it superfluous, unclear or indefinite to say, as claim
`
`14 does, that either an entire step or only a portion of it is accessible to something else.
`
`Defendants next argue (at 6) that “correlating” and “associating” in claims 11 and 14
`
`cannot have the same meaning because “no lexicography or disavowal in the specification
`
`overcomes [the] presumption” that the two words mean different things. As discussed above, no
`
`lexicography or disavowal is necessary here because the plain meanings of these two terms are,
`
`for purposes of these patents, identical. In other words, if one were to “associate[e] each media
`
`content identifying data element with at least one of a plurality of media content” one would also
`
`necessarily “correlat[e] media content identifying data with at least one broadcast segment
`
`received by a communication device.” There is nothing unclear or indefinite about the word
`
`“correlating” in claim 14 referring to both the preamble and body of claim 11, especially since
`
`claim 14 refers to “at least one of the … correlating operations.”
`
`Claims do not require mathematical precision, only reasonable certainty. See Biosig
`
`Instruments, Inc. v. Nautilus, Inc., 783 F.3d 1374, 1381 (Fed. Cir. 2015). Here, it is reasonably
`
`clear which operations claim 14 refers to, so the claim is not indefinite.
`
`2.
`
`“Accessible by” is not indefinite
`
`Defendants argue a database cannot access anything, but they do not explain why.
`
`Defendants appear to acknowledge (at 7) that databases reside on database management systems,
`
`and that database management systems can access other systems. A person of ordinary skill
`
`would not need to redefine the word “database” to understand a database operates in an
`
`environment that allows it to access to other systems and operations. [See D.I. 55-25 at 30:8-
`
`
`
`
`7
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 13 of 23
`
`
`
`31:7; D.I. 55-31 ¶¶ 58-59 .] Regardless, even if Defendants are correct, that does not make the
`
`claim indefinite. The words “database” and “accessible by” are clear. At most, Defendants raise
`
`an enablement question—whether it is possible to create a system where a database can access
`
`the claimed operations. That is not a dispute the Court should resolve on claim construction.
`
`See USB Bridge Sols., LLC v. Buffalo Inc., 2020 U.S. Dist. LEXIS 67678 at *14 (W.D. Tex. Apr.
`
`17, 2020).
`
`D.
`
` “Interactive Media Receiver” (’833 Patent, all claims)
`
`Defendants argue incorrectly (at 8-9) that this term is indefinite because StratosAudio
`
`“never states what an ‘interactive media receiver’ is” and does not identify all possible examples
`
`of the term. As to the latter point, there is no requirement that a patent specification disclose all
`
`possible preferred embodiments. See Manual of Patent Examining Procedure § 2164.02
`
`(“because only an enabling disclosure is required, applicant need not describe all actual
`
`embodiments”). As to the former point, the specification identifies multiple examples of an
`
`interactive media receiver, such as a computer or car radio, and contrasts them with receivers of
`
`“non-interactive media.” [See ’833 Patent at 7:16-25, 7:36-41, 19:30-33.] Accordingly, the term
`
`is not purely functional, as Defendants allege, and the specification provides specific
`
`embodiments. Even if the language were functional, that does not render the claim indefinite, as
`
`Defendants’ own cited case held: “apparatus claims are not necessarily indefinite for using
`
`functional language.” See Microprocessor Enhancement Corp. v. Tex. Instr’s Inc., 520 F.3d
`
`1367, 1375 (Fed. Cir. 2008) (holding claims not indefinite).
`
` Defendants contend (at 9) that an interactive media receiver cannot be a cell phone,
`
`computer, or radio, but the specification does not say that. Rather, the cited portions of the
`
`patent identify “examples of other devices which can support integrated interactive broadcast
`
`media” as including “computers (including laptops), electronic personal digital assistants,
`
`
`
`
`8
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 14 of 23
`
`
`
`automotive entertainment systems, digital video recorders, digital audio devices, digital media
`
`devices, GPS devices, radios, televisions, and/or the like.” [’833 Patent at 7:20-25.] Each of
`
`these are embodiments that could serve as an interactive media receiver. Nor does the cited
`
`testimony from StratosAudio’s expert state that the term excludes a computer or radio. [Cf.
`
`Reply at 9 (citing D.I. 61-2 at 160:14-16, 162:5-7).] Indeed, Dr. Mangione-Smith said just the
`
`opposite: that radios can be interactive media receivers. [See Id. at 187:20-188:13.]
`
` Finally, Defendants’ reliance on Google Ngram Viewer results are irrelevant. At most
`
`Defendants are suggesting this is a coined term, but that does not make it indefinite. See 3M
`
`Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1321 (Fed. Cir. 2013) (“Idiosyncratic
`
`language, highly technical terms, or terms coined by the inventor are best understood by
`
`reference to the specification.”). That is especially true where, as here, the specification gives
`
`specific examples of what the claimed “interactive media receiver” can be, and where both the
`
`terms “interactive media” and “receiver” had well-known meaning to a POSITA. [See D.I. 51-6,
`
`¶¶ 10-12.]
`
`E.
`
`“Responder Identifier” (’833 Patent, all claims)
`
`Defendants’ latest indefiniteness arguments for the “responder identifier” term fare no
`
`better than their prior arguments. First, Defendants insist (at 10) that “responder identifier” is
`
`indefinite because the claims “fail to limit who or what the responder can be.” This argument is
`
`baseless—there is no reason why the ’833 patent must limit the isolated term “responder.”
`
`Claim 1 already places various limitations on the responder identifier, reciting (for example) that
`
`it is associated with database entries that allow the system to schedule an event. [’833 Patent,
`
`Claim 1.] Dependent claims further characterize the responder identifier: claim 3 states it can
`
`identify a user or an interactive media receiver, while claims 6 and 7 state that the responder
`
`identifier can be associated with “demographics,” “preferences,” a “calendar,” a “location,” or a
`
`
`
`
`9
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 15 of 23
`
`
`
`“schedule.” [Id., Claims 3, 6, & 7.] A POSITA would understand what the responder identifier
`
`is: information. Specifically, it is information that identifies a user or a device, and that is used
`
`to facilitate scheduling. There is no reason why the claims must incorporate additional
`
`limitations to explain this term.
`
` Next, Defendants’ arguments (at 20-21) about competing expert opinions are misplaced
`
`because Defendants concede Dr. Medoff addressed only “responder” by itself, and not claim 3.
`
`Dr. Medoff opined that there are many types of potential “responses” in the ’833 patent (see D.I.
`
`51-6, ¶ 57), but “breadth is not indefiniteness.” BASF, 875 F.3d at 1367. As Dr. Mangione-
`
`Smith explained, the availability of many types of responses or responders does not make the
`
`term indefinite to a POSITA. [See WMS Decl., ¶¶ 66-67.] By way of analogy, when a claim
`
`recites a “user” one of skill understands that covers any user. The phrase “user identifier” would
`
`not be indefinite simply because a claim did not give the identity of a specific user.
`
`Finally, for the same reasons discussed above, Defendants’ reliance on Google Ngram
`
`Viewer results is irrelevant. At most, Defendants are suggesting Plaintiff coined this phrase, but
`
`that does not make it indefinite. One of skill would have known what a “responder” was in the
`
`context of the ’833 Patent, which recites sending a response to a scheduling request, and one of
`
`skill also would have understood how to identify a user or system. The words “responder” and
`
`“identifier” are not indefinite whether considered individually or in combination.
`
`F.
`
`“Third Party Encoded Data” (’806 Patent claim 5) /
`“Encoded Third Party Data” (’843 Patent claim 10)
`
`For the “third party” phrases, Defendants attempt to manufacture ambiguity where there
`
`is none. The dictionary definitions for “third party” make clear this phrase refers to a “person or
`
`group besides the two primarily involved in a situation.” [D.I. 55-27 (emphasis added).] It
`
`cannot refer to equipment because equipment is not a “party.” In the context of the ’806 and
`
`
`
`
`
`10
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 16 of 23
`
`
`
`’843 Patents, there will be (1) a broadcaster operating broadcasting equipment, (2) a receiver
`
`operating receiving equipment, and (3) a third party that provides data (in the ’843 Patent) or
`
`encoded data (in the ’806 Patent). The claims require that the data/encoded data come from the
`
`third party, not that the third party operates any particular piece of equipment.
`
`Defendants complain (at 12) that there may be a “gray area” surrounding whether a party
`
`is a “third-party.” Any ambiguity, however, is not caused by the definition of “third party”—that
`
`phrase unambiguously requires a separate person or entity. Of course the facts surrounding
`
`whether one party is related to another can be complex and case-specific. For example, if a
`
`record company owns a broadcaster, a fact-finder may conclude the record company is not a
`
`third-party. Whether two parties are related may require analyzing their corporate structure, or
`
`their contractual relationships. That does not make the phrase “third party” unclear. It simply
`
`means the fact-finder may need to analyze facts to resolve any disputes.
`
`This is also why Defendants’ cited testimony from StratosAudio’s expert witness is
`
`irrelevant. Defendants gave the expert various hypothetical scenarios. Some hypotheticals were
`
`clear, and the expert was able to say whether Defendants’ fact pattern described a third party.
`
`[See D.I. 61-2 at 65:8-67:17.] Other hypotheticals were unclear, so the expert was not able to
`
`form an opinion without more information. [See Id. at 77:10-78:6.] This questioning shows why
`
`infringement and anticipation are questions of fact, and why courts employ burdens of proof. It
`
`has nothing to do with whether the phrase “third party” has a plain and ordinary meaning, which
`
`it clearly does.
`
`Finally, Defendants suggest (at 13) that there is no difference between the phrases
`
`“encoded third-party data” and “third-party encoded data.” This is wrong, and it shows why the
`
`Court must construe these two different phrases. “Third-party encoded data” requires a third
`
`
`
`
`
`11
`
`
`
`
`
`
`
`Case 6:20-cv-01131-ADA Document 61 Filed 09/24/21 Page 17 of 23
`
`
`
`party to encode the data. “Encoded third party data” does not require the third-party to encode
`
`the data. In both instances, the data must come from a third party. StratosAudio’s constructions
`
`make these points clear, and the Court should adopt them.
`
`G.
`
` “Stream Scanner Module” (’806 Patent, Claims 5 & 6)
`
`1.
`
`The claim itself connotes sufficient structure
`
`Defendants argue (at 14) that whether the word “scanner” connotes structure is “not a
`
`pertinent question.” This invites legal error. In Williamson, the Federal Circuit considered
`
`whether the prefix “distributed learning control” imparted sufficient structure to the claimed
`
`“module,” finding on the facts of that case that it did not. See Williamson v. Citrix Online, LLC,
`
`792 F.3d 1339, 1351 (Fed. Cir. 2015) (en banc). Similarly, in Power Integrations, the Federal
`
`Circuit considered whether the prefix “soft start” added sufficient structure when describing a
`
`claimed “circuit,” finding that it did. See Power Integrations, Inc. v. Fairchild Semiconductor
`
`Int'l, Inc., 711 F.3d 1348, 1364-65 (Fed. Cir. 2013). In Apex Inc. v. Raritan Computer, Inc., 325
`
`F.3d 1364, 1374 (Fed. Cir. 2003), the Federal Circuit cautioned that it would be legal error to
`
`interpret a claim as means-plus-function without considering the limitation as a whole, including
`
`any “adjectival qualifications.”
`
`Here, Defendants ignore the “adjectival qualifications,” which indisputably do recite
`
`struc