`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TYLER DIVISION
`
` CASE NO. 6:15-cv-01095
`
` [LEAD CASE]
`
`§§§§§§§§§§§
`
`PAPST LICENSING GMBH & CO.
`KG,
`
`Plaintiff,
`
`vs.
`
`APPLE INC., et al.,
`
`Defendants.
`
`MEMORANDUM OPINION AND ORDER
`
`This Memorandum Opinion construes disputed claim terms in U.S. Patent Nos. 6,470,399
`
`(“the ’399 Patent”), 6,895,449 (“the ’449 Patent”), 8,504,746 (“the ’746 Patent”), 8,966,144 (“the
`
`’144 Patent”), and 9,189,437 (“the ’437 Patent”) (collectively, the “patents-in-suit”) asserted by
`
`Plaintiff Papst Licensing GmbH & Co., KG (“Plaintiff”) against Defendants Apple Inc. (“Apple”),
`
`Lenovo (United States) Inc. (“Lenovo”), Motorola Mobility LLC (“Motorola”), LG Electronics,
`
`Inc., LG Electronics U.S.A., Inc., LG Electronics MobileComm U.S.A., Inc., (“LG”), Huawei
`
`Technologies Co., Ltd., Huawei Technologies USA, Inc. (“Huawei”), Samsung Electronics Co.,
`
`Ltd., Samsung Electronics America, Inc. (“Samsung”), and ZTE (USA) Inc. (“ZTE”) (collectively
`
`“Defendants”). On January 5, 2017, the parties presented oral arguments on the disputed claim
`
`terms at a Markman hearing. For the reasons stated below, the Court ADOPTS the following
`
`constructions.1
`
`1 For ease of reference, the Court’s constructions are reproduced in Appendix A.
`
`Papst Licensing GmbH & Co., KG.
`Petitioner – Apple, Inc.
`Patent Owner - Papst Licensing GmbH & Co., KG.
`IPR2016-01839
`EXH. 2003
`
`1
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 2 of 52 PageID #: 10319
`
`TABLE OF CONTENTS
`
`
`BACKGROUND ............................................................................................................................ 3
`APPLICABLE LAW ...................................................................................................................... 3
`Section 112(b): Indefiniteness .................................................................................................... 5
`Section 112(f): Means-Plus-Function Limitations ...................................................................... 6
`AGREED TERMS .......................................................................................................................... 7
`CLAIM CONSTRUCTION OF DISPUTED TERMS ................................................................... 7
`1. “connecting device” Terms .................................................................................................... 7
`2. “first command interpreter” and “second command interpreter” ........................................ 13
`3. “multi-purpose interface” ..................................................................................................... 17
`4. “specific driver for the multi-purpose interface” ................................................................. 19
`5. “parameter” and “signal” Terms .......................................................................................... 20
`6. “customary” Terms .............................................................................................................. 25
`7. “automatic” Terms ............................................................................................................... 29
`8. “data transmit/receive device” ............................................................................................. 34
`9. “simulating a virtual file system to the host” ....................................................................... 37
`10. “user-loaded” Terms .......................................................................................................... 39
`11. “input/output (i/o) port” ..................................................................................................... 43
`12. “analog signal acquisition channel[s],” “acquisition channels,” and “analog acquisition
`channel” .................................................................................................................................... 44
`APPENDIX A: COLLECTED CONSTRUCTIONS ................................................................... 47
`
`
`
`
`
`Page 2 of 52
`
`2
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 3 of 52 PageID #: 10320
`
`BACKGROUND
`
`
`
`“The five asserted patents share a common specification.” Dkt. No. 185 at 1 n.1. “The
`
`Patents generally relate to a unique method for achieving high data transfer rates for data
`
`acquisition systems (e.g., still pictures, videos, voice recordings) to a general-purpose computer,
`
`without requiring an end user to purchase, install, and/or run specialized software for each system.”
`
`Dkt. No. 175 at 1 (citing ’399 Patent at 4:23–27).
`
`
`
`Terms in the ’399 and ’449 Patents have been construed in a Multi-District Litigation
`
`proceeding: In re Papst Licensing GmbH & Co. KG Patent Litig., MDL No. 1880, Misc. Action
`
`No. 07-493 (D.D.C.) (“Papst MDL”). Claim constructions reached in the Papst MDL have been
`
`addressed by the Federal Circuit. See In re Papst Licensing Digital Camera Patent Litig., 778
`
`F.3d 1255, 1261–70 (Fed. Cir. 2015) (“Papst Opinion”).
`
`APPLICABLE LAW
`
`“It is a ‘bedrock principle’ of patent law that ‘the claims of a patent define the invention to
`
`which the patentee is entitled the right to exclude.’” Phillips v. AWH Corp., 415 F.3d 1303, 1312
`
`(Fed. Cir. 2005) (quoting Innova/Pure Water, Inc. v. Safari Water Filtration Sys., Inc., 381 F.3d
`
`1111, 1115 (Fed. Cir. 2004)). The Court examines a patent’s intrinsic evidence to define the
`
`patented invention’s scope. Id. at 1313–14; Bell Atl. Network Servs., Inc. v. Covad Commc’ns
`
`Group, Inc., 262 F.3d 1258, 1267 (Fed. Cir. 2001). Intrinsic evidence includes the claims, the rest
`
`of the specification and the prosecution history. Phillips, 415 F.3d at 1312–13; Bell Atl. Network
`
`Servs., 262 F.3d at 1267. The Court gives claim terms their ordinary and customary meaning as
`
`understood by one of ordinary skill in the art at the time of the invention. Phillips, 415 F.3d at
`
`1312–13; Alloc, Inc. v. Int’l Trade Comm’n, 342 F.3d 1361, 1368 (Fed. Cir. 2003).
`
`Page 3 of 52
`
`3
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 4 of 52 PageID #: 10321
`
`Claim language guides the Court’s construction of claim terms. Phillips, 415 F.3d at 1314.
`
`“[T]he context in which a term is used in the asserted claim can be highly instructive.” Id. Other
`
`claims, asserted and unasserted, can provide additional instruction because “terms are normally
`
`used consistently throughout the patent.” Id. Differences among claims, such as additional
`
`limitations in dependent claims, can provide further guidance. Id.
`
`“[C]laims ‘must be read in view of the specification, of which they are a part.’” Id. (quoting
`
`Markman v. Westview Instruments, Inc., 52 F.3d 967, 979 (Fed. Cir. 1995)). “[T]he specification
`
`‘is always highly relevant to the claim construction analysis. Usually, it is dispositive; it is the
`
`single best guide to the meaning of a disputed term.’” Id. (quoting Vitronics Corp. v.
`
`Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)); see Teleflex, Inc. v. Ficosa N. Am. Corp.,
`
`299 F.3d 1313, 1325 (Fed. Cir. 2002). In the specification, a patentee may define his own terms,
`
`give a claim term a different meaning than it would otherwise possess, or disclaim or disavow
`
`some claim scope. Phillips, 415 F.3d at 1316. Although the Court generally presumes terms
`
`possess their ordinary meaning, this presumption can be overcome by statements of clear
`
`disclaimer. See SciMed Life Sys., Inc. v. Advanced Cardiovascular Sys., Inc., 242 F.3d 1337,
`
`1343–44 (Fed. Cir. 2001). This presumption does not arise when the patentee acts as his own
`
`lexicographer. See Irdeto Access, Inc. v. EchoStar Satellite Corp., 383 F.3d 1295, 1301 (Fed. Cir.
`
`2004).
`
`The specification may also resolve ambiguous claim terms “where the ordinary and
`
`accustomed meaning of the words used in the claims lack sufficient clarity to permit the scope of
`
`the claim to be ascertained from the words alone.” Teleflex, Inc., 299 F.3d at 1325. For example,
`
`“[a] claim interpretation that excludes a preferred embodiment from the scope of the claim ‘is
`
`rarely, if ever, correct.’” Globetrotter Software, Inc. v. Elan Computer Group Inc., 362 F.3d 1367,
`
`Page 4 of 52
`
`4
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 5 of 52 PageID #: 10322
`
`1381 (Fed. Cir. 2004) (quoting Vitronics Corp., 90 F.3d at 1583). But, “[a]lthough the
`
`specification may aid the court in interpreting the meaning of disputed language in the claims,
`
`particular embodiments and examples appearing in the specification will not generally be read into
`
`the claims.” Constant v. Advanced Micro-Devices, Inc., 848 F.2d 1560, 1571 (Fed. Cir. 1988);
`
`see also Phillips, 415 F.3d at 1323.
`
`Although “less significant than the intrinsic record in determining the legally operative
`
`meaning of claim language,” the Court may rely on extrinsic evidence to “shed useful light on the
`
`relevant art.” Phillips, 415 F.3d at 1317 (quotation omitted). Technical dictionaries and treatises
`
`may help the Court understand the underlying technology and the manner in which one skilled in
`
`the art might use claim terms, but such sources may also provide overly broad definitions or may
`
`not be indicative of how terms are used in the patent. Id. at 1318. Similarly, expert testimony may
`
`aid the Court in determining the particular meaning of a term in the pertinent field, but “conclusory,
`
`unsupported assertions by experts as to the definition of a claim term are not useful.” Id.
`
`Generally, extrinsic evidence is “less reliable than the patent and its prosecution history in
`
`determining how to read claim terms.” Id.
`
`Section 112(b): Indefiniteness
`
`Patent claims must particularly point out and distinctly claim the subject matter regarded
`
`as the invention. 35 U.S.C. § 112(b). “A claim is invalid for indefiniteness if its language, when
`
`read in light of the specification and the prosecution history, ‘fail[s] to inform, with reasonable
`
`certainty, those skilled in the art about the scope of the invention.’” Biosig Instruments, Inc. v.
`
`Nautilus, Inc., 783 F.3d 1374, 1377 (Fed. Cir. 2015) (quoting Nautilus, Inc. v. Biosig Instruments,
`
`Inc., 134 S. Ct. 2120, 2124 (2014)). Whether a claim meets this definiteness requirement is a
`
`matter of law. Young v. Lumenis, Inc., 492 F.3d 1336, 1344 (Fed. Cir. 2007). A party seeking to
`
`Page 5 of 52
`
`5
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 6 of 52 PageID #: 10323
`
`invalidate a patent must overcome a presumption that the patent is valid. See 35 U.S.C. § 282;
`
`Microsoft Corp. v. i4i Ltd. P’ship, 131 S. Ct. 2238, 2243 (2011); U.S. Gypsum Co. v. Nat’l Gypsum
`
`Co., 74 F.3d 1209, 1212 (Fed. Cir. 1996). As such, the burden is on the challenging party to prove
`
`the patent’s invalidity by clear and convincing evidence. Microsoft, 131 S. Ct. at 2243; U.S.
`
`Gypsum Co., 74 F.3d at 1212. The ultimate issue is whether someone working in the relevant
`
`technical field could understand the bounds of a claim. Haemonetics Corp. v. Baxter Healthcare
`
`Corp., 607 F.3d 776, 783 (Fed. Cir. 2010).
`
`When a term of degree is used in a claim, “the court must determine whether the patent
`
`provides some standard for measuring that degree.” Biosig Instruments, Inc., 783 F.3d at 1378
`
`(internal quotation omitted). Likewise, when a subjective term is used in a claim, “the court must
`
`determine whether that patent’s specification supplies some standard for measuring the scope of
`
`the [limitation].” Datamize, LLC v. Plumtree Software, Inc., 417 F.3d 1342, 1351 (Fed. Cir. 2005).
`
`Section 112(f): Means-Plus-Function Limitations
`
`Asserted patents may contain means-plus-function limitations that require construction.
`
`Where a claim limitation is expressed in means-plus-function language and does not recite definite
`
`structure in support of its function, the limitation is subject to 35 U.S.C. § 112(f) (formerly 35
`
`U.S.C. § 112, ¶ 6). Braun Med., Inc. v. Abbott Labs., 124 F.3d 1419, 1424 (Fed. Cir. 1997). In
`
`relevant part, § 112(f) mandates that “such a claim limitation be construed to cover the
`
`corresponding structure . . . described in the specification and equivalents thereof.” Id. (citing 35
`
`U.S.C. § 112(f)). Accordingly, when faced with means-plus-function limitations, courts “must turn
`
`to the written description of the patent to find the structure that corresponds to the means recited
`
`in the [limitation].” Id.
`
`Page 6 of 52
`
`6
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 7 of 52 PageID #: 10324
`
`“It is well settled that a claim limitation that actually uses the word ‘means’ invokes a
`
`rebuttable presumption that § 112, ¶ 6 applies. In contrast, a claim term that does not use ‘means’
`
`will trigger the rebuttable presumption that § 112, ¶ 6 does not apply.” Apex Inc. v. Raritan Comp.,
`
`Inc., 325 F.3d 1364, 1371 (Fed. Cir. 2003) (citations omitted). The Federal Circuit elaborated that
`
`“[w]hen a claim term lacks the word ‘means,’ the presumption can be overcome and § 112, ¶ 6
`
`will apply if the challenger demonstrates that the claim term fails to recite sufficiently definite
`
`structure or else recites function without reciting sufficient structure for performing that function.”
`
`Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1349 (Fed. Cir. 2015) (quotations omitted).
`
`“The standard is whether the words of the claim are understood by persons of ordinary skill in the
`
`art to have a sufficiently definite meaning as the name for structure.” Id.
`
`AGREED TERMS
`
`The parties have presented no agreed-upon constructions. See Dkt. No. 151 at 2.
`
`CLAIM CONSTRUCTION OF DISPUTED TERMS
`
`1. “connecting device” Terms
`
`
`“a first connecting device for interfacing the host device with the interface device via the
`multi-purpose interface of the host device”
`(’399 Patent, Claims 1, 11; ’449 Patent, Claims 1, 17)
`
`
`
`“interfacing of the host device with a first connecting device of the interface device via
`the multi-purpose interface of the host device”
`(’399 Patent, Claim 14)
`
`
`Plaintiff’s Proposed Construction
`“a component or group of components for
`interfacing the interface device with the host
`device”
`
`If M+F [(means-plus-function)], alternatively:
`
`Function: Agreed
`
`
`Defendants’ Proposed Construction
`Samsung, Lenovo, and Motorola: Subject to
`§112(6)
`
`Function: [Agreed] interfacing the host device
`with the interface device via the multi-
`purpose interface of the host device.
`
`
`Page 7 of 52
`
`7
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 8 of 52 PageID #: 10325
`
`Structure: Fig. 1 and associated text (’399 and
`’449 Patents)
`
`
`Structure: 12xx structures as described at
`’399, col. 9:30–48 and Fig. 2.
`
`
`
`“a second connecting device for interfacing the interface device with the data
`transmit/receive device”
`(’399 Patent, Claims 1, 11; ’449 Patent, Claims 1, 17)
`
`“interfacing of the data transmit/receive device with a second connecting device of the
`interface device”
`(’399 Patent, Claim 14)
`
`
`Plaintiff’s Proposed Construction
`“a component or group of components for
`interfacing the interface device with the data
`transmit/receive device”
`
`If M+F [(means-plus-function)], alternatively:
`
`Function: Agreed
`
`Structure: Fig. 1 and associated text (’399 and
`’449 Patents)
`
`
`Defendants’ Proposed Construction
`Samsung, Lenovo, and Motorola: Subject to
`§112(6)
`
`Function: [Agreed] interfacing the interface
`device with the data transmit/receive device.
`
`Structure: 15xx structures as described at
`’399, col. 9:49–64 and Fig. 2.
`
`
`Dkt. No. 151, Ex. A at 1–2; Dkt. No. 175 at 4; Dkt. No. 185 at 2–3; Dkt. No. 197, Ex. A at 25–26,
`
`30–32 & 37.
`
`
`
`Plaintiff argues that its proposed construction is consistent with the Federal Circuit’s
`
`findings in the Papst Opinion. Dkt. No. 175 at 5. Plaintiff also submits that “[t]he words of the
`
`claims themselves explain the location of the first and second connecting device . . . .” Id. Further,
`
`Plaintiff argues, “[t]he varied usage of a term in the specification is evidence that it should be
`
`interpreted broadly.” Id. at 6. Finally, Plaintiff argues that Defendants cannot overcome the
`
`presumption that these non-means terms should not be treated as means-plus-function terms. Id.
`
`at 7–8.
`
`
`
`Defendants respond that these disputed terms are means-plus-function terms because “they
`
`have no structural meaning and the specification does not redefine the meaning of ‘connecting
`
`Page 8 of 52
`
`8
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 9 of 52 PageID #: 10326
`
`device’ in a way that connotes structure . . . .” Dkt. No. 185 at 3. In particular, Defendants argue
`
`that “device” is a “nonce” word that is tantamount to “means.” Id. at 3–4. Further, Defendants
`
`argue, “nothing in the specification or prosecution would inform one of skill in the art about the
`
`structural nature of the ‘connecting device’ term or otherwise impart structure to it.” Id. at 4.
`
`
`
`Plaintiff replies that a “term that identifies a variety of structures provides sufficient
`
`structure.” Dkt. No. 191 at 1.
`
`
`
`At the January 5, 2017 hearing, Defendants also urged that the word “component,”
`
`proposed by Plaintiff, is another “nonce” word that lacks structure. Docket No. 220 at 14:8–20.
`
`Plaintiff responded that Defendants are attempting to eliminate any consideration of the
`
`understanding of a person of ordinary skill in the art. See id. at 21:19–22:3.
`
`
`
`Title 35 U.S.C. § 112(f) (formerly 35 U.S.C. § 112, ¶ 6) provides: “An element in a claim
`
`for a combination may be expressed as a means or step for performing a specified function without
`
`the recital of structure, material, or acts in support thereof, and such claim shall be construed to
`
`cover the corresponding structure, material, or acts described in the specification and equivalents
`
`thereof.”
`
`
`
`“[T]he failure to use the word ‘means’ . . . creates a rebuttable presumption . . . that § 112,
`
`para. 6 does not apply.” Williamson, 792 F.3d at 1348 (citations and internal quotation marks
`
`omitted). “When a claim term lacks the word ‘means,’ the presumption can be overcome and §
`
`112, para. 6 will apply if the challenger demonstrates that the claim term fails to recite sufficiently
`
`definite structure or else recites function without reciting sufficient structure for performing that
`
`function.” Id. at 1349 (citations and internal quotation marks omitted).
`
`
`
`Williamson, in an en banc portion of the decision, abrogated prior statements that the
`
`absence of the word “means” gives rise to a “strong” presumption against means-plus-function
`
`Page 9 of 52
`
`9
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 10 of 52 PageID #: 10327
`
`treatment. Id. (citation omitted). Williamson also abrogated prior statements that this presumption
`
`“is not readily overcome” and that this presumption cannot be overcome “without a showing that
`
`the limitation essentially is devoid of anything that can be construed as structure.” Id. (citations
`
`omitted). Instead, Williamson found, “[h]enceforth, we will apply the presumption as we have
`
`done prior to Lighting World . . . .” Id. (citing Lighting World, Inc. v. Birchwood Lighting, Inc.,
`
`382 F.3d 1354, 1358 (Fed. Cir. 2004)). In a subsequent part of the decision not considered en
`
`banc, Williamson affirmed the district court’s finding that the term “distributed learning control
`
`module” was a means-plus-function term that was indefinite because of lack of corresponding
`
`structure, and in doing so Williamson stated that “‘module’ is a well-known nonce word.” 792
`
`F.3d at 1350.
`
`
`
`Williamson further noted that “[g]eneric terms such as ‘mechanism,’ ‘element,’ ‘device,’
`
`and other nonce words that reflect nothing more than verbal constructs may be used in a claim in
`
`a manner that is tantamount to using the word ‘means’ because they ‘typically do not connote
`
`sufficiently definite structure’ and therefore may invoke § 112, para. 6.” Id. (emphasis added;
`
`citations and internal quotation marks omitted).
`
`
`
`The term “connecting device,” as used in the ’399 Patent and ’449 Patent claims that are
`
`at issue here, is not a “nonce” term (see id.) but rather connotes a class of electrical connection
`
`structures, for example as disclosed in the specification as follows:
`
`In the preferred embodiment of the interface device 10 shown in FIG. 2, the first
`connecting device 12 of FIG. 1 contains the following components: an SCSI
`interface 1220 and a 50-pin SCSI connector 1240 for attachment to an SCSI
`interface present on most host devices or laptops. The SCSI (small computer
`system interface) interface 1220 translates the data received via the SCSI connector
`1240 into data understood by the DSP 1300, as known by those skilled in the art.
`Further, the first connecting device 12 comprises an EPP (enhanced parallel port)
`with a data transfer rate of approx. 1 MBps which delivers a more moderate data
`transfer rate of 1 MBps by comparison to the data transfer rate of 10 MBps of the
`
`Page 10 of 52
`
`10
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 11 of 52 PageID #: 10328
`
`SCSI interface. The EPP 1260 is connected to a 25-pin D-shell connector 1280 to
`permit attachment to a printer interface of a host device for example. Optionally,
`the first connecting device 12 also comprises a 25-pin connector 1282 which
`permits the attachment of 8 digital outputs and 8 digital inputs 1284 at a host device.
`
` *
`
` * *
`
`
`As described above, the first connecting device 12 comprises the SCSI interface
`1220 with a peak transfer rate of 10 MBps. An optional PCMCIA-to-SCSI adapter
`permits high-speed communication with laptop computers which are desirable and
`in widespread use, particularly by mobile service technicians. The EPP 1260 with
`its associated connector 1280 permits data transfer at a more moderate rate.
`
`’399 Patent at 9:29–47 & 10:59–65 (emphasis added). The opinion of Plaintiff’s expert is also
`
`persuasive in this regard. See Dkt. No. 175, Ex. 8, Nov. 21, 2016 Fernald Decl. at ¶ 38
`
`(“a component or group of components necessary to contribute to an electrical connection between
`
`the two devices to be interfaced together”). Further, surrounding claim language provides context
`
`as to the “inputs and outputs” and how a connecting device “interacts with other components . . .
`
`in a way that . . . inform[s] the structural character of the limitation-in-question or otherwise
`
`impart[s] structure.” Williamson, 792 F.3d at 1351. For example, a portion of Claim 1 of the ’399
`
`Patent recites (emphasis added): “the data transmit/receive device attached to the second
`
`connecting device of the interface device.” At the January 5, 2017 hearing, Plaintiff was amenable
`
`to construing the disputed terms as being “electrical” components. E.g., Docket No. 220 at 11:4–
`
`7 (“These are connecting devices or components that provide those electrical connections and
`
`nothing more is needed than those electrical connections.”).
`
`
`
`This finding of structure follows from the long-standing principles articulated prior to the
`
`abrogated Lighting World decision. See, e.g., Linear Tech. Corp. v. Impala Linear Corp., 379 F.3d
`
`1311, 1320 (Fed. Cir. 2004) (“when the structure-connoting term ‘circuit’ is coupled with a
`
`description of the circuit’s operation, sufficient structural meaning generally will be conveyed to
`
`Page 11 of 52
`
`11
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 12 of 52 PageID #: 10329
`
`persons of ordinary skill in the art, and § 112 ¶ 6 presumptively will not apply”; noting “language
`
`reciting [the circuits’] respective objectives or operations”); Apex, 325 F.3d at 1372 (“While we
`
`do not find it necessary to hold that the term ‘circuit’ by itself always connotes sufficient structure,
`
`the term ‘circuit’ with an appropriate identifier such as ‘interface,’ ‘programming’ and ‘logic,’
`
`certainly identifies some structural meaning to one of ordinary skill in the art.”); Personalized
`
`Media Commc’ns, LLC v. Int’l Trade Comm’n, 161 F.3d 696, 705 (Fed. Cir. 1998) (“Even though
`
`the term ‘detector’ does not specifically evoke a particular structure, it does convey to one
`
`knowledgeable in the art a variety of structures known as ‘detectors.’ We therefore conclude that
`
`the term ‘detector’ is a sufficiently definite structural term to preclude the application of § 112,
`
`¶ 6.”); Greenberg v. Ethicon Endo-Surgery, Inc., 91 F.3d 1580, 1583 (Fed. Cir. 1996) (finding that
`
`“detent mechanism” was not a means-plus-function term because it denotes a type of device with
`
`a generally understood meaning in the mechanical arts).2
`
`
`
`Defendants have cited TracBeam, LLC v. T-Mobile US, Inc., 6:14-CV-678-RWS, 2016 WL
`
`3751624, at *6 (E.D. Tex. July 14, 2016), but TracBeam is distinguishable because there the Court
`
`found that the context in which the terms at issue were used failed to suggest any structure. Here,
`
`by contrast, the above-discussed context provided by the claims and the specification demonstrate
`
`that the “connecting device” terms refer to electrical connections.
`
`
`
`The Court therefore hereby construes the disputed terms as set forth in the following chart:
`
`
`2 Greenberg, 91 F.3d at 1583 (“‘detent’ denotes a type of device with a generally understood
`meaning in the mechanical arts, even though the definitions are expressed in functional terms”);
`id. (“It is true that the term ‘detent’ does not call to mind a single well-defined structure, but the
`same could be said of other commonplace structural terms such as ‘clamp’ or ‘container.’ What
`is important is not simply that a ‘detent’ or ‘detent mechanism’ is defined in terms of what it
`does, but that the term, as the name for structure, has a reasonably well understood meaning in
`the art.”)
`
`Page 12 of 52
`
`12
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 13 of 52 PageID #: 10330
`
`Construction
`
`“first connecting device”:
`“a first electrical component, or group of
`electrical components, for interfacing the
`interface device with the host device”
`
`
`
`“second connecting device”:
`“a second electrical component, or group
`of electrical components, for interfacing the
`interface device with the data
`transmit/receive device”
`
`
`Term
`
`“a first connecting device for interfacing
`the host device with the interface device via
`the multi-purpose interface of the host
`device”
`
`(’399 Patent, Claims 1, 11; ’449 Patent,
`Claims 1, 17)
`
`
`“interfacing of the host device with a first
`connecting device of the interface device via
`the multi-purpose interface of the host
`device”
`
`(’399 Patent, Claim 14)
`
`“a second connecting device for interfacing
`the interface device with the data
`transmit/receive device”
`
`(’399 Pat., Cls. 1, 11; ’449 Pat., Cls. 1, 17)
`
`
`“interfacing of the data transmit/receive
`device with a second connecting device of
`the interface device”
`
`(’399 Pat., Cl. 14)
`
`
`
`2. “first command interpreter” and “second command interpreter”
`
`
`“first command interpreter” (’399 Patent, Claims 1, 11)
`
`
`Plaintiff’s Proposed Construction
`“a program that receives a command and
`executes some function based on that
`command”3
`
`If M+F [(means-plus-function)], alternatively:
`
`3 Plaintiff previously proposed: “a component or group of components for interfacing the
`interface device with the data transmit/receive device.” Dkt. No. 151, Ex. A at 2.
`
`Defendants’ Proposed Construction
`Samsung, Lenovo, and Motorola: Subject to
`§112(6)
`
`Function: [Agreed] when receiving an inquiry
`from the host device as to a type of a device
`
`Page 13 of 52
`
`13
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 14 of 52 PageID #: 10331
`
`
`Function: Agreed
`
`Structure: ’399 patent Fig. 1; 6:19–26, 6:48–
`55
`
`attached to the multi-purpose interface of the
`host device, sends a signal, regardless of the
`type of the data transmit/receive device
`attached to the second connecting device of
`the interface device, to the host device which
`signals to the host device that it is an
`input/output device customary in a host
`device, whereupon the host device
`communicates with the interface device by
`means of the [driver for the input/output
`device customary in a host device] [specific
`driver for the multi-purpose interface].
`
`Structure: No algorithm, source code, or flow
`chart is disclosed for performing the recited
`function, therefore the term is indefinite.
`
`
`Defendants’ Proposed Construction
`Samsung, Lenovo, and Motorola: Subject to
`§112(6)
`
`Function: [Agreed] interpret a data request
`command from the host device to the type of
`input/output device signaled by the first
`command interpreter as a data transfer
`command for initiating a transfer of the digital
`data to the host device.
`
`Structure: No algorithm, source code, or flow
`chart is disclosed for performing the recited
`function, therefore the term is indefinite.
`
`
`
`“second command interpreter” (’399 Patent, Claims 1, 11)
`
`
`Plaintiff’s Proposed Construction
`“a program that receives a command and
`executes some function based on that
`command”4
`
`If M+F [(means-plus-function)], alternatively:
`
`Function: Agreed
`
`Structure: ’399 patent Fig. 1; 6:19–26, 6:48–
`55
`
`
`Dkt. No. 151, Ex. A at 2–3; Dkt. No. 175 at 15; Dkt. No. 185 at 9; Dkt. No. 197, Ex. A at 38–39
`
`& 41–42.
`
`
`4 Plaintiff previously proposed: “a component or group of components for interfacing the
`interface device with the data transmit/receive device.” Dkt. No. 151, Ex. A at 2.
`
`Page 14 of 52
`
`14
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 15 of 52 PageID #: 10332
`
`
`
`Plaintiff argues that its proposal is supported by the specification as well as by “[t]he
`
`common and ordinary meaning of command interpreter at the time of the invention.” Dkt. No. 175
`
`at 16. Plaintiff also argues that Defendants cannot overcome the presumption that these non-means
`
`terms should not be treated as means-plus-function terms. Id. at 17.
`
`
`
`Defendants respond that “command interpreter” is purely functional in nature and does not
`
`connote any structure. Dkt. No. 185 at 10. Defendants also urge that “[t]he specification fails to
`
`disclose any structure corresponding to the claimed functions” and “fails to disclose an algorithm
`
`for performing the claimed functions.” Id. at 12, 14.
`
`
`
`Plaintiff replies that “‘[c]ommand interpreter’ is a well-understood structure in computer
`
`science,” and “the claims also explain exactly how the commands are interpreted.” Dkt. No. 191
`
`at 3–4.
`
`
`
`Legal principles regarding 35 U.S.C. § 112, ¶ 6 and Williamson, 792 F.3d 1339, are
`
`discussed above as to the “connecting device” terms.
`
`
`
`Here, “command interpreter” is not a “nonce” term (see Williamson, 792 F.3d at 1350) but
`
`rather connotes a class of structures. See ’399 Patent at 6:48–55; see also Dkt. No. 175, Ex. 9, The
`
`IEEE Standard Dictionary of Electrical and Electronics Terms 549 (6th ed. 1996) (“A computer
`
`program that translates and executes each statement or construct of a computer program before
`
`translating and executing the next.”); id., Ex. 11, Microsoft Press Computer Dictionary 101 (3d
`
`ed. 1997); id., Ex. 8, Nov. 21, 2016 Fernald Decl. at ¶ 45. Also, surrounding claim language
`
`provides context as to the “inputs and outputs” and how a command interpreter “interacts with
`
`other components . . . in a way that . . . inform[s] the structural character of the limitation-in-
`
`question or otherwise impart[s] structure.” Williamson, 792 F.3d at 1351. For example, a portion
`
`of Claim 1 of the ’399 Patent recites (emphasis added): “wherein the first command interpreter is
`
`Page 15 of 52
`
`15
`
`
`
`Case 6:15-cv-01095-RWS Document 275 Filed 03/07/17 Page 16 of 52 PageID #: 10333
`
`configured in such a way that the command interpreter, when receiving an inquiry from the host
`
`device as to a type of a device attached to the multi-purpose interface of the host device, sends a
`
`signal, regardless of the type of the data transmit/receive device attached to the