throbber
Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 1 of 27
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`
`
`
`PROXENSE, LLC,
`
`Plaintiff,
`
`v.
`
`GOOGLE LLC,
`
`Defendant.
`
`Civil Action No. 6:23-cv-320
`
`JURY TRIAL REQUESTED
`
`DEFENDANT GOOGLE LLC’S OPENING CLAIM CONSTRUCTION BRIEF
`
`
`
`
`
`
`
`
`
`
`
`
`
`Patent Owner Exhibit 2005, Page 1 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 2 of 27
`
`
`
`
`
`I.
`
`II.
`
`TABLE OF CONTENTS
`
`Page
`
`Introduction ..........................................................................................................................1
`
`Background ..........................................................................................................................2
`
`III.
`
`Level of Skill in the Art .......................................................................................................3
`
`IV.
`
`Undisputed Terms ................................................................................................................3
`
`V.
`
`Disputed Terms ....................................................................................................................4
`
`A.
`
`B.
`
`3.
`
`Device ID Patents ....................................................................................................4
`1.
`“integrated device” (’730 claims 1, 15) .......................................................4
`2.
`“persistently storing … a plurality of codes and other data values
`comprising a device ID code … and a secret decryption value”
`(’730 claim 1, 15; ’954 claim 1, 22) ............................................................9
`“access message” terms (’730 claims 1, 15; ’954 claim 1, 22; ’905
`claim 1, 13) ................................................................................................11
`“The method of claim 1, wherein the biometric data and the scan
`data are both based on a fingerprint scan by the user.” (’730 claim
`5) ................................................................................................................13
`Hybrid Device Patents ...........................................................................................18
`1.
`“receiver-decoder circuit” (’042 claim 10; ’289 claim 14) ........................18
`2.
`“personal digital key” (’042 claim 10; ’289 claim 14) ..............................19
`
`4.
`
`VI.
`
`CONCLUSION ..................................................................................................................21
`
`
`
`
`
`
`
`
`
`Patent Owner Exhibit 2005, Page 2 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 3 of 27
`
`TABLE OF AUTHORITIES
`
`Page
`
`
`
`
`
`Cases
`
`In re Anderson,
`471 F.2d 1237 (C.C.P.A.1973) ........................................................................................................7
`Chef Am., Inc. v. Lamb-Weston, Inc.,
`358 F.3d 1371 (Fed. Cir. 2004)......................................................................................................18
`Dart Indus., Inc. v. Banner,
`636 F.2d 684 (D.C. Cir. 1980) .....................................................................................................7, 8
`Goldenberg v. Cytogen, Inc.,
`373 F.3d 1158 (Fed. Cir. 2004)........................................................................................................8
`Ingevity Corp. v. BASF Corp.,
`No. 18-CV-1391-RGA, 2019 WL 2356978 (D. Del. June 4, 2019) ................................................6
`IQASR LLC v. Wendt Corp.,
`825 F. App’x 900 (Fed. Cir. 2020) ..............................................................................................4, 6
`Iridescent Networks, Inc. v. AT&T Mobility, LLC,
`933 F.3d 1345 (Fed. Cir. 2019)....................................................................................................4, 5
`Litton Sys., Inc. v. Whirlpool Corp.,
`728 F.2d 1423 (Fed. Cir. 1984)........................................................................................................8
`Multilayer Stretch Cling Film Holdings, Inc. v. Berry Plastics Corp.,
`831 F.3d 1350 (Fed. Cir. 2016)................................................................................................13, 16
`Nautilus, Inc. v. Biosig Instruments, Inc.,
`572 U.S. 898 (2014) ...................................................................................................................9, 10
`In re Oda,
`443 F.2d 1200 (C.C.P.A.1971) ........................................................................................................7
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005)......................................................................................................19
`Proxense, LLC v. Samsung Elecs. Co., Ltd.,
`No. 6:21-cv-210-ADA (W.D. Tex.) .................................................................................................2
`Teva Pharms. USA, Inc. v. Sandoz, Inc.,
`789 F.3d 1335 (Fed. Cir. 2015)................................................................................................10, 11
`TMI Prod., Inc. v. Rosen Ent. Sys., L.P.,
`610 F. App'x 968 (Fed. Cir. 2015) .................................................................................................20
`Trustees of Columbia Univ. in City of New York v. Symantec Corp.,
`811 F.3d 1359 (Fed. Cir. 2016)......................................................................................................15
`
`
`
`Patent Owner Exhibit 2005, Page 3 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 4 of 27
`
`
`
`TurboCare Div. of Demag Delaval Turbomachinery Corp. v. Gen. Elec. Co.,
`264 F.3d 1111 (Fed. Cir. 2001)........................................................................................................8
`WSOU Investments LLC v. Google LLC,
`Nos. 2022-1066 & 2022-1067, 2023 WL 6210607 (Fed. Cir. Sept. 25, 2023) .............................15
`WSOU Invs., LLC v. Google LLC,
`No. 6:20-CV-00571-ADA, 2021 WL 11745550 (W.D. Tex. June 2, 2021)
`(Albright, J.), aff'd, No. 2022-1066, 2023 WL 6210607 (Fed. Cir. Sept. 25, 2023) .....................17
`
`Statutes
`35 U.S.C. § 112, ¶ 4 .......................................................................................................................13, 16
`
`Other Authorities
`U.S. Patent No. 8,352,730..........................................1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 17, 18
`U.S. Patent No. 8,646,042..........................................................................................1, 3, 18, 19, 20, 21
`U.S. Patent No. 8,886,954..........................................................................................1, 3, 6, 7, 8, 10, 12
`U.S. Patent No. 9,679,289................................................................................................1, 3, 19, 20, 21
`U.S. Patent No. 9,928,905....................................................................................................1, 2, 3, 8, 12
`U.S. Patent No. 10,073,960................................................................................................................1, 3
`
`
`
`
`
`Patent Owner Exhibit 2005, Page 4 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 5 of 27
`
`
`
`Defendant Google LLC (“Google) respectfully submits this Opening Claim Construction
`
`Brief for U.S. Patent No. 8,352,730 (“’730 patent”), U.S. Patent No. 8,886,954 (“’954 patent”),
`
`U.S. Patent No. 9,928,905 (“’905 patent”), U.S. Patent No. 8,646,042 (“’042 patent”), U.S. Patent
`
`No. 9,679,289 (“’289 patent”), and U.S. Patent No. 10,073,960 (“’960 patent”) asserted by
`
`Plaintiff Proxense, LLC (“Proxense”) in the above-captioned action.
`
`I.
`
`INTRODUCTION
`
`In all, there are six disputed terms that fall into two categories. First, there are three terms
`
`(i.e., “integrated device,” “plurality of codes and other data values,” and the “fingerprint”
`
`limitation in a dependent claim of the ’730 patent) that are indefinite because they fail to inform
`
`those of ordinary skill of the scope of the alleged inventions. The term “integrated device” is a
`
`coined term with no plain meaning, and the specification of the ’730 patent provides no guidance
`
`regarding the meaning of that term. This is confirmed by the fact that Proxense added an express
`
`definition for “integrated device” to the specifications of subsequent applications purporting to
`
`claim the benefit of the ’730 patent. But this definition is absent from the ’730 patent, rendering
`
`“integrated device” indefinite in the claims of that patent, where the term is not defined. Next, the
`
`phrase “plurality of codes and other data values” is susceptible to at least four different
`
`interpretations, each requiring different sets of data to be stored. Accordingly, this phrase too is
`
`indefinite because it fails to inform those of ordinary skill of the scope of the alleged invention and
`
`fails to put the public on notice of what would constitute infringement. Finally, dependent claim
`
`5 of the ’730 patent purports to narrow the “biometric data” from claim 1, but instead introduces
`
`language that conflicts with the plain meaning of claim 1. Because the claim is internally
`
`inconsistent and irreconcilable, it is indefinite.
`
`Second, there are three terms (i.e., the “access message” terms, “receiver-decoder circuit,”
`
`and “personal digital key”) that were previously construed by the Court, at least in part, and Google
`
`
`
`1
`
`Patent Owner Exhibit 2005, Page 5 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 6 of 27
`
`
`
`herein proposes only minor revisions or additions to ensure the Court’s constructions align with
`
`the plain meaning of the language of the claims asserted here.
`
`II.
`
`BACKGROUND
`
`The asserted patents belong to two different, purported patent families.1 The ’954 and ’905
`
`patents claim priority to the non-provisional application for the ’730 patent filed December 20,
`
`2005, as well as to two provisional applications, Nos. 60/637,538 (“’765 Prov. Appl.”) filed
`
`December 20, 2004, and 60/652,765 (“’765 Prov. Appl.”) filed February 14, 2005. The ’730, ’954,
`
`and ’905 patents are collectively referred to herein as the “Device ID patents.”
`
`The ’042, ’289, and ’960 patents all claim priority to a non-provisional application filed
`
`December 5, 2008, and provisional application No. 60/992,953 filed December 6, 2007. The ’042,
`
`’289, and ’960 patents are collectively referred to herein as the “Hybrid Device patents.”
`
`Members of both the Device ID and Hybrid Device patent families, including the ’730 and
`
`’905 patents, were previously construed by the Court in Proxense, LLC v. Samsung Elecs. Co.,
`
`Ltd., No. 6:21-cv-210-ADA (W.D. Tex.) (“the Samsung case”) in Dkt. 43 (“Order”) and Dkt. 149
`
`(“Memorandum in Support of Claim Construction Order”).2
`
`In this litigation, Proxense is asserting a limited set of claims from different members of
`
`the same previously-asserted patent families:
`
`Patent Family
`
`Patent
`
`Claims (independent claims emphasized)
`
`Device ID Patents
`
`’730 Patent
`
`1, 2-3, 5, 15, 16-17
`
`
`1 As addressed below, while the ’954 and ’905 patents purport to be continuations of the ’730
`patent, and thus are part of the same purported patent family, the applications for the ’954 and
`’905 patents add new matter not present in the ’730 patent, and thus the ’954 and ’905 patents’
`cannot be continuations of the ’730 patent.
`2 In the Samsung case, the asserted Device ID patents were the ’730 patent, the ’905 patent, and
`U.S. Pat. No. 10,698,989, and the asserted Hybrid Device patents were U.S. Pat. Nos. 9,049,188
`and 9,235,700.
`
`
`
`2
`
`Patent Owner Exhibit 2005, Page 6 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 7 of 27
`
`
`
`’954 Patent
`
`’905 Patent
`
`Hybrid Device Patents
`
`’042 Patent
`
`1, 2-3, 5-7, 22, 23-27
`1, 2, 4-5, 7, 133
`104
`
`’289 Patent
`
`’960 Patent
`
`14, 16
`
`14, 16
`
`
`III. LEVEL OF SKILL IN THE ART
`
`Google submits that a person of ordinary skill in the art would have had at least a B.S. in
`
`computer or electrical engineering, or equivalent, and at least three years of experience in the field
`
`of encryption and security or equivalent experience. More education could substitute for less
`
`experience, and vice-versa. Black Decl. ¶ 17.
`
`IV. UNDISPUTED TERMS
`
`The parties have agreed to the following constructions entered in the Samsung case:
`
`Term
`
`“device ID code” / “ID code” (’730 claims 1, 15; ’954
`claims 1, 22; ’905 claim 1, 13)
`
`Agreed Construction
`
`“a unique code identifying a device”
`
`“access message” (’730 claims 1, 15; ’954 claims 1,
`22; ’905 claim 1, 13)
`
`“a signal or notification enabling or
`announcing access”
`
`“persistently storing . . . a tamper proof format written
`to a storage element on the integrated device that is
`unable to be subsequently altered” (’730 claims 1, 15)
`
`“hybrid device” (’042 claim 10; ’289 claim 14)
`
`“enablement signal” (’042 claim 10; ’289 claim 14;
`’960 claim 14)
`
`No construction necessary
`
`“A device comprising an integrated
`personal digital key (PDK) and an
`integrated receiver-decoder circuit”
`
`No construction necessary
`
`
`3 Proxense’s cover pleadings to its infringement contentions identify dependent claim 15, but the
`accompanying claim chart is based on the language of independent claim 13. Google therefore
`understands claim 13 of the ’905 patent is asserted, not claim 15.
`4 Proxense’s complaint identifies claim 1 of the ’042 patent, but Proxense’s opposition to
`Google’s motion to dismiss stated that this was “a typographical error” and that, consistent with
`its infringement contentions, Proxense intended to assert claim 10. Dkt. 27 at 4 fn. 4.
`
`
`
`3
`
`Patent Owner Exhibit 2005, Page 7 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 8 of 27
`
`
`
`V.
`
`DISPUTED TERMS
`
`A.
`
`Device ID Patents
`
`1.
`
`“integrated device” (’730 claims 1, 15)
`
`Term
`
`Google’s Construction
`
`Proxense’s Construction
`
`“integrated device”
`
`Indefinite
`
`No construction necessary
`
`
`“[I]ntegrated device” is “a coined term, meaning it has no ordinary and customary
`
`meaning,” and thus “the question is whether the intrinsic evidence provides objective boundaries
`
`to the scope of the term.” See Iridescent Networks, Inc. v. AT&T Mobility, LLC, 933 F.3d 1345,
`
`1353 (Fed. Cir. 2019). Here, neither the claim language nor other intrinsic evidence defines the
`
`scope of the claimed “integrated device,” leaving undefined what types of devices are
`
`authenticated by the method and system of claims 1 and 15 of the ’730 patent and thereby rendering
`
`those claims indefinite. See, e.g., IQASR LLC v. Wendt Corp., 825 F. App’x 900, 908 (Fed. Cir.
`
`2020) (finding a “magnetic fuzz” claim term was indefinite because “‘patent fails to offer any
`
`meaningful and functional explanation’ of the definitional characteristics of ‘magnetic fuzz’”).
`
`The two asserted independent claims of the ’730 patent are directed to methods and systems
`
`for authenticating an “integrated device.” ’730 patent, claims 1 and 15. Asserted method claim 1
`
`requires storing a “device ID code uniquely identifying the integrated device” and “a third-party
`
`trusted authority possessing a list of device ID codes uniquely identifying legitimate integrated
`
`devices.” Asserted system claim 15 refers to “a device ID code uniquely identifying [a] biometric
`
`key” but then requires a “third-party trusted authority possessing a list of device ID codes uniquely
`
`identifying legitimate integrated devices.”
`
`As explained by Google’s expert, Dr. John Black, the term “integrated device” is not a
`
`known term used in connection with computer technology and lacks any ordinary or customary
`
`meaning. Black Decl. ¶ 20. Dr. Black’s survey of nine computer dictionaries did not identify a
`
`
`
`4
`
`Patent Owner Exhibit 2005, Page 8 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 9 of 27
`
`
`
`single definition for “integrated device.” Id. ¶¶ 21-22.
`
`The constituent words of “integrated device” also fail to inform one of ordinary skill
`
`regarding the scope of this claim term. For example, in asserted method claim 1, the term dictates
`
`that the claimed “device” being “authenticated” via the claimed method must be “integrated,” but
`
`other than indicating that the “integrated device” includes “a storage element,” the language of
`
`method claim 1 fails to define what it means for a device to be “integrated,” including whether it
`
`is the device itself that is “integrated” into a system or it is individual components that are
`
`“integrated” into the device, or anything about the nature or number of components that must be
`
`included in a device for it to qualify as an “integrated device.” Black Decl. ¶¶ 23-24. Asserted
`
`system claim 15 fares even worse, since it refers to “a biometric key,” yet does not identify whether
`
`that alone is an example of the claimed “legitimate integrated devices,” or what else would be
`
`required for such key to qualify as an “integrated device” (e.g., whether there is a particular
`
`arrangement of components within the key that must be “integrated” and/or whether there must be
`
`other system components in addition to that “biometric key” for it to qualify as an “integrated
`
`device”). Id. ¶ 25.
`
`Nor does “the intrinsic evidence provide[] objective boundaries to the scope of the term.”
`
`See Iridescent, 933 F.3d at 1353. Indeed, the specification of the ’730 patent provides no guidance
`
`whatsoever on the scope of the claimed “integrated device.” The term is found only in the abstract,
`
`which merely parrots the claim language. ’730 patent at Abstract. None of the figures in the
`
`specification, including Figures 1 and 2 showing a “Biometric Key,” are ever described as
`
`including an “integrated device.” The specification incorporates by reference the provisional
`
`applications, but those provisional applications also never use the term “integrated device,” instead
`
`at most referring to “integrated biometric readers/scanners” found in a “Bio Key.” Ex. 1 at 6; Ex.
`
`
`
`5
`
`Patent Owner Exhibit 2005, Page 9 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 10 of 27
`
`
`
`2 at 5. In sum, neither the ’730 patent nor any of its predecessor applications describes, or provides
`
`any guidance regarding the scope of, the claimed “integrated device.” Black Decl. ¶¶ 26-27.
`
`Accordingly, a POSITA reading the claim language and other intrinsic evidence is left
`
`without reasonable certainty as to whether the claimed “integrated device” refers to just a
`
`“Biometric Key” (due to its inclusion of “integrated biometric readers/scanners”), a device with a
`
`“Biometric Key,” or a device with a “Biometric Key” and other components. Nor can Proxense
`
`argue that the claim is broad enough to support all of the foregoing possibilities, because any such
`
`assertion leaves unanswered the fundamental question: what does it mean for the device to be an
`
`“integrated device” and what must be “integrated” for a device to become an integrated device?
`
`Because the intrinsic evidence fails to define the scope of the coined “integrated device” term, the
`
`asserted claims of the ’730 patent reciting the same are indefinite. See IQASR, 825 F. App’x at
`
`908; see also Ingevity Corp. v. BASF Corp., No. 18-CV-1391-RGA, 2019 WL 2356978, at *4 (D.
`
`Del. June 4, 2019) (finding “incremental adsorption capacity” indefinite as “it is neither a term of
`
`art nor defined by the patentee,” and a POSITA would need to select between multiple methods of
`
`measuring “adsorption capacity”).
`
`Subsequent developments in the purported Device ID patent family confirm the
`
`indefiniteness of the “integrated device” term in the ’730 patent claims. When Proxense filed the
`
`first purported continuation application from the ’730 patent application, which matured into
`
`the ’954 patent, it added an express definition for “integrated device” and a list of exemplary
`
`devices that qualify as an “integrated device”—none of which appears in the ‘730 patent:
`
`In one embodiment, the biometric key 100 is integrated into another
`object or device. A device having an integrated biometric key 100 is
`occasionally referred to herein as an “integrated device.” For
`example, in one embodiment, the biometric key 100 is integrated
`into a mobile phone (e.g. a cellular phone or smartphone), tablet,
`laptop, mp3 player, mobile gaming device, watch, key fob or other
`
`
`
`6
`
`Patent Owner Exhibit 2005, Page 10 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 11 of 27
`
`
`
`mobile device, thereby making the biometric key 100 unobtrusive
`to carry.
`
`’954 patent at 4:6-14. Thus, in later patent applications, Proxense deemed it necessary to define
`
`“integrated device” as a device (e.g., a cellular phone) “having an integrated biometric key.” Yet
`
`none of that discussion is found anywhere in the ’730 patent or either of its provisional
`
`applications.
`
`By adding a written description of what constitutes an “integrated device” to the ‘954
`
`patent application and its progeny, Proxense introduced new matter that is not part of the ‘730
`
`patent. See, e.g., Dart Indus., Inc. v. Banner, 636 F.2d 684, 688 (D.C. Cir. 1980) (“An addition to
`
`a patent specification constitutes ‘new matter’ when it changes the invention disclosed or
`
`introduces a concept not previously present in that specification.”) (citing In re Anderson, 471 F.2d
`
`1237, 1244 (C.C.P.A.1973); In re Oda, 443 F.2d 1200, 1203-05 & n.2 (C.C.P.A.1971)).
`
`Proxense’s addition of new matter only confirms that the “integrated device” recited in the ’730
`
`patent claims was inadequately defined in the ’730 patent specification, such that a POSITA would
`
`be unable to ascertain its scope. Proxense tacitly recognized this deficiency and surreptitiously
`
`sought to correct it in its subsequent application by adding a new definition, without alerting the
`
`USPTO to the addition of new matter. Ex. 3 at 48 (application data sheet for ’954 patent
`
`application, claiming it is a “continuation” ’730 patent application); Ex. 3 at 13-14 (paragraph
`
`[0025] of originally filed application for ’954 patent containing new matter relative to ’730 patent
`
`application without any indication that it is new).
`
`This addition of new matter in subsequent patents, however, cannot cure the indefiniteness
`
`of the earlier-filed ’730 patent claims, which issued without the benefit of Proxense’s belated
`
`attempt at lexicography. Not only did the subsequent ’954 and ’905 patents add a new definition
`
`of “integrated device,” these later patents disclosed and claimed an “integrated device” that
`
`
`
`7
`
`Patent Owner Exhibit 2005, Page 11 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 12 of 27
`
`
`
`“comprises one or more of a mobile phone, tablet, laptop, mp3 player, mobile gaming device,
`
`watch and a key fob” (’954 patent at 4:10-14; ’954 patent claims 6, 25; ’905 patent claims 5, 12,
`
`15), whereas the ’730 patent only disclosed that “biometric key 100 comprises a modified key fob”
`
`(’730 patent at 3:53-54). See Ex. 4 at 5 (redline comparison of ’954 patent to originally-filed non-
`
`provisional application for the ’730 patent); see also Dart Indus., 636 F.2d at 688.5
`
`The fact that these later patents disclosed and claimed embodiments (“a mobile phone,
`
`tablet, laptop, mp3 player, mobile gaming device, watch”) not found in the ’730 patent only
`
`confirms that they added new matter. See TurboCare Div. of Demag Delaval Turbomachinery
`
`Corp. v. Gen. Elec. Co., 264 F.3d 1111, 1119 (Fed. Cir. 2001) (finding claims improperly added
`
`new matter where the original disclosure was “completely lacking in any description” of the
`
`embodiment described in the claims). That fact has two consequences. First, because the ’954
`
`and ’905 patents added new matter, they cannot be “continuations” of the ’730 patent, which is the
`
`only relationship Proxense ever identified between the ’730, ’954, and ’905 patent. See Litton
`
`Sys., Inc. v. Whirlpool Corp., 728 F.2d 1423, 1437–38 (Fed. Cir. 1984). Second, even if Proxense
`
`were to argue that the ’954 and ’905 patents are continuations-in-part of the ’730 patent, the newly
`
`added definition of “integrated device” cannot be used to interpret the undefined “integrated
`
`device” term found in the earlier-filed ’730 patent claims. Indeed, the Federal Circuit has made
`
`clear that “new matter added by the [] continuation-in-part application” is “not part of the intrinsic
`
`evidence” of a patent at issue and, therefore, such new matter “is not available to construe the
`
`claims” of the patent at issue. Goldenberg v. Cytogen, Inc., 373 F.3d 1158, 1168 (Fed. Cir. 2004).
`
`
`5 The ’954 and ’905 patent also added new matter in the form of disclosure and claims
`specifying that the application to which access is controlled can be “a financial account (e.g. a
`savings account, checking account, brokerage account, credit card account, credit line, etc.)” or
`“medical information such as a medical record, insurance information or other healthcare
`information.” ’954 patent at 6:22-26; ’905 patent at 6:24-28; see also Ex. 4 at 8.
`
`
`
`8
`
`Patent Owner Exhibit 2005, Page 12 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 13 of 27
`
`
`
`Thus, the asserted ’730 patent claims are invalid as indefinite.
`
`2.
`
`“persistently storing … a plurality of codes and other data values
`comprising a device ID code … and a secret decryption value” (’730
`claim 1, 15; ’954 claim 1, 22)
`
`Term
`
`Google’s
`Construction
`
`Proxense’s
`Construction
`
`“persistently storing … a plurality of codes and
`other data values comprising a device ID
`code … and a secret decryption value”
`
`Indefinite
`
`No construction
`necessary
`
`
`The asserted claims of the ’730 and ’954 patents require “persistently storing … a plurality
`
`of codes and other data values comprising a device ID code … and a secret decryption value.”
`
`This claim language does not clearly delineate the scope of the claimed subject matter, leaving the
`
`scope of the claims unclear. Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898, 909 (2014)
`
`(“[A] patent must be precise enough to afford clear notice of what is claimed, thereby ‘appris[ing]
`
`the public of what is still open to them.’”). Indeed, the language is susceptible to at least four
`
`different interpretations—as shown through the use of parentheses to group different terms
`
`together and thereby change the interpretation—each resulting in different claim scope:
`
`1. “(plurality of (codes and other data values)) comprising (a device ID code and a secret
`
`decryption value)”: Under this interpretation, the claims require a plurality of elements,
`
`and each of those elements can be either a “code” or an “other data value.” Just storing one
`
`“device ID code” and one “secret decryption value” would meet this limitation.
`
`2. “((plurality of codes) and (other data values)) comprising (a device ID code and a secret
`
`decryption value)”: Under this interpretation, the claims require a plurality of code, and
`
`also require “other data values.” Because each of those terms is plurality, storing a single
`
`“device ID code” and a single “secret decryption value” would be required to meet the
`
`limitation, but not sufficient. Instead, you would need to store at least two codes and at
`
`
`
`9
`
`Patent Owner Exhibit 2005, Page 13 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 14 of 27
`
`
`
`least two values to meet the claim language.
`
`3. “(plurality of codes) and (other data values comprising a device ID code) and (a secret
`
`decryption value)”: Since the specification teaches that a single “code” can be one or more
`
`“values” (’730 Patent at 7:24-31), the limitation can also be interpreted to require storing
`
`three different types of codes/values: (1) a plurality of codes; (2) other data values
`
`comprising a device ID code; and (3) a secret decryption value. Under this interpretation,
`
`you would need to store at least three codes (two due to “plurality of codes” requirement;
`
`and one more due to the separate “device ID code requirement”) and at least one value to
`
`meet the claim language.
`
`4. “((plurality of (codes and other data values)) comprising a device ID code) and (a secret
`
`decryption value)”: Under this interpretation, the “plurality of codes and other data values”
`
`include the claimed “device ID code,” while the “secret decryption value” is a separate
`
`requirement. To meet the limitation would thus require storing at least two codes and at
`
`least one value.
`
`Because the asserted ’730 and ’954 patent claims and their specifications fail to specify
`
`with reasonable certainty the scope of the “persistently storing” limitation—including the number
`
`and nature of codes and values that must be stored—these claims are indefinite. The Federal Circuit
`
`has found a claim indefinite where a POSITA would have multiple interpretations of the same
`
`term. For example, in Teva Pharms. USA, Inc. v. Sandoz, Inc., the court determined that the term
`
`“molecular weight” could be understood to cover three different measurements – Mp, Mn, or Mw
`
`– and the claims “[did] not indicate which measure to use.” 789 F.3d 1335, 1344-45 (Fed. Cir.
`
`2015). As a result, the Federal Circuit determined that the patentee “failed to inform with
`
`reasonable certainty those skilled in the art about the scope of the invention.” The same logic
`
`
`
`10
`
`Patent Owner Exhibit 2005, Page 14 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 15 of 27
`
`
`
`applies here, where the term “persistently storing … a plurality of codes and other data values
`
`comprising a device ID code … and a secret decryption value” is susceptible to multiple
`
`interpretations and leaves a POSITA guessing as to the scope of the claim.
`
`3.
`
`“access message” terms (’730 claims 1, 15; ’954 claim 1, 22; ’905 claim
`1, 13)
`
`Term
`
`Google’s Construction
`
`Proxense’s Construction
`
`“an access message …
`[allowing / allows] the user
`[access to / to access] an
`application” (’730 claims 1,
`15; ’954 claim 1, 22)
`
`“an access message …
`[allowing / allows] the user to
`complete a financial
`transaction (’905 claim 1, 13)
`
`“a signal or notification
`allowing the user to access an
`application”
`
`No construction necessary
`beyond adopting the Court’s
`previous construction of
`“access message”
`
`“a signal or notification
`allowing the user to complete
`a financial transaction”
`
`No construction necessary
`beyond adopting the Court’s
`previous construction of
`“access message”
`
`
`This Court previously construed the term “access message” as “a signal or notification
`
`enabling or announcing access.” Google is not challenging the Court’s holding that an “access
`
`message,” in the abstract, is not limited to just “enabling” access and can include “announcing”
`
`access. However, this construction leaves the impression that the “access message,” as specifically
`
`used in the asserted claims, may be used merely as notification that a user (previously) accessed
`
`an application or completed a financial transaction. Such an interpretation of the claims would be
`
`incorrect and conflict with the plain meaning of the remaining claim language and, as such,
`
`Google’s clarifications are necessary to avoid an improper application to the claims.
`
`Specifically, the remaining claim language is clear that any “signal or notification” must
`
`do more to meet the claims than just “announc[e]” prior access; it must “allow” the user “to access
`
`an application” or “to complete a financial transaction”:
`
`
`
`’730 patent claim 1: “receiving an access message from the agent allowing the user access
`
`to an application;”
`
`
`
`11
`
`Patent Owner Exhibit 2005, Page 15 of 27
`
`

`

`Case 6:23-cv-00320-ADA Document 40 Filed 11/06/23 Page 16 of 27
`
`
`
`
`
`
`
`
`
`
`
`
`
`’730 patent claim 15: “receiving an access message from the agent allowing the user to
`
`access an application;”
`
`’954 patent claim 1: “receiving, at an application, an access message from the trusted
`
`authority … allowing the user access to the application;”
`
`’954 patent claim 22: “receives an access message from the trusted authority … and allows
`
`the user to access an application;”
`
`’905 patent claim 1: “responsive to receiving an access message from the third-party trusted
`
`authority …, allowing the user to complete a financial transaction;” and
`
`’905 patent claim 13: “receives an access messa

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