throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Examiner:
`
`Tarae, Catherine Michelle
`
`Art Unit:
`
`3992
`
`In re application of: Giobbi
`
`U.S. Patent No.:
`
`8,352,730
`
`Issued:
`
`January 8, 2013
`
`Application No.:
`
`11/314,199
`
`Filed:
`
`December 20, 2005
`
`Title: BIOMETRIC PERSONAL DATA
`KEY (PDK) AUTHENTICATION
`
`PATENT OWNER RESPONSE
`
`Mail Stop Ex Parte Reexam
`Attn: Central Reexamination Unit
`Commissioner for Patents
`P.O. Box 1450
`Alexandria, VA 22313
`
`Dear Commissioner:
`
`Proxense, the ownerof U.S. Patent 8,352,730 (“730 Patent”) hereby responds to the Order
`
`Granting Ex Parte Reexamination Petition. For the reasons described herein, these Reexamination
`
`proceedings should be terminated.
`
`Patent Owner Exhibit 2024, Page 1 of 11
`
`Patent Owner Exhibit 2024, Page 1 of 11
`
`

`

`TABLE OF CONTENTS
`
`I.
`
`Construction of “Third-Party Trusted Authority” 000.000.0000. cee cet ete eet teeseenteenneey 3
`
`Il.=The Prior Art (Alone or in Combination) Does Not Include a “Third-Party Trusted
`AUTOTIty” ooocen nec eee E LEE EOL fete de cit ttbetttitecidestieetirtititectieenreneey 4
`
`A.
`
`B.
`
`C.
`
`Ludtke Does Not Disclose a “Third-Party Trusted Authority”... 0. ceeeceeeeeeeee 5
`
`Okereke and Robinson Do NotDisclose a “Third-Party Trusted Authority”........ 10
`
`Scott Does Not Disclose a “Third-Party Trusted Authority” ....... eee esters 10
`
`THT.=Conclusion oe. ceee cece eeceeeeeceeesseeeeesseseeteeeeeesseeseeseesseeteeseseeseesseetsesseeteeeseeeeenees 11
`
`2
`
`Patent Owner Exhibit 2024, Page 2 of 11
`
`Patent Owner Exhibit 2024, Page 2 of 11
`
`

`

`Pursuant to 37 CFR 1.530 and 35 U.S.C. 304, Patent Ownerrespectfully submits this
`
`patent ownerstatement.
`
`At bottom, the patent claims of U.S. Patent No. 8,532,730 are patentable considering the
`
`cited prior art patents and printed publications alone or in any reasonable combination.
`
`Specifically, none of the prior art discloses a “third-party trusted authority” as that term has been
`
`construed by the Patent Trial and Appeal Board (“PTAB”).
`
`I.
`
`CONSTRUCTIONOF “THIRD-PARTY TRUSTED AUTHORITY”
`
`“During reexamination ordered under 35 U.S.C. § 304 ... claims are given the broadest
`
`reasonable interpretation consistent with the specification”. MPEP § 2258(1)G). “Under a
`
`broadest reasonable interpretation (BRI), words of the claim must be given their plain meaning,
`
`unless such meaningis inconsistent with the specification”. MPEP § 2111.01(1). Accordingly,
`
`during reexamination, terms of the claim are typically given their plain meaning. With respect to
`
`the ‘730 Patent, the PTAB hasalready ruledasto the plain meaning of “third-party trusted
`
`authority” and thus decided the broadest reasonable interpretation of the claims.
`
`In particular, the PTAB foundthat “[t]he plain meaning of ‘third-party trusted authority’
`
`suggests an entity or party separate from the principal parties to a transaction”. Samsung
`
`Electronics America, Inc. v. Proxense, LLC, TPR2021-01444, Paper 11 at 14 (PTAB February
`
`28, 2022). The PTAB further noted such wasconsistent with specification — noting Figure 3
`
`“depicts trusted key authority 320 as an entity separate from biometric key 100, authentication
`
`module 310, and application 330”. /d. Accordingly, the PTABinterpreted the plain meaning of
`
`“third-party trusted authority” consistent with the specification to be “a trusted authority that is
`
`an entity separate from the parties to a transaction”. /d, at 15. As the plain meaning defines the
`
`broadest reasonable interpretation consistent with the specification, the PTAB hasalready
`
`Patent Owner Exhibit 2024, Page 3 of 11
`
`Patent Owner Exhibit 2024, Page 3 of 11
`
`

`

`determined the broadest reasonable interpretation of “third-party trusted authority” and,
`
`therefore, the construction of the term to be applied in this reexamination.
`
`The PTAB also determined how the broadest reasonable interpretation of “third-party
`
`trusted authority” is to be applied when evaluating prior art. Whendistinguishing the claim 1
`
`from the prior art, the PTAB noted “the DPC appears to be whatis being accessed, as the payee
`
`and payor, with the PIA, accessalist of financial accounts from the DPC. Here, the DPC is the
`
`resource to be accessed, but it is a party to the transaction, rather than a third-party”. /d, at 26
`
`(internal citations omitted). Accordingly, under the broadest reasonable interpretation, a third-
`
`party trusted authority cannot be what is being accessed. The purported substantial new
`
`questions of patentability that is identified fail to account for a third-party trusted authority,
`
`which cannotbe the system being accessed.
`
`I.
`
`THE PRIOR ART (ALONEOR IN COMBINATION) DOES NOT INCLUDE A
`“THIRD-PARTY TRUSTED AUTHORITY”
`
`Claim 1 recites the action of “wirelessly sending one or more codes form the plurality of
`
`codes and other data values for authentication by an agent thatis third-party trusted authority
`
`possessing a list of device ID codes uniquely identifying legitimate integrated devices”.
`
`Similarly, claim 8 recites “a verification unit ... wirelessly sends one or more codes form the
`
`plurality of codes and other data values for authentication by an agent thatis a third-party
`
`trusted authority possessing a list of device ID codes uniquely identifying legitimate integrated
`
`devices.” Claim 15 also requires the presence of a componentthat sendsto a third-party trusted
`
`authority, reciting “an authentication unit ... send the plurality of codes and the other data values
`
`to an agent for authentication to determine whether the one or more codes and the other data
`
`values are legitimate, wherein the agentis a third-party trusted authority possessingalist of
`
`device ID codes uniquely identifying legitimate integrated devices.” Thus claims 1, 8, and 15
`
`Patent Owner Exhibit 2024, Page 4 of 11
`
`Patent Owner Exhibit 2024, Page 4 of 11
`
`

`

`require the action of sending to a third-party trusted authority or the presence of a component
`
`carrying out such action.
`
`Instead of sending to a third-party party trusted authority, claims 12 recites “receiving
`
`one or more codes from a plurality of codes and other data values including a device ID code...
`
`the device ID code being registered with an agent thatis a third-party trusted authority
`
`possessing a list of device ID codes uniquely identifying legitimate integrated devices.” Claim
`
`12 thus requires receiving a device ID code registered with a third-party trusted authority.
`
`A.
`
`Ludtke Does Not Disclose a “Third-Party Trusted Authority”
`
`Regardless of sending or receiving, each of the independent claims at issue require
`
`communicating with a third-party trusted authority that, under the broadest reasonable
`
`interpretation, is not the system being accessed. In finding substantial new questions of
`
`patentability, the Examineridentified the transaction privacy clearing house (TPCH) of Ludtke
`
`(U.S. Patent No. 7,188,110) as the third-party trusted authority. Specifically, the Examiner noted
`
`the “the transaction device information is provided to the TPCH 110 that then indicates to the
`
`vendorand the user approval of the transaction to be performed”and that “the transaction
`
`privacy clearing house maintains a secure database of transaction device information.” Decision
`
`on Requestfor Ex Parte Reexamination, mailed August 2, 2022, at 8-9. Thoughnotspecifically
`
`identifying the TPCH asthe third-party trusted authority, the Examiner appearsto be referencing
`
`the list of device ID codes possessedby a third-party trusted authority and a communication with
`
`a third-party trusted authority as recited in the claims. In so doing, the Examiner appears to
`
`equate the third-party trusted authority with the TPCH. However,just like the DPC of Laps/ey,
`
`the TPCH of Ludtke is the system being accessed by the payee and payor; the TPCH
`
`authenticates the transaction andsettles the funds and thusis not a third-party trusted authority.
`
`Patent Owner Exhibit 2024, Page 5 of 11
`
`Patent Owner Exhibit 2024, Page 5 of 11
`
`

`

`Whenattempting to purchase goods, the TPCHis accessed by the userto transfer the
`
`appropriate financial credit into the vendor’s account. This is shown in clearly in Ludtke ’s
`
`Figures 16 and 17 (reproduced below).
`
`CLERK
`
`RETAIL POS
`TERMINAL
`
`TPCH
`
`VENDOR
`
`1601
`DISPLAY CURRENT TOTAL
`
`PRIVACY
`CARD
`
`3}
`
`DIGITAL
`WALLET
`
`i}
`
`USER
`
`ii
`
`PEeemeacermaeeeeeeeeeeeeeeeee.
`aN1618 RETURNECARD & PAPER @aCEIRThi
`
`d
`
`Oooeeeaeeee
`
`‘
`
`RETATRANSACTION
`
`FIG. 1 6
`
`Patent Owner Exhibit 2024, Page 6 of 11
`
`iii3}tt't'
`
`eeeeheee
`
`vhucoeerunouasdPURCHASE
`
`
`1862 fun
`{
`1803 REQUESTPAYMENT
`;
`eeeneesnenSen
`| 1604TRIGGERPAYMENT WITH ECOUPONS
`11605REQUESTAlAUTHORIZATION & INFO
`‘iets PROVIDE FINGERPRINT, ECOUPON SELECTION
`1 1607 DISPLAY ECHUPONS
`[ene
`!
`1 1809 REQUEST CARD
`11608 SCAN BARCODES
`t
`(1649 SELECTACCOUNT
`eeoeeeoe
`$1611 SEGURE EXCHANGE, PROGRAMMAG STRIPE
`3
`Rd
`1612 READY TO UBE
`hepteeonenne—reemaanannncel
`£1613 REMOVE CARO. HAND TO CLER
`mt 1B SWIPE CAR
`F645 TRANSACTEiGN REQUEST: PURCHASE RECORD, ACCOUNT INFO
`1
`1 1616, 1817 TRANSACTION CONFIRMATION
`t
`;
`IS19/SETTLE FUNDS, DATA MINING INFO
`Posiaenseensestotenneneiereetiy
`3620 ELECTRONIC RECEIPT VIA INTERNET
`
`
`i §
`
`t '
`
`$ifI
`
`Oneeenee
`
`Patent Owner Exhibit 2024, Page 6 of 11
`
`

`

`VENDOR
`
`Tesm.petsStteteeStteSetbSAOaetateerenreAetyOkteseHette
`
`tataeheeaaeaayleaahat
`eheatSenaAneeeicapyneeaepemeeae
`NieattteesentnetiateSe
`seehaia
`
`{I
`
`6 USER VALIGATED
`__ACCOUNT DATA
`
`111 '
`
`'
`9-17 TRANSACTION CONFIRMATION
`
`:j i
`
`tt
`
`t
`t
`i
`!
`}
`t
`
`j
`i CONTENT
`!
`tpsseoenneromaasebrenaumnooroeny
`t
`fetae
`
`Fe SECURECONTENTDISTRIBUTION i
`_
`ap
`Aeea
`14 CONFIRMATION OF RECEIPT
`1
`i
`i
`j
`j
`q
`
`4 SETTLE FUNDS)
`Peer’
`neiete
`
`WEB TRANSACTION
`
`FIG : | f
`
`Figures 16 and 17 of Ludtke detail use of the TPCHin retail and web transactions,
`
`respectively. The transactions involve access of the TPCH by a user via a POS terminal. As
`
`described in Ludtke, “the POS terminal may collect the necessary information from the
`
`transaction device, e.g., digital wallet, combine it with the purchase data, and sendit to the
`
`TPCH. The TPCH maythen authorize the transaction, store data relevantto the transaction inits
`
`records andtrigger a financial transfer to the vendor’s account.” Ludtke, 23:50-55; see alsoid.,
`
`21:51-57 (“In one embodiment, a POS terminalis the link betweenthe digital wallet or privacy
`
`card and the transaction privacy clearing house (TPCH)of the eCommerce system.”). The main
`
`purpose of Ludtke’s POS terminalis to establish a secure transaction connection between the
`
`Patent Owner Exhibit 2024, Page 7 of 11
`
`BROWSER
`DIGITAL
`:
`WALLET
`i
`;
`¢ TRIGGER PURCHASE
`rerenni
`2 REQUEST PURCHASE}
`PROVIDE PURCHASE RECGAD
`i
`{ SVALIDATE USES, GET ACCOUNT INFO
`'4 REQUEST FINGERPRINT,
`ACCOUNTsoAcaeuiSELEGTON
`
`§ PROVIDEFINGERPRINT,
`ACCOUNT SELECTION
`|
`1
`
`USER
`
`PPOS
`TERMINAL
`
`TPCH
`
`eeeres
`
`7 TRANSACTION reouesr
`PURCHASE RECORD, OW 10,
`|_ACCOUNT INFO
`t
`| 8 TRANSACTION3
`4QNFIBMATION|
`
`Patent Owner Exhibit 2024, Page 7 of 11
`
`

`

`transaction device and the TPCHandtotransfer transaction data to the TPCH for completion of
`
`the transaction.
`
`Accordingly, as shown by step 1615 in Figure 16 of Ludtke, “the retail POS terminal
`
`establishes a secure connection with the TPCH,and requests that the transaction be carried out.”
`
`Ludtke, 27:56-58. Prior to this, as shown by steps 1611, 1613 and 1614, the POS receives data
`
`from the digital wallet via the magnetic stripe on a privacy card interfaced with the digital wallet
`
`and then POS. Duringa retail transaction, therefore, the POS receives data from the digital
`
`wallet and then the “POS terminal establishes a secure connection with the TPCH,and requests
`
`that the transaction by carried out, step 1615.” Ludtke, 27:56-58. After receiving the request and
`
`sending a confirmation messageto the POS at step 1616, the process moves on to step 1619
`
`where“the TPCHsettles funds, transferring the appropriate amount into the vendor’s account”.
`
`Ludtke, 27:66-67. The TPCH, whichtransfers funds into the vendor’s account, is the same
`
`system being accessed by the user to pay the merchant—and therefore cannot be the claimed
`
`“third-party trusted authority.”
`
`A similar process for web transactions is shownin Figure 17 of Ludtke. However,
`
`instead of receiving data from the digital wallet via a magnetic stripe on a privacy card, the POS
`
`“communicates with the transaction device, asking the transaction device to validate the user,
`
`confirm that the user wants to make this transaction, and get the appropriate information for
`
`which account the user wants to use for payment.” Ludtke, 28:58-62. This is shown bystep 6 in
`
`Figure 17. “When information on the user’s side of the transaction has been set up to perform a
`
`transaction, the personal POS terminal opens a secure communication session to the TPCH,
`
`requesting a transaction. The personal POS terminal provides the transaction record thatit
`
`received from the web browserand the unique ID of the transaction device. The TPCH uses the
`
`Patent Owner Exhibit 2024, Page 8 of 11
`
`Patent Owner Exhibit 2024, Page 8 of 11
`
`

`

`unique ID ofthe transaction device to process the transaction.” Ludtke, 29: 6-14. Thus, as
`
`shownbystep 7 of Figure 17, the POS collects the necessary information from the transaction
`
`device, e.g., digital wallet, combines it with the purchase data, and sends it to the TPCH. The
`
`TPCHthensettles funds, as shownby step 15.
`
`“The settlement of funds involves the transfer of the appropriate financial credit into the
`
`vendor’s account.” Ludtke, 29:35-36. As shown in Figures 16 and 17, the settlement of fundsis
`
`handled by the TPCH. Settlement(i.e., transfer of funds) is one of the core functionalities of the
`
`TPCH. “The TPCHagent 615 handles system management and policy control and forms the
`
`corefunctionality of the TPCH 600... Among the responsibilities handled by the agent include
`
`internal system managementfunctions, such as data mining, financial settlement and allocation
`
`ofpayments to internal and external accounts, and registration of new user joining the system.”
`
`Ludtke, 9:43-51. The TPCH is tendering paymentto the vendor by taking funds from the user’s
`
`account and transferring to the vendor’s account. Consequently, the TPCHis the system being
`
`accessed to tender payment to the vendor — and not the claimed “third-party trusted authority.”
`
`As noted supra, the PTAB has already determined the broadest reasonable interpretation
`
`of “third-party trusted authority”, under which a third-party trusted is not the system being
`
`accessed. The PTAB held the plain meaning of “third-party trusted authority” — which defines
`
`its broadest reasonable interpretation — is “an entity or party separate from the principal parties to
`
`a transaction”. IPR2021-01444, Paper 11 at 15. The TPCH, however,is the resource to be
`
`accessed to tender payment, makingit a party to the transaction. Based on similarinteractions,
`
`the PTAB held Zaps/ey’s DPC, usedto access a list of financial account, is not a third-party
`
`trusted authority because it is the system being accessed. /d. at 26-27. Thus, because Ludtke ’s
`
`TPCHis the system being accessed to tender payment,it is not a third-party trusted authority
`
`Patent Owner Exhibit 2024, Page 9 of 11
`
`Patent Owner Exhibit 2024, Page 9 of 11
`
`

`

`under what the PTAB hasdeterminedto be the broadest reasonable interpretation. As such,
`
`Ludtke does not disclose or suggest the claimed “third-party trusted authority.”
`
`B.
`
`Okereke and Robinson Do Not Disclose a “Third-Party Trusted Authority”
`
`The Examinerhas not pointed to the teachings of Okereke (U.S. Publication No.
`
`2003/0196084) or Robinson (U.S. Publication No. 2003/0177102) as raising substantial new
`
`questions of patentability with respect to a third-party trusted authority. Accordingly, neither
`
`Okereke nor Robinson, alone or in combination, discloses or suggests the claimed third-party
`
`trusted authority.
`
`C.
`
`Scott Does Not Disclose a “Third-Party Trusted Authority”
`
`With regards to Scott (WO 9956429 A2), the PTAB specifically held Scott fails to
`
`disclose a third-party trusted authority. IPR2021-01444, Paper 11 at 24-25. While, this finding
`
`may not have been presented in final written decision, it was a final determination ending the
`
`proceedings. A final determination, therefore, was made by the PTAB with respect to Scott's
`
`failure to disclose a third-party trusted authority. In view of this determination, and in point of
`
`fact, Scott does not disclose components for or actions of communicating with a third-party
`
`trusted authority as recited in the claims.
`
`10
`
`Patent Owner Exhibit 2024, Page 10 of 11
`
`Patent Owner Exhibit 2024, Page 10 of 11
`
`

`

`I.
`
`CONCLUSION
`
`In view of the foregoing, the substantial new questions of patentability that are identified
`
`by the Examiner do notestablish questions regarding components for or actions of
`
`communicating with a third-party trusted authority, and thus do not address all the limitations of
`
`the claims. In addition to not addressingall the limitations of the claims, the substantial new
`
`questions of patentability do not demonstrate the claims at issue are either anticipated or
`
`rendered obvious by Ludtke, Okereke, Robinson, or Scott, alone or in combination. Termination
`
`of these proceedings, therefore, is respectfully requested.
`
`DATED: November2, 2022
`
`Respectfully Submitted,
`
`Hard IP LLC
`
`/Kinza Hecht/
`Kinza Hecht
`Patent Agent
`Reg. No. 62,325
`Phone: (212) 321-0598
`Email: kinza@hard-ip.net
`
`11
`
`Patent Owner Exhibit 2024, Page 11 of 11
`
`Patent Owner Exhibit 2024, Page 11 of 11
`
`

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