throbber
Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 1 of 27
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`PROXENSE, LLC,
`
`Plaintiff,
`
`v.
`
`MICROSOFT CORPORATION,
`
`Defendant.
`
`Case No. 6:23-cv-00319-ADA
`
`MICROSOFT CORPORATION’S OPENING CLAIM CONSTRUCTION BRIEF
`
`1
`
`MICROSOFT 1013
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 2 of 27
`
`TABLE OF CONTENTS
`
`Page(s)
`
`I.
`
`II.
`
`III.
`
`IV.
`
`INTRODUCTION .............................................................................................................. 1 
`
`LEGAL STANDARD ......................................................................................................... 1 
`
`AGREED CONSTRUCTIONS .......................................................................................... 2 
`
`THE ASSERTED PATENTS ............................................................................................. 2 
`
`A.
`
`B.
`
`Biometric Authentication Patents ........................................................................... 2 
`
`Hybrid Device Patents ............................................................................................ 3 
`
`V.
`
`DISPUTED CLAIM TERMS ............................................................................................. 3 
`
`A.
`
`B.
`
`C.
`
`D.
`
`“access message” (’730 Patent, claims 1, 15; ’954 Patent, claim 1; ’905
`Patent, claim 1) ....................................................................................................... 3 
`
`“wherein the biometric data and the scan data are both based on a fingerprint
`scan by the user” (’730 Patent, claim 5) ................................................................. 7 
`
`“personal digital key” or “PDK” (’042 Patent, claim 10) ..................................... 11 
`
`“receiver-decoder circuit” or “RDC” (’042 Patent, claim 10; ’289 Patent,
`claims 14 and 16) .................................................................................................. 17 
`
`VI.
`
`CONCLUSION ................................................................................................................. 21 
`
`i
`
`2
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 3 of 27
`
`
`
`Cases
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`Allergan Sales, LLC v. Sandoz, Inc.,
`935 F.3d 1370 (Fed. Cir. 2019)..................................................................................................1
`
`Cdn Innovations v. Grande Communs. Networks,
`No. 4:20-CV-653-SDJ, 2021 WL 3615908 (E.D. Tex. Aug. 13, 2021) ....................................4
`
`Central Admixture Pharmacy Services, Inc. v. Advanced Cardiac Solutions, P.C.,
`482 F.3d 1347, 82 U.S.P.Q.2d 1293 (Fed. Cir. 2007), cert. denied, 128 S. Ct.
`648 (U.S. 2007) ........................................................................................................................18
`
`Eon-Net LP v. Flagstar Bancorp,
`653 F.3d 1314 (Fed. Cir. 2011)................................................................................................13
`
`Exxon Chem. Patents, Inc. v. Lubrizol Corp.,
`64 F.3d 1553 (Fed. Cir. 1995)..................................................................................................18
`
`Goldenberg v. Cytogen, Inc.,
`373 F.3d 1158 (Fed. Cir. 2004)................................................................................................11
`
`Howmedica Osteonics Corp. v. Zimmer, Inc.,
`822 F.3d 1312 (Fed. Cir. 2016)................................................................................................12
`
`Huawei Techs. Co. v. T-Mobile US, Inc.,
`No. 2.16-CV-00055 JRG(RSP), 2017 WL 2190103 (E.D. Tex. May 17,2017) ........................7
`
`Indacon, Inc. v. Facebook, Inc.,
`824 F.3d 1352 (Fed. Cir. 2016)................................................................................................11
`
`Lexion Medical, LLC v. Northgate Techs., Inc.,
`641 F.3d 1352 (Fed. Cir. 2011)..................................................................................................1
`
`Multilayer Stretch Cling Film Holdings, Inc. v. Berry Plastics Corp.,
`831 F.3d 1350 (Fed. Cir. 2016)............................................................................................8, 10
`
`Nevro Corp. v. Boston Sci. Corp.,
`955 F.3d 35 (Fed. Cir. 2020)....................................................................................................17
`
`Pfizer, Inc. v. Ranbaxy Labs. Ltd.,
`457 F.3d 1284 (Fed. Cir. 2006)..................................................................................................7
`
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005)............................................................................................2, 11
`
`Praxair, Inc. v. ATMI, Inc.,
`543 F.3d 1306 (Fed. Cir. 2008)................................................................................................16
`
`ii
`
`3
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 4 of 27
`
`
`
`Renishaw PLC v. Marposs Societa’ per Azioni,
`158 F.3d 1243 (Fed. Cir. 1998)................................................................................................12
`
`Wi-LAN USA, Inc. v. Apple Inc.,
`830 F.3d 1374 (Fed. Cir. 2016)............................................................................................4, 13
`
`Statutes
`
`35 U.S.C. § 112 ¶ 4 ....................................................................................................................7, 10
`
`
`
`
`
`
`
`iii
`
`4
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 5 of 27
`
`TABLE OF EXHIBITS
`
`Ex. No.
`Ex. A
`Ex. B
`Ex. C
`
`Description
`2023-10-02 Email from counsel for Proxense regarding claim construction
`Excerpts from the file history for U.S. Patent No. 8,352,730
`Excerpts from the file history for U.S. Patent No. 8,886,954
`
`iv
`
`5
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 6 of 27
`
`
`
`I.
`
`INTRODUCTION
`
`Plaintiff Proxense, LLC (“Proxense”) asserts six patents, which can be categorized into
`
`two groups: (1) the “Biometric Authentication Patents,” which consist of U.S. Patent Nos.
`
`8,352,730, 8,886,954, and 9,298,905 and (2) the “Hybrid Device Patents,” which consist of U.S.
`
`Patent Nos. 8,646,042, 9,679,289, and 10,073,960. Several of the disputes as to the scope of the
`
`terms arise from infringement allegations against an unspecified group of Defendant Microsoft
`
`Corporation’s (“Microsoft”) offerings and various third-party offerings that are unrelated to
`
`Microsoft.1
`
`II.
`
`LEGAL STANDARD
`
`Claim terms should be “given their ordinary and customary meaning,” defined as “the
`
`meaning that the term would have to a person of ordinary skill in the art in . . . question at the time
`
`of the invention.” Allergan Sales, LLC v. Sandoz, Inc., 935 F.3d 1370, 1373 (Fed. Cir. 2019)
`
`(quoting Phillips v. AWH Corp., 415 F.3d 1303, 1312-13 (Fed. Cir. 2005)). “The words used in
`
`the claims are interpreted in light of the intrinsic evidence of record, including the written
`
`description, the drawings, and the prosecution history.” Id. (quoting Teleflex, Inc. v. Ficosa N.
`
`Am. Corp., 299 F.3d 1313, 1324 (Fed. Cir. 2002) (brackets omitted)); see also Lexion Medical,
`
`LLC v. Northgate Techs., Inc., 641 F.3d 1352, 1356 (Fed. Cir. 2011) (stating that the meaning of
`
`a disputed claim term “should be harmonized, to the extent possible, with the intrinsic record, as
`
`understood within the technological field of the invention”). “The construction that stays true to
`
`the claim language and most naturally aligns with the patent’s description of the invention will be,
`
`
`1 Proxense’s failure to define the Accused Product(s), as well as its violation of the fundamental
`rule prohibiting divided infringement, are discussed in Microsoft’s Motion to Dismiss for Failure
`to State a Claim (Dkt. No. 21) and its reply in support thereof (Dkt. No. 26).
`
`1
`
`6
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 7 of 27
`
`
`
`in the end, the correct construction.” Phillips, 415 F.3d at 1316 (quoting Renishaw PLC v.
`
`Marposs Societa’ per Azioni, 158 F.3d 1243, 1250 (Fed. Cir. 1998)).
`
`III. AGREED CONSTRUCTIONS
`
`The parties agree upon the following constructions:
`
`Term
`“ID code” or “device ID
`code”
`
`“hybrid device”
`
`Patents
`’730 Patent, claims 1, 3, 15;
`’954 Patent, claims 1, 3;
`’905 Patent, claims 1, 2
`’042 Patent, claim 10;
`’289 Patent, claims 14, 16
`
`Agreed-Upon Construction
`“a unique code identifying a device”
`
`“a device comprising an integrated
`personal digital key (PDK) and an
`integrated receiver-decoder circuit”
`
`
`
`Proxense stated that it: “does not believe any additional terms need to be construed and
`
`adopts the Court’s prior constructions for terms that have been previously construed by this Court
`
`in the Proxense, LLC v. Samsung et. al [sic] litigation.” Ex. A. For these two terms, Microsoft’s
`
`proposed constructions align with the Claim Construction order from Proxense, LLC v. Samsung
`
`Electronics Co., Ltd. et al., 6:21-cv-00210-ADA (W.D. Tex.) (“Proxense/Samsung”), Dkt. No. 43
`
`(Claim Construction Order). Hence, these terms are not disputed.
`
`IV.
`
`THE ASSERTED PATENTS
`A.
`
`Biometric Authentication Patents
`
`This first group of asserted patents relate to biometric authentication: U.S. Patent Nos.
`
`8,352,730 (the “’730 Patent”), 8,886,954 (the “’954 Patent”), and 9,298,905 (the “’905 Patent”)
`
`(collectively, the “Biometric Authentication Patents”). This Court has previously construed
`
`several terms for U.S. Patent Nos. 8,352,730 (the “’730 Patent”) and 9,298,905 (the “’905 Patent”)
`
`in Proxense/Samsung.
`
`The Biometric Authentication Patents relate generally to “computerized authentication”
`
`using biometric data. ’730 Patent at 1:15–18; ’954 Patent at 1:19–22; ’905 Patent at 1:21–24. The
`
`2
`
`7
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 8 of 27
`
`
`
`patents generally disclose a distributed form of biometric authentication involving biometric key
`
`that persistently stores biometric data in a tamper-resistant format, a scanner that collects biometric
`
`data from a user, and an integrated device that compares the scan against the biometric data and
`
`sends a code, for example to an application, to indicate that the user was successfully verified.
`
`’730 Patent at 1:59–67; ’954 Patent at 2:4–12; ’905 Patent at 2:6–14.
`
`B.
`
`Hybrid Device Patents
`
`The second group of asserted patents relate to hybrid devices: U.S. Patent Nos. 8,646,042
`
`(the “’042 Patent”), 9,679,289 (the “’289 Patent”), and 10,073,960 (the “’960 Patent”)
`
`(collectively, the “Hybrid Device Patents”). The disputed terms appear in the asserted claims of
`
`the ’042 and ’289 Patents. This Court previously construed terms in related patents, U.S. Patent
`
`Nos. 9,049,188 (the “’188 Patent”) and 9,235,700 (the “’700 Patent”) in Proxense/Samsung, but
`
`has not construed terms in the asserted Hybrid Device Patents.
`
`
`
`These patents generally relate “to a hybrid device including a personal digital key (PDK)
`
`and a receiver-decoder circuit (RDC) and methods for using same.” ’042 Patent at 1:21–27; ’289
`
`Patent at 1:44–52. The patents disclose “[p]roximity sensors and location tracking,” where
`
`“proximity sensors can be used to provide secure access to physical and/or digital assets, based on
`
`biometrics, passwords, PINs, or other types of authentication.” ’042 Patent at 1:30–33; ’289 Patent
`
`at 1:55–58.
`
`V.
`
`DISPUTED CLAIM TERMS
`A.
`
`“access message” (’730 Patent, claims 1, 15; ’954 Patent, claim 1; ’905
`Patent, claim 1)
`
`Microsoft’s Construction
`“a message enabling access”
`
`Proxense’s Construction
`Adopts the Proxense/Samsung Claim
`Construction Order:
`“A signal or notification enabling or
`announcing access”
`
`3
`
`8
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 9 of 27
`
`
`
`Microsoft’s proposed construction stays true to the claim language in which “access
`
`message” appears and the description in the specification. Microsoft proposes the natural reading
`
`of the “access message,” which is a message that itself enables access. Whereas Proxense,
`
`proposes that “access message” variably consists of different data and functions, such as a “signal
`
`or notification” (instead of, simply, “message”) that either “enable[es]” or “announces” access to
`
`the application, which receives the access message. In one instance, it functions as a key to gain
`
`access, in the other it functions as an alert to say that access has already been obtained.
`
`The claim language of the ’730 Patent expressly and repeatedly describes the access
`
`message as “allowing the user access to an application.” ’730 Patent at claims 1 (“receiving an
`
`access message from the agent allowing the user access to an application”), 8 (“receives an access
`
`message from the agent allowing the user access to an application”), 12 (“in response to a positive
`
`access message, allowing the biometrically verified user access to an application”), 15 (“the
`
`authentication unit receiving an access message from the agent allowing the user to access an
`
`application”). This mirrors the description of “access message” in the specifications of the
`
`Biometric Authentication Patents. ’730 Patent at 7:18–19 (“an access message to the application
`
`to allow user access”); ’954 Patent at 8:12–14 (same); ’905 Patent at 8:15–17 (same). Because the
`
`’730 Patent describes “access message” in only one manner in the entire specification (and the
`
`’954 and ’905 Patents mention “access message” only one additional time, in the Abstract), that
`
`description should weigh heavily during construction. See, e.g., Wi-LAN USA, Inc. v. Apple Inc.,
`
`830 F.3d 1374, 1382 (Fed. Cir. 2016) (“Consistent use of a term in a particular way in the
`
`specification can inform the proper construction of that term.”); Cdn Innovations v. Grande
`
`Communs. Networks, No. 4:20-CV-653-SDJ, 2021 WL 3615908, at *5 (E.D. Tex. Aug. 13, 2021)
`
`(quoting Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)) (finding that
`
`4
`
`9
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 10 of 27
`
`
`
`“[t]he specification is ‘always highly relevant to the claim construction analysis’ and is usually
`
`‘dispositive’” and that “[t]he specification ‘is the single best guide to the meaning of a disputed
`
`term.’”). Moreover, although not in the context of “access message” specifically, the specification
`
`describes sending a “message to [the] application 330, or otherwise allow[ing] access to the
`
`application” that is “responsive to a successful authentication by trusted key authority 320.” ’730
`
`Patent at 5:23–26; ’954 Patent at 6:15–17; ’905 Patent at 6:17–19. Notably, however, the
`
`specification does not describe sending a message to the application, or otherwise “announcing”
`
`access to the application, in a way that offers any support to Proxense’s construction.
`
`Microsoft’s construction is also consistent with the only depiction of “access message” in
`
`the figures of the Biometric Authentication Patents.
`
`’730 Patent at Fig. 7 (red box added); see also ’954 Patent at Fig. 7; ’905 Patent at Fig. 7. As
`
`shown, sending an “Access Message” (740) is right above “END” (795). See also ’730 Patent at
`
`
`
`5
`
`10
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 11 of 27
`
`
`
`7:18–23 (“If authentication is successful, the trusted key authority sends an access message to the
`
`application to allow user access . . . If authentication is not successful, authentication fails 750 and
`
`the message to the application indicates that the user should be denied access.”); ’954 Patent at
`
`8:12–17; ’905 Patent at 8:15–20. There is no indication of another function, such as sending a
`
`signal/notification announcing access.
`
`Further, Proxense’s proposed construction is illogical, as it calls for “announcing access”
`
`without requiring granting access. There is no alternate signal that Proxense proposes as the
`
`message enabling access, other than “access message.” So if, as Proxense proposes, “access
`
`message” can be either a “signal or notification enabling access” or a “signal or notification
`
`announcing access,” then, in instances where “access message” acts as an announcement, there
`
`would be no signal that enables access—making that announcement incorrect. Nor is there any
`
`support to add an “announcing” function on top of the enabling function when “access message”
`
`enables access. Indeed, “announcing access” is an addition that Proxense seeks to introduce to
`
`this claim term without support. In other words, Proxense’s construction, which adds an additional
`
`function of “announcing” access, is not only unsupported by the specification, but logically
`
`incompatible with the sequence of events as outlined by the claims and the specification.
`
`The Applicant’s statements during prosecution are also informative. During the
`
`prosecution of the ’730 and ’954 Patents, the Applicant stated that the user is allowed access upon
`
`receipt of an access message. See Ex. B (’730 Patent File History) at 9 (Resp. to July 7, 2010
`
`Office Action) (“The user is allowed access responsive to receipt of an access message from the
`
`agent that authenticates the code.”); Ex. C (’954 Patent File History) at 12 (Resp. to June 13, 2013
`
`Office Action) (“The user is allowed access responsive to receipt of an access message from the
`
`6
`
`11
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 12 of 27
`
`
`
`agent that authenticates the code.”).2 In contrast, a message, signal, or notification “announcing
`
`access” was never discussed.
`
`Proxense’s proposed construction of “a signal or notification enabling or announcing
`
`access” is unsupported by the intrinsic record. The terms “notification” (or “notice”) and
`
`“announcing” (or “announce”) are not found in the ’730, ’954, or ’905 Patents. Although the word
`
`“signal” appears in the specification, it is never used to describe the “access message.”
`
`Therefore, the term “access message” should be construed to mean “message enabling
`
`access.”
`
`B.
`
`“wherein the biometric data and the scan data are both based on a
`fingerprint scan by the user” (’730 Patent, claim 5)
`
`Microsoft’s Construction
`Invalid under 112 ¶ 4
`
`Proxense’s Construction
`Adopts the Proxense/Samsung Claim
`Construction Order:
`No construction needed, plain and ordinary
`meaning.
`
`Claim 5, which is dependent on claim 1, is invalid under 35 U.S.C. § 112 ¶ 4, because it
`
`
`
`improperly broadens the closed Markush grouping set forth in claim 1. § 112 ¶ 4 provides: “a
`
`claim in dependent form shall contain a reference to a claim previously set forth and specify a
`
`further limitation of the subject matter claimed.” Even when “attempting to claim what might
`
`otherwise have been patentable subject matter” if “all the limitations of the claim to which it refers”
`
`are not present, that claim is invalid. Pfizer, Inc. v. Ranbaxy Labs. Ltd., 457 F.3d 1284, 1291-93
`
`(Fed. Cir. 2006), accord Huawei Techs. Co. v. T-Mobile US, Inc., No. 2.16-CV-00055 JRG(RSP),
`
`2017 WL 2190103, at *28 (E.D. Tex. May 17, 2017) (invalidating claim under §112 ¶ 4 at claim
`
`construction). Here, dependent claim 4 attempts to broaden the scope of the closed group in its
`
`
`2 All emphases in quoted language have been added, unless otherwise indicated.
`
`7
`
`12
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 13 of 27
`
`
`
`parent claim, which precludes claim 4 from being narrower than claim 1. Where the referenced
`
`claim excludes a limitation, while the dependent claim includes it, that dependent claim is invalid.
`
`See Multilayer Stretch Cling Film Holdings, Inc. v. Berry Plastics Corp., 831 F.3d 1350, 1362
`
`(Fed. Cir. 2016).
`
`Generally, the use of a Markush group and the language “consisting of” provides a strong
`
`presumption of a closed group. Multilayer Stretch Cling Film Holdings, Inc. v. Berry Plastics
`
`Corp., 831 F.3d 1350, 1358 (Fed. Cir. 2016) (“claim drafters often use the term ‘group of’ to signal
`
`a Markush group.” “Use of the transitional phrase ‘consisting of’ to set off a patent claim element
`
`creates a very strong presumption that that claim element is ‘closed’ and therefore ‘exclude[s] any
`
`elements, steps, or ingredients not specified in the claim.’”). Here, both factors are present in claim
`
`1 and there is nothing in the specification or prosecution that would alter the very strong
`
`presumption that this group is closed. In fact, this Court has previously found that “Claim 1’s
`
`limitation ‘wherein the biometric data is selected from a group consisting of a palm print, a retinal
`
`scan, an iris scan, a hand geometry, a facial recognition, a signature recognition and a voice
`
`recognition’ is a closed Markush group.” See Proxense v. Samsung, Case No. 6:21-cv-00210-
`
`ADA, Dkt. No. 149 (Memorandum in Support of Claim Construction Order) at 23-24 (W.D. Tex.
`
`Dec. 28, 2022).
`
`Claim 1 of the ’730 Patent reads, in relevant part: “wherein the biometric data is selected
`
`from a group consisting of a palm print, a retinal scan, an iris scan, a hand geometry, a facial
`
`recognition, a signature recognition and a voice recognition.” The claimed list does not include
`
`fingerprints. But claim 5, which depends on claim 1, states: “5. The method of claim 1, wherein
`
`the biometric data and the scan data are both based on a fingerprint scan by the user.” This
`
`impermissibly attempts to expand the scope of the dependent claim beyond the categories
`
`8
`
`13
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 14 of 27
`
`
`
`disclosed in claim 1. A “fingerprint scan” of claim 5 is not a subpart or otherwise included in any
`
`of the terms in the closed Markush Group in claim 1 of the ’730 Patent. Nor is “fingerprint” a
`
`subset of “palm print,” “hand geometry,” or any other “biometric data” listed for claim 1. The
`
`specification distinguishes “palm print” and “hand geometry” as “other embodiments” from a
`
`“fingerprint.” See ’730 Patent at 3:4–11 (“[a]lthough the embodiments below are described using
`
`the example of biometric verification using a fingerprint, other embodiments . . . can include a
`
`palm print, a retinal scan, an iris scan, hand geometry recognition, facial recognition, signature
`
`recognition, or voice recognition.”).
`
`Further, in the related ’905 and ’954 Patents (the other two patents in the Biometric
`
`Authentication Patent group), Proxense specifically included “fingerprint” in addition to “palm
`
`print” and “hand geometry,” as shown below:
`
`Patent
`
`Exemplary Claim
`
`U.S. Patent No. 8,352,730
`
`U.S. Patent No. 8,886,954
`
`U.S. Patent No. 9,298,905
`
`Claim 1: “wherein the biometric data is selected from a group
`consisting of a palm print, a retinal scan, an iris scan, a hand
`geometry, a facial recognition, a signature recognition and a
`voice recognition.” [no mention of “fingerprint”]
`
`Claim 5: “The method of claim 1, wherein the biometric data
`includes one or more of a fingerprint, palm print, a retinal
`scan, an iris scan, a hand geometry, a facial recognition, a
`signature recognition and a voice recognition.”
`
`Claim 4: “The method of claim 1, wherein the biometric data
`includes data from one or more of a fingerprint, palm print,
`a retinal scan, an iris scan, a hand geometry, a facial
`recognition, a signature recognition and a voice recognition.”
`
`
`Clearly, by including “fingerprint” in addition to “palm print” and “hand geometry” for the
`
`’954 and ’905 Patents, Proxense’s Markush groupings recognize that fingerprint is a separate and
`
`distinct limitation that is not a palm print or hand geometry.
`
`9
`
`14
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 15 of 27
`
`
`
`Finally, the Federal Circuit has found that a claim that attempts to improperly broaden the
`
`scope of a closed Markush Group renders that claim indefinite. See, e.g., Multilayer, 831 F.3d at
`
`1356 (affirming the district court’s finding that claim was indefinite because it “attempts to
`
`improperly broaden the scope of the closed Markush Group in element (b) of Claim 1”). In
`
`Multilayer, the court found that claim 10, which depended on claim 1, required “at least one said
`
`inner layer comprises low density polyethylene homopolymers.” Id. Claim 1, in turn, required
`
`the inner layer to “be[] selected from the group consisting of linear low density polyethylene, very
`
`low density polyethylene, ultra low density polyethylene, and metallocene-catalyzed linear low
`
`density polyethylene resins.” Id. at 1353. Because claim 10’s “low density polyethylene
`
`homopolymers” was not listed in the closed Markush group in claim 1 and because it was “distinct
`
`from the four resins” recited in claim 1, the Federal Circuit affirmed the district court’s finding
`
`that claim 10 was indefinite. Id. at 1356. Similarly, here, claim 5 requires the biometric data to
`
`be a “fingerprint scan,” which is not listed in the closed Markush group in claim 1 (which consists
`
`only of “a palm print, a retinal scan, an iris scan, a hand geometry, a facial recognition, a signature
`
`recognition, and a voice recognition”). See ’730 Patent at claims 1, 5. Thus, by claiming a type
`
`of biometric data outside of this group, dependent claim 5 fails to further limit claim 1, rendering
`
`it invalid under Section 112 ¶ 4.
`
`Given the broadening of the Markush group in claim 1 to include the term “fingerprint,”
`
`Proxense should not be allowed “to recapture through litigation what the patentees forfeited during
`
`patent prosecution” and must instead “deal with the consequence of the patentee’s decision to add
`
`a Markush group to claim 1.” See Endo Pharm. Inc. v. Watson Labs., Inc., C.A. No. 10-138
`
`(GMS), Dkt. No. 92 at 1–2 n. 1 (D. Del. June 27, 2011).
`
`10
`
`15
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 16 of 27
`
`C.
`
`“personal digital key” or “PDK” (’042 Patent, claim 10)
`
`Microsoft’s Construction
`“a device that includes an antenna, a
`transceiver for communicating with the RDC
`and a controller and memory for storing
`information particular to a user”
`
`Proxense’s Construction
`Adopts the Proxense/Samsung Claim
`Construction Order re the ’188 and ’700
`Patents:
`
`“An operably connected collection of
`elements including an antenna and a
`transceiver for communicating with a RDC
`and a controller and memory for storing
`information particular to a user
`
`The Parties do not dispute that a “personal digital key” or “PDK” in the ’042 Patent
`
`
`
`
`
`includes an antenna, a transceiver for communicating with the RDC and a controller, and memory
`
`for storing information particular to a user. The dispute is whether a PDK is “a device” or is “[a]n
`
`operably connected collection of elements.” Based on the intrinsic evidence, “PDK” is plainly a
`
`device. The Court previously construed this term in Proxense/Samsung for the ’188 and ’700
`
`Patents, which were later dismissed by Proxense and not asserted in this case. Microsoft
`
`respectfully requests reconsideration of this term based on the additional evidence and argument
`
`presented herein.
`
`The claim language supports construing “PDK” as a device. See Phillips, 415 F.3d at 1314
`
`(“[T]he context in which a term is used in the asserted claim can be highly instructive.”). As an
`
`initial matter, “PDK” was coined by the inventor and not a term of art, and “[w]here a claim term
`
`has no ordinary and customary meaning, a court must resort to the remaining intrinsic evidence . .
`
`. to obtain the meaning of that term.” Goldenberg v. Cytogen, Inc., 373 F.3d 1158, 1164 (Fed. Cir.
`
`2004); see also Indacon, Inc. v. Facebook, Inc., 824 F.3d 1352, 1357 (Fed. Cir. 2016) (terms with
`
`no established meaning “ordinarily cannot be construed broader than the disclosure in the
`
`specification”). Claim 10 reads:
`
`11
`
`16
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 17 of 27
`
`
`
`10. A method comprising:
`
`creating a first wireless link between an integrated receiver-decoder circuit
`(RDC) of a hybrid device and an external personal digital key (PDK), the
`hybrid device including an integrated PDK and the integrated RDC;
`
`receiving a first signal at the integrated RDC via the first wireless link from
`the external PDK;
`
`generating an enablement signal enabling one or more of an application, a
`function and a service on one or more of the hybrid device and a device
`associated with an external RDC; and
`
`sending the enablement signal to one or more of the hybrid device and the
`device associated with an external RDC.
`
`’042 Patent at claim 10. As used in claim 10, a PDK is a device that may be “integrated” with a
`
`hybrid device or be an “external” device. Either way, the claim’s usage of “PDK” is consistent
`
`with the view that a PDK is a discrete device that is physically intact, not merely a collection of
`
`disparate elements. For example, if PDK is a collection of elements, the distinction between an
`
`“external PDK” and “integrated PDK” would be muddled, because different “elements” can be
`
`simultaneously external to, and integrated in, another device. The “wireless link” is also recited
`
`as begin “from the external PDK,” as opposed to some component that is a part of the PDK. The
`
`plain reading of claim 10 supports a PDK as a device, rather than a collection of elements.
`
`
`
`The specification also repeatedly and consistently describes PDK as a device, not an
`
`amorphous collection. A person of ordinary skill in the art “would naturally look to the written
`
`description for a full understanding of the claims.” Howmedica Osteonics Corp. v. Zimmer, Inc.,
`
`822 F.3d 1312, 1322 (Fed. Cir. 2016); Renishaw PLC v. Marposs Societa’ per Azioni, 158 F.3d
`
`1243, 1250 (Fed. Cir. 1998) (“The construction that stays true to the claim language and most
`
`naturally aligns with the patent’s description of the invention will be, in the end, the correct
`
`construction.”). The ’042 Patent’s abstract states: “[t]he hybrid device operates in one of several
`
`modes including, PDK only, RDC only, or PDK and RDC.” ’042 Patent at Abstract. Hence, the
`
`12
`
`17
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 18 of 27
`
`
`
`disclosed hybrid device includes a mode where PDK can function by itself. And the body of the
`
`specification repeatedly confirms that PDK is a device. See, e.g., ’042 Patent at 3:48–50 (“The
`
`PDK 102 is a compact, portable uniquely identifiable wireless device typically carried by an
`
`individual.”); 5:44–45 (“The PDK 102 can be standalone as a portable, physical device or can be
`
`integrated into commonly carried items”); 17:63–64 (“[A] PDK 102 b operating as the first device
`
`. . . .”). This further comports with the invention’s focus on proximity detection and location
`
`determination. See, e.g., ’042 Patent at 1:20–67. These descriptions show that the PDK is a device,
`
`whether it be standalone or integrated into another device and the consistent description of PDK
`
`as a device supports construing it as a device. See Wi-LAN USA, Inc. v. Apple Inc., 830 F.3d 1374,
`
`1382 (Fed. Cir. 2016) (“Consistent use of a term in a particular way in the specification can inform
`
`the proper construction of that term.”); Eon-Net LP v. Flagstar Bancorp, 653 F.3d 1314, 1321
`
`(Fed. Cir. 2011) (limiting claim terms “document” and “file” to “information that originates from
`
`a hard copy document” where “[t]he written description repeatedly and consistently defines the
`
`invention as a system that processes information derived from hard copy documents.”).
`
`The specification also describes the portability of the PDK, which makes sense, given that
`
`it is a Personal Digital Key meant to be carried by a person. The specification’s descriptions of
`
`the PDK’s portability are consistent with the understanding that a PDK is a singular device that
`
`can be easily carried by a person, rather than a “collection of elements.” See, e.g., ’042 Patent at
`
`3:48–50 (“The PDK 102 is a compact, portable uniquely identifiable wireless device typically
`
`carried by an individual.”); 12:26–28 (“In the example, a user carrying a PDK is located within
`
`a service oriented business, such as a department store, casino, restaurant, etc.”); 14:36–39 (“The
`
`SIM content (Cell phone account, contact information, and credit card information) that is
`
`normally stored in the cell phone 1202 is instead stored in the PDK 102 b carried by the user”);
`
`13
`
`18
`
`

`

`Case 6:23-cv-00319-ADA Document 31 Filed 11/06/23 Page 19 of 27
`
`
`
`14:65–6

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