throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Ex Parte Reexamination of
`
`U.S. Patent No. 9,298,905
`
`Inventor: John J. Giobbi
`
`Assignee: Proxense, LLC
`
`Control No. 90/015,053
`
`Issue Date: March 29, 2016
`
`Confirmation No. 7424
`
`Art Unit: 3992
`
`Examiner: Carlson, Jeffrey D.
`
`Title: BIOMETRIC PERSONAL DATA KEY (PDK) AUTHENTICATION
`
`Mail Stop Ex Parte Reexam
`Attn: Central Reexamination Unit
`Commissioner for Patents
`United States Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`INTERVIEW SUMMARY
`
`
`
`Patent Owner thanks Examiner Jeffery D. Carlson, Reexamination Specialist C. Michelle
`
`Tarae, and Supervisory Patent Examiner Michael Fuelling for the interview conducted on October
`
`9, 2024.
`
`Prior to the Interview, Patent Owner submitted and an Agenda detailing why a request for
`
`adverse judgement under 37 C.F.R. § 42.73(b) will be filed in IPR2024-00234. As noted in the
`
`Agenda, in Google, LLC. v. Proxense, LLC, IPR2024-00234, Decision Granting Institution, Paper
`
`10 at 10-11 (PTAB July 23, 2024), the PTAB apparently construed “financial transaction” as
`
`recited in claims 1, 9, and 13 as including transactions in which the principal parties are a merchant
`
`(e.g., grocery store) and a user. Financial transactions in which the principal parties are a user and
`
`merchant, however, lack written description support and/or are not enabled by the 905 Patent. The
`
`claims, as apparently construed by the PTAB in IPR2024-00234, therefore, are invalid under 35
`
` 1
`
`Patent Owner Exhibit 2016, Page 1 of 6
`
`

`

`U.S.C. § 112 irrespective of the prior art. This renders moot the Final Rejection and Appeal in the
`
`present proceedings, as well as
`
`the grounds
`
`for
`
`invalidity asserted
`
`in
`
`IPR2024-
`
`00234. Accordingly, Patent Owner will be filing a request for adverse judgement under 37 C.F.R.
`
`§ 42.73(b) in IPR2024-00234.
`
`In support of construing the claims to encompass financial transactions in which the
`
`principal parties to the transaction are a merchant and a user, the PTAB stated the following:
`
`“Fig. 7. Although the trusted key authority in this example is not a principal party
`to the transaction (here, the parties are the user and the application), it is an active
`participant in facilitating the transaction. In another preferred embodiment of the
`’905 Patent, trusted key authority 320 plays an active role in transactions, e.g.,
`verifying to a grocery store that a biometric key presented by a customer is
`legitimate, thereby allowing the transaction to proceed. Id. at 6:39–53, Figs. 3–4.
`However, despite trusted key authority’s active participation, the parties to such a
`transaction are the customer and the grocery store, not trusted key authority 320.”
`IPR2024-00234, Paper 10 at 10-11 (emphasis added).
`
`Figures 3 and 4, however, neither disclose nor enable a transaction between a grocery store
`
`and customer. Rather, Figures 3 and 4 depict a system and method the 905 patent details as
`
`conforming with Figure 7, which the PTAB found discloses a transaction where “the parties to the
`
`transaction are the user and the application.”
`
`Figure 7 (reproduced below) details the code utilized to authenticate a biometric key in the
`
`method 400 for authenticating a biometrically verified user. Method 400 is illustrated in Figure 4
`
`(reproduced below). Specifically, the 905 Patent states:
`
`“The code is utilized to authenticate the biometric key itself 450, 460 as described
`below with reference to FIG. 7 and profile information is received. Responsive to
`successful authentication of
`the key, access
`is allowed 470
`to
`the
`application.” 905 Patent, 7:23-28 (emphasis added).
`
` 2
`
`Patent Owner Exhibit 2016, Page 2 of 6
`
`

`

`Accordingly, Figure 4 incorporates Figure 7. Consequently, as Figure 7 depicts a
`
`transaction in which “the parties are the user and the application,” Figure 4 must also depict a
`
`transaction in which the parties are the user and the application, and not a transaction in which the
`
`parties are a customer and grocery store.
`
`
`
`
`
`
`
`
`
`Figure 3 (reproduced below) also fails to show a transaction in which the parties are a user
`
`and a merchant.
`
`
`
` 3
`
`Patent Owner Exhibit 2016, Page 3 of 6
`
`

`

`
`
`
`
`With regards to Figure 3, the 905 Patent states:
`
`
`
`“Further, in one embodiment, authentication module 310 provides the code to
`trusted key authority 320 in order to verify that it belongs to a legitimate key (e.g.,
`when application 330 is security-critical). Authentication module 310 can send a
`to application 330, or otherwise
`allow
`access
`to
`the
`message
`application, responsive to a successful authentication by trusted key authority
`320.”905 Patent, 6:13-19 (emphasis added).
`
`Authentication module 310 providing the code to trusted key authority 320 corresponds to
`
`step 710 of Figure 7 (“Wirelessly Receive The Code”) and step 450 of Figure 4 (“Request
`
`Authentication”). Furthermore, authentication module 310 sending a message to application 330
`
`responsive to successful authentication by trusted key authority 320 corresponds to step 740 of
`
`Figure 7 (“Send Access Message To The Application”). Accordingly, Figure 3 is analogous to
`
`Figure 7 and therefore depicts a transaction in which the parties are the user and the application,
`
`and not a transaction in which the parties are a customer and grocery store.
`
`As with Figures 3 and 4, the passage cited by the PTAB fails to describe a transaction
`
`between a user and merchant. The passage cited by the PTAB reads:
`
` 4
`
`Patent Owner Exhibit 2016, Page 4 of 6
`
`

`

`“In one embodiment, trusted key authority 320 verifies that a code from a biometric
`key is legitimate. To do so, the trusted key authority 320 stores a list of codes for
`legitimate biometric keys. The list can be batched or updated each time a new
`user/key is enrolled. In one embodiment, trusted key authority 320 can also store a
`profile associated with a biometric key. The profile describes the user associated
`with the key, the key itself, the trusted key authority, and/or other relevant
`information. In one embodiment, the functionality of trusted key authority 320 is
`provided by a server or other computerized device.”
`
`“In an open system, where unknown users can attempt authentication (e.g., in a
`public grocery store), trusted key authority 320 provides verification that a key
`presenting a certain code is legitimate.”905 Patent, 6:39-53 (emphasis added).
`
`Only once does the passage mention a merchant, but not as a party to a
`
`transaction. Rather, the merchant is only mentioned as the location of the transaction – “in a
`
`public grocery store.” Accordingly, the passage does not describe a transaction in which the
`
`parties are a user and a merchant.
`
`As the above demonstrates, the portions of the 905 Patent cited by the PTAB in support of
`
`its apparent construction fail to describe a transaction in which the parties are a user and
`
`merchant. Only
`
`transactions
`
`in which parties are a user and application are
`
`described. Consequently, the PTAB’s apparent construction of a “financial transaction” lacks
`
`written description and/or is not enabled by the specification of the 905 Patent. Therefore, the
`
`claims of the 905 Patent, as apparently construed by the PTAB in IPR2024-00234, are invalid
`
`under 35 U.S.C. § 112, irrespective of the prior art. This renders moot the Final Rejection and
`
`Appeal in the present proceedings, as well as the grounds for invalidity asserted in IPR2024-00234.
`
`SPE Fuelling advised Mr. Zak that irrespective of filing a request for adverse judgement
`
`under 37 C.F.R. § 42.73(b) in IPR2024-00234, the proceedings would be maintained because inter
`
` 5
`
`Patent Owner Exhibit 2016, Page 5 of 6
`
`

`

`partes review was not instituted on dependent claim 8. No agreement, consequently, was reached
`
`on how to terminate the proceedings to save the Office time and effort.
`
`With this Interview Summary, Patent Owner has filed a Statutory Disclaimer under 35
`
`U.S.C. § 253(a) and 37 C.F.R. § 1.321(a) disclaiming the entire term of U.S. Patent No. 9,298,905,
`
`thereby rendering the proceedings moot.
`
`
`October 10, 2024
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted by:
`
`/James A. Zak, Esq./
`
`Attorney for Patent Owner
`Proxense, LLC
`Reg. No. 60,190
`
`Hecht Partners LLP
`125 Park Ave. 25th Floor
`New York, NY 10017
`E: jzak@hechtpartners.com
`P: (651) 357-8517
`
` 6
`
`Patent Owner Exhibit 2016, Page 6 of 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